NAKALA

nakala.fr · Storage · 2 records · JSON

NAKALA (IR* Huma-Num, CNRS / French national HSS data repository) Storagecaveatinstitutionno cardRdisagrees
Nakala (Huma-Num, France) - no formal size limit, but a HumanID gate and a conversation with the team Storagefails: identityinstitutionno cardRdisagrees

NAKALA (IR* Huma-Num, CNRS / French national HSS data repository) Storage

caveatinstitutionno cardRdisagrees

nakala.fr · academic · storage/nakala · JSON · compare

Sibling records disagree:

verdict: storage/nakala says qualifies-with-caveat, storage/nakala-no-formal-size-limit-but-a-humanid-gate-and-a-con says fails-identity

Free tier	Public deposits are explicitly uncapped: 'Il n'existe aucune limite pour les dépôts publics' (there is no limit for public deposits), and 'Un accès à vos données sans limite de volumétrie, ni de temps' (access to your data with no volume or time limit). The only quota is on PRIVATE staging: 10,000 private deposits or 100 GB equivalent. unit GB; metered on unstated
Price	none stated
Per-object cap	not stated
Retention	not published
Egress	Free. Files are served from Huma-Num/IN2P3-hosted infrastructure in France with no metering and no egress charge; public deposits are downloadable by any visitor and IIIF image endpoints are exposed for tif/tiff/jpg/jpeg/jp2.
Identity	institution derived from the record's prose, not from an identity field, and no signup was executed: 00 GB equivalent. CRITICAL liveness flag: nakala.fr and api.nakala.fr both returned HTTP 503 on 6 consecutive probes across ~25 minutes (site and API, direct and through the proxy
Binding	none no constraint in the record binds at this scale; the record carries no limit of a kind the vocabulary names
Interface	rest, rclone rest
Tooling	Documented REST API split into search / datas / collections / groups / users / vocabularies, with a per-account API key ('Certaines opérations nécessitent ... sa clé d'API disponible dans son compte personnel'); swagger at api.nakala.fr/doc, separate test instance apitest.nakala.fr. Also OAI-PMH (api.nakala.fr/oai2?verb=Identify), a SPARQL triplestore, IIIF Image API, and a published notebook at gitlab.huma-num.fr/huma-num-public/notebook-api-nakala. No rclone backend.
Composes with	Unlimited public deposits per account, no volume cap per deposit — so the account is the only unit and it does not need multiplying for 500 GB. Groups feature shares deposit rights across a project team, so a lab can pour many researchers' output into one quota-free surface.
Reliability	CRITICAL liveness flag: nakala.fr and api.nakala.fr both returned HTTP 503 on 6 consecutive probes across ~25 minutes (site and API, direct and through the proxy), so the quota is docs-verified but the service was NOT live at probe time. Budget-stable (CNRS-funded national infrastructure) but treat availability as unconfirmed.
Notes	Public deposits are explicitly uncapped: 'Il n'existe aucune limite pour les dépôts publics' (there is no limit for public deposits), and 'Un accès à vos données sans limite de volumétrie, ni de temps' (access to your data with no volume or time limit). The only quota is on PRIVATE staging: 10,000 private deposits or 100 GB equivalent.
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	documentation.huma-num.fr/nakala/	'Il n'existe aucune limite pour les dépôts publics' and 'Le nombre de dépôts privés par déposant est limité à 10 000 (ou l'équivalent de 100 Go)'
2026-10-21	documentation.huma-num.fr/nakala-API/	REST API endpoint list, api.nakala.fr/doc, OAI-PMH, SPARQL, IIIF
2026-10-21	nakala.fr/	probe: GET -> 503 six times; GET https://api.nakala.fr/oai2?verb=Identify -> 503 (service down at probe time)

Unknown or withheld values (5)

$.free_tier.notes process
$.per_object_cap.notes not-extracted
$.per_object_cap.stated not-extracted
$.retention.notes not-extracted
$.retention.stated withheld

Nakala (Huma-Num, France) - no formal size limit, but a HumanID gate and a conversation with the team Storage

fails: identityinstitutionno cardRdisagrees

nakala.fr/ · academic · storage/nakala-no-formal-size-limit-but-a-humanid-gate-and-a-con · JSON · compare

Sibling records disagree:

verdict: storage/nakala says qualifies-with-caveat, storage/nakala-no-formal-size-limit-but-a-humanid-gate-and-a-con says fails-identity

Free tier	'There is no formal limitation on the size of data deposited'; above ~10 GB per file you must contact the Nakala team first. Private pre-publication space is capped far lower (9,999 items or 100 GB), so the large-volume path is publish-as-you-go. unit objects; metered on unstated
Price	none stated
Per-object cap	10 GB per file (10000000000 bytes)
Retention	not stated
Egress	Free public HTTPS with a DOI per deposit; no egress metering published.
Identity	institution institution
Limits	per-object-cap 10 GB per file source Account path is HumanID -> request Nakala access -> 'Discuss the scientific and technical project associated with the deposit with HumaNum's team'. Research data only, must be documented to a metadata schema, licence from a closed list, ORCID checked on authors. Published deposits cannot be deleted unilaterally.
Binding	none the quota is real and unreachable: identity is the binding constraint, and it is not one of the six limits kinds
Interface	rest rest
Tooling	Nakala REST API plus nakalot (multipart batch uploader driven by a CSV/XLS manifest); OAI-PMH.
Composes with	Per deposit, unlimited deposits - but the gate is identity, not bytes.
Reliability	MESR-funded national infrastructure, data preserved at CINES after audit; ~100 TB of storage on the ISIDORE/Nakala stack. French research context in practice.
Notes	'There is no formal limitation on the size of data deposited'; above ~10 GB per file you must contact the Nakala team first. Private pre-publication space is capped far lower (9,999 items or 100 GB), so the large-volume path is publish-as-you-go.
Evidence rung	reported One page read moves it to documented.
Checked	2026-10-21 (inherited); stale on 2026-11-04
Parsed numbers	`$.limits[0].value` limit:per-object-cap 10.0 GB

Evidence (3)

date	source	what it proved
2026-10-21	documentation.huma-num.fr/nakala-faq/	'Il n'y a pas formellement de limitation pour la taille des donnees deposees. Cependant... superieur a 10 GOs par fichier, il est necessaire de prendre contact avec l'equipe NAKALA'
2026-10-21	documentation.huma-num.fr/en/nakala-workflow-en/	'Request a HumanID login'; 'Discuss the scientific and technical project... with HumaNum's team'; mandatory pre-curation for level 2/3
2026-10-21	www.orient-mediterranee.com/wp-content/uploads/2024/01/2023_	'Espace de depot limite a 9 999 donnees ou a 100 Go' for the private status

More fields (1)

{
 "dead_end": {
  "failure_class": "quota",
  "why": "'There is no formal limitation on the size of data deposited'; above ~10 GB per file you must contact the Nakala team first. Private pre-publication space is capped far lower (9,999 items or 100 GB), so the large-volume path is publish-as-you-go.",
  "retry_when": null,
  "first_recorded": "2026-10-21"
 }
}

Unknown or withheld values (5)

$.extras.dead_end.retry_when process
$.free_tier.notes process
$.per_object_cap.notes not-extracted
$.retention.notes not-extracted
$.retention.stated not-extracted