NOMAD
nomad-lab.eu · Storage · 1 record · JSON
NOMAD (NOMAD Central / nomad-lab.eu) Storage
fails: quotaemailno cardR
| Free tier | 32 GiB maximum per project, and at most 10 unpublished projects per user. Both are config knobs (process.max_upload_size, services.upload_limit) rather than business limits, and they differ per deployment. Publishing requires at least one successfully parsed entry, and publishing is what frees the 10-project slot. unit GiB; metered on unstated |
|---|---|
| Price | none stated |
| Per-object cap | not stated |
| Retention | not stated |
| Egress | Free and anonymous for published entries via the NOMAD API and GUI. |
| Identity | email email |
| Binding | none no constraint of a named kind was recorded; the verdict rests on the quota sentence rather than on a named limit |
| Interface | rest rest |
| Tooling | A documented REST API (I got HTTP 401 'Authentication required.' from /prod/v1/api/v1/info, which is the correct behaviour — a real auth gate, not a fake 200) with API-token upload from the GUI's 'Upload via API' dialog. Parsers are plugin-based, so what counts as a valid file is deployment-specific. |
| Composes with | So the steady-state ceiling is bounded by how fast a human can publish, not by bytes. |
| Reliability | Well-run EU (FAIRmat) infrastructure with a real API. The constraint is semantic, not technical. |
| Notes | 32 GiB maximum per project, and at most 10 unpublished projects per user. Both are config knobs (process.max_upload_size, services.upload_limit) rather than business limits, and they differ per deployment. Publishing requires at least one successfully parsed entry, and publishing is what frees the 10-project slot. |
| Evidence rung | reported One page read moves it to documented. |
| Checked | 2026-10-21 (inherited); stale on 2026-11-04 |
Evidence (3)
| date | source | what it proved |
|---|---|---|
| 2026-10-21 | docs.nomad-lab.eu/howto/manage/gui/upload.html | opened: 'a maximum project size of 32 GiB, controlled by process.max_upload_size'; 'at most 10 unpublished projects per user, controlled by services.upload_limit'; 'A project must contain at least one successfully processed entry before it can be published.' |
| 2026-10-21 | nomad-lab.eu/prod/v1/api/v1/info | PROBED: curl -> HTTP 200, 271,764 bytes (public endpoint). curl https://nomad-lab.eu/prod/v1/api/v1/uploads?page_size=1 -> HTTP 401, 37 bytes, {"detail":"Authentication required."} — an honest auth gate. |
| 2026-10-21 | nomad-lab.eu/prod/v1/docs/howto/manage/gui/upload.html | (older v1 doc, reached via search) — same 32 GB / 10 upload figures, confirming the numbers are stable across doc generations. |
More fields (1)
{
"dead_end": {
"failure_class": "quota",
"why": "32 GiB maximum per project, and at most 10 unpublished projects per user. Both are config knobs (process.max_upload_size, services.upload_limit) rather than business limits, and they differ per deployment. Publishing requires at least one successfully parsed entry, and publishing is what frees the 10-project slot.",
"retry_when": null,
"first_recorded": "2026-10-21"
}
}Unknown or withheld values (7)
$.chainingpartly-held$.extras.dead_end.retry_whenprocess$.free_tier.notesprocess$.per_object_cap.notesnot-extracted$.per_object_cap.statednot-extracted$.retention.notesnot-extracted$.retention.statednot-extracted