osf registrations

osf.io · Storage · 2 records · JSON

OSF (Open Science Framework) — per-component quotas Storagecaveatinstitution?card?Rper-object-cap
osf registrations (as a quota multiplier) Storagefails: quotaemail?card?R

OSF (Open Science Framework) — per-component quotas Storage

caveatinstitution?card?Rper-object-cap

osf.io · academic · storage/osf-per-component-quotas · JSON · compare

Free tier	50 GB per public project, 5 GB per private project, 5 GB per file — but 'Each Component on a project has its own 5GB/50GB storage limit' and, crucially, 'Currently, there is no applied overall cap on the amount of OSF Storage per user.' Component trees are unbounded, so this is per-unit quota, not per-account. unit GB; metered on stored-bytes
Price	none stated
Per-object cap	5 GB per file (5000000000 bytes)
Retention	not stated
Egress	Unmetered; downloads served from OSF Storage (US/Canada/Germany/Australia regions)
Identity	institution (placeholder) inferred from the category 'academic'; the source record states no identity cost, so this is a class assumption, not evidence
Limits	per-object-cap 5 GB per file source 5 GB per file is the hard limit — worse than Zenodo's 50 GB and worse than Harvard's 2.5 GB only in being middling. 5 GB applies to private projects, so working storage is the expensive tier here; 50 GB requires making the project public.
Binding	per-object-cap the per-object cap sets the shard size and therefore the object count; it bounds the total more tightly than any headline quota
Interface	rest rest
Tooling	OSF open API v2 (api.osf.io/v2, JSON:API: nodes, files, waterbutler); official osfclient Python package; OSF is the canonical 'component = free bucket' multiplier
Composes with	50 GB x unlimited components x (optionally) unlimited projects. A project can nest components, each with its own 50 GB, and there is no overall per-user cap — so the structure is the same per-record multiplier as Zenodo but with a smaller unit (50 GB) and a much lower per-file ceiling (5 GB).
Reliability	OSF is mid-'Project Transition' per its own help banner, which is a structural-change risk for a long-lived archive. Storage is regional and selectable only at project creation and cannot be moved afterwards.
Notes	50 GB per public project, 5 GB per private project, 5 GB per file — but 'Each Component on a project has its own 5GB/50GB storage limit' and, crucially, 'Currently, there is no applied overall cap on the amount of OSF Storage per user.' Component trees are unbounded, so this is per-unit quota, not per-account.
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 5.0 GB

Evidence (3)

date	source	what it proved
2026-10-21	help.osf.io/article/555-add-ons-storage-api-integration-faq-	read live: 'Currently, there is no applied overall cap on the amount of OSF Storage per user' and 'Individual files must be 5GB or less'
2026-10-21	help.osf.io/article/353-welcome-to-projects	read live: 'Private Projects: 5 GB ... Public Projects: 50 GB ... Max File Size: 5 GB per individual file ... Each Component on a project has its own 5GB/50GB storage limit'
2026-10-21	help.osf.io/article/353-welcome-to-projects	read live: storage add-ons 'do not count against these storage limits', i.e. add-ons are a second un-metered path

Unknown or withheld values (5)

$.free_tier.notes process
$.identity_cost.kind identity-defaulted
$.per_object_cap.notes not-extracted
$.retention.notes not-extracted
$.retention.stated not-extracted

osf registrations (as a quota multiplier) Storage

fails: quotaemail?card?R

help.osf.io/article/555-add-ons-storage-api-integration-faq- · rejected-provider · storage/osf-registrations · JSON · compare

Free tier	Registrations archive OSF Storage plus add-ons but are capped at 5 GB across all storage being registered, and you can no longer create Registrations from Projects after the transition. Not unit none; metered on none
Price	none stated
Per-object cap	not recorded
Retention	not recorded
Egress	not recorded
Identity	email (placeholder) not published
Binding	none no constraint of a named kind was recorded; the verdict rests on the quota sentence rather than on a named limit
Interface	unknown
Tooling	not recorded
Composes with	not recorded
Reliability	Registrations archive OSF Storage plus add-ons but are capped at 5 GB across all storage being registered, and you can no longer create Registrations from Projects after the transition. Not
Notes	Registrations archive OSF Storage plus add-ons but are capped at 5 GB across all storage being registered, and you can no longer create Registrations from Projects after the transition. Not
Evidence rung	reported
Checked	2026-10-21 (inherited); stale on 2026-11-04

Evidence (1)

date	source	what it proved
2026-10-21	help.osf.io/article/555-add-ons-storage-api-integration-faq-	Registrations archive OSF Storage plus add-ons but are capped at 5 GB across all storage being registered, and you can no longer create Registrations from Projects after the transition. Not

More fields (1)

{
 "dead_end": {
  "failure_class": "quota",
  "why": "Registrations archive OSF Storage plus add-ons but are capped at 5 GB across all storage being registered, and you can no longer create Registrations from Projects after the transition. Not",
  "retry_when": null,
  "first_recorded": "2026-10-21"
 }
}

Unknown or withheld values (15)

$.chaining not-recorded
$.confidence_note withheld
$.egress.terms not-recorded
$.extras.dead_end.retry_when process
$.free_tier.notes process
$.identity_cost.detail defaulted
$.identity_cost.kind identity-defaulted
$.interface interface-unknown
$.interface_detail withheld
$.limits_note process
$.per_object_cap.notes not-recorded
$.per_object_cap.stated not-recorded
$.retention.notes process
$.retention.stated not-recorded
$.tooling not-recorded