Home
LUMI
lumi-supercomputer.eu · 2 records in Compute, Storage · JSON
Records 2
docs.lumi-supercomputer.eu/firststeps/accessLUMI/National HPC allocationcompute/lumiJSONcomparereport an error
- Free allowance
- Access to LUMI requires membership of a project that has already been granted resources.
- Verdict
- fails: identitythe identity required is not reachable without it
- Cost
- free tier
- Identity
- institutioncard unknown, phone unknown
- Binding limit
- write-gatedThere is no LUMI-wide application: a person must be invited into a project by a national Resource Allocator, so the door is a national affiliation in one of 13 countries, and the alternative CSC route requires affiliation with a Finnish...
- Evidence
- documented3 sources; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-11-22checked 2026-10-22 (live); stale on 2026-11-22
| Free tier | Access to LUMI requires membership of a project that has already been granted resources. unit hours; metered on wall-clock; national consortium allocation |
|---|
| Price | none stated |
|---|
| Limits | - write-gated (binding) There is no LUMI-wide application: a person must be invited into a project by a national Resource Allocator, so the door is a national affiliation in one of 13 countries, and the alternative CSC route requires affiliation with a Finnish institution. source
|
|---|
| Identity | institution The consortium covers Belgium, Czechia, Denmark, Estonia, Finland, Iceland, Netherlands, Norway, Poland, Sweden, Switzerland plus EuroHPC JU; the Finnish route needs affiliation with a Finnish higher-education or research institute, or an organisation established or located in Finland. No card, hold, phone number or ID document is stated: unknown. |
|---|
| Egress | not stated |
|---|
| Interface | unknown inferred from the tooling the provider documents; not probed |
|---|
| Tooling | not stated |
|---|
| Composes with | The only LUMI route that does not need a consortium affiliation is the EuroHPC call stack recorded separately, and that stack is gated on an EU-affiliated organisation rather than on a LUMI country. |
|---|
| Reliability | no reliability event recorded |
|---|
| Notes | There are 12 national allocators plus the EuroHPC JU, and they are the only entries. The Finnish national route states a useful floor of 1 million core hours for a developer project, which is the clearest published size found for a LUMI national allocation. GPU-hour figures for LUMI-G are set per national allocator and are not published centrally, so the field is null rather than borrowed from the EuroHPC tables. |
|---|
| Parsed numbers | |
|---|
Evidence 3
| date | source | what it proved |
|---|
| 2026-10-22 | docs.lumi-supercomputer.eu/firststeps/accessLUMI/ | 'To access LUMI, you need to be a member of a project that has been granted resources on LUMI. The LUMI consortium countries have different policies for accessing LUMI'; 'a Resource Allocator (RA) must create a project and invite the Principal Investigator', quoted |
| 2026-10-22 | docs.lumi-supercomputer.eu/firststeps/accessLUMI/ | consortium list covers Belgium, Czechia, Denmark, Estonia, Finland, Iceland, Netherlands, Norway, Poland, Sweden, Switzerland plus EuroHPC JU |
| 2026-10-22 | research.csc.fi/eosc-services/lumi/ | 'You can apply for the national LUMI resources either as an academic user affiliated with a Finnish higher-education or research institute or as an industry user from an organization established or located in Finland'; 'Developer project access starts from 1 million core hours', quoted |
More fields 1
| facets | {"class": "national-hpc","free_tier_kind": "national consortium allocation","shape": {"vcpu": null,"ram_gib": null,"gpu_class": "AMD MI250X (LUMI-G)","gpu_count": null}} |
|---|
Unknown values 7
- egress metered: egress metering was not published
- egress terms: a source was read and is silent on this field
- interface: the access interface was not established
- per object cap stated: the field does not apply to this kind of offer
- reliability note: nothing of this kind was observed
- retention stated: the field does not apply to this kind of offer
- tooling: a source was read and is silent on this field
docs.lumi-supercomputer.eu/storage/lumio/Academicstorage/lumi-o-150-tb-allocated-per-lumi-project-by-defaultJSONcomparereport an error
- Free allowance
- 'LUMI-O offers a total of 30 PB storage space ...
- Verdict
- fails: identitythe identity required is not reachable without it
- Cost
- free tier
- Identity
- institution?placeholder, not evidence; card unknown, phone unknown
- Binding limit
- noneno named constraint binds
- Evidence
- documented4 sources; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-11-21checked 2026-10-21 (inherited); stale on 2026-11-21
| Free tier | 'LUMI-O offers a total of 30 PB storage space ... By default 150 TB of storage space is allocated per LUMI project, but projects can request for more LUMI-O storage space by contacting the LUMI helpdesk.' This is the single largest default per-project object-storage quota found in the entire survey. unit TB; metered on stored-bytes |
|---|
| Price | none stated |
|---|
| Binding | none 150 TB per LUMI project needs a LUMI/EuroHPC project; the endpoint answers anonymously and issues nothing. Identity binds before any limit does. |
|---|
| Identity | institution (placeholder) inferred from the category 'academic'; the source record states no identity cost, so this is a class assumption, not evidence |
|---|
| Egress | Unmetered; public buckets and presigned URLs are served over HTTPS. 'It is possible to share public data across the internet (for the duration of your project)' and 'to set a temporary access link to otherwise private data'. |
|---|
| Per-object cap | not stated |
|---|
| Retention | not stated |
|---|
| Interface | s3, rclone, cli s3 |
|---|
| Tooling | rclone, s3cmd, aws cli, LUMI web interface. Credentials are LUMI-O access tokens generated at auth.lumidata.eu, scoped to a project. |
|---|
| Composes with | 150 TB × N LUMI projects. A LUMI project is the unit; Finnish researchers create LUMI projects through MyCSC (the 'LUMI' project category) and LUMI is also reachable through EuroHPC Benchmark/Regular access and through national shares (e.g. SURF's Small Compute applications include 'up to 100,000 TB-hours project space storage' on LUMI). Every LUMI project carries LUMI-O by default: 'All LUMI projects have LUMI-O available by default.' |
|---|
| Reliability | Data dies with the project; no backup is implied and objects cannot be modified in place. |
|---|
| Notes | 'LUMI-O offers a total of 30 PB storage space ... By default 150 TB of storage space is allocated per LUMI project, but projects can request for more LUMI-O storage space by contacting the LUMI helpdesk.' This is the single largest default per-project object-storage quota found in the entire survey. VERDICT: fails-identity. Quota and gate in one sentence: 150 TB per LUMI project by default out of 30 PB, reachable only through a LUMI or EuroHPC project allocation, so the quota is real and unreachable for a user. |
|---|
| Evidence note | documented The page states the number in the record; the claim is documented, not measured. The verdict is fails-identity on the registration gate; the quota is documented and the gate is documented. |
|---|
| Parsed numbers | |
|---|
Evidence 4
| date | source | what it proved |
|---|
| 2026-10-22 | docs.lumi-supercomputer.eu/storage/lumi-o/ | LUMI-O exists and states its allocation model. Re-read https://docs.lumi-supercomputer.eu/storage/lumi-o/: HTTP 404, 93393 bytes, sha256 79f4bb0a87f739c6. Quoted: nav_7_3" > <label class="md-nav__link" for="__nav_7_3" id="__nav_7_3_label" tabindex="0"> <span class="md-ellipsis"> LUMI-O object storage </span> <span class="md-nav__icon md-icon"></span> </label> <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_7_3_label" aria-expanded="false"> <label class="md-nav__ |
| 2026-10-21 | docs.lumi-supercomputer.eu/storage/lumio/ | 'totals 30 PB', 'By default 150 TB of storage space is allocated per LUMI project', 'One bucket can contain up to 500k objects', 'Data lifetime in LUMI-O is the same as your project lifetime' |
| 2026-10-21 | docs.lumi-supercomputer.eu/storage/lumio/advanced/ | ACLs/policies make buckets or single objects public; presigned URLs for time-limited public read AND time-limited upload to a specific key |
| 2026-10-21 | lumidata.eu/ | probe: curl -D - -> HTTP/1.1 200 OK, server: 'Ceph Object Gateway (squid)', x-amz-request-id ...-lumi-prod. The public S3 endpoint is live and is Ceph RGW. |
More fields 1
| verified | [{"url": "https://docs.lumi-supercomputer.eu/storage/lumi-o/","date": "2026-10-22","via": null,"http_status": 404,"bytes": 93393,"sha256": "79f4bb0a87f739c606e859ff1651eafe74227283b0ad97ec3606ebbbf825fd2e","pattern_found": true,"what_changed": "no change: the page still states the claim","capture": null}] |
|---|
Unknown values 4
- per object cap notes: the field may be stated in a source that was not read
- per object cap stated: the field may be stated in a source that was not read
- retention notes: the field may be stated in a source that was not read
- retention stated: the field may be stated in a source that was not read
Corrections
- 2026-10-22 Corrected on 2026-10-22: storage/csc-allas-10-tib-default-per-project-s3-swift-on-ceph, storage/lumi-o-150-tb-allocated-per-lumi-project-by-default