osf registrations
osf.io · 2 records in Storage · JSON
Records 2
- caveatOSF (Open Science Framework) — per-component quotas
Storagefree tieridentity institution?card?limit per-object-capevidence reportedstale on 2026-11-05
- fails: quotaosf registrations
Storageidentity email?card?evidence reportedstale on 2026-11-05
- Free allowance
- 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...
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- free tier
- Identity
- institution?placeholder, not evidence; card unknown, phone unknown
- Binding limit
- per-object-cap5 GB per file
- Evidence
- reported3 sources; a third party said so
- Freshness
- stale on 2026-11-05checked 2026-10-21 (inherited); stale on 2026-11-05
| 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 |
| Limits |
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. |
| 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; downloads served from OSF Storage (US/Canada/Germany/Australia regions) |
| Per-object cap | 5 GB per file (5000000000 bytes) |
| Retention | not stated |
| 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. |
| Parsed numbers |
|
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 values 3
- per object cap notes: 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
osf registrations
Storage- Free allowance
- 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.
- Verdict
- fails: quotathe free allowance is too small to matter
- Cost
- not stated
- Identity
- email?placeholder, not evidence; card unknown, phone unknown
- Binding limit
- noneno named constraint binds
- Evidence
- reported1 source; a third party said so
- Freshness
- stale on 2026-11-05checked 2026-10-21 (inherited); stale on 2026-11-05
| 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 |
| Identity | email (placeholder) not published |
| Egress | not recorded |
| Interface | unknown |
| Tooling | not recorded |
Evidence 1
| date | source | what it proved |
|---|---|---|
| 2026-10-21 | help.osf.io/article/555-add-ons-storage-api-integration-faq- | the text of Free tier, above |
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 values 7
- chaining: no value was recorded for this field
- egress terms: no value was recorded for this field
- interface: the access interface was not established
- per object cap notes: no value was recorded for this field
- per object cap stated: no value was recorded for this field
- retention stated: no value was recorded for this field
- tooling: no value was recorded for this field