NSF ACCESS

jetstream-cloud.org · Compute, Storage · 2 records · JSON

NSF ACCESS / Jetstream2 object store (OpenStack Swift, S3-compatible) — 1 TB default storage per allocation Storagecaveatinstitutionno cardRwrite-gated
Jetstream2 Computefails: identityinstitutionno cardDwrite-gated

NSF ACCESS / Jetstream2 object store (OpenStack Swift, S3-compatible) — 1 TB default storage per allocation Storage

caveatinstitutionno cardRwrite-gated

docs.jetstream-cloud.org/general/quotas/ · academic · storage/nsf-access-jetstream2-object-store-1-tb-default-storage · JSON · compare

Free tier	'By default, all allocations receive 1 TB (1000 GB) of Jetstream2 Storage quota.' Additional storage is bought with ACCESS credits at '1 ACCESS credit == 1 GB', and the default is a floor, not additive: 'the default 1 TB is replaced by a discrete allocation, not added on top of it.' Explore projects carry 400,000 credits; Discover 1,500,000; Accelerate 3,000,000 — so storage up to hundreds of TB is purchasable with credits, subject to justification review. unit TB; metered on stored-bytes
Price	none stated
Per-object cap	not stated
Retention	not stated
Egress	Unmetered within the NSF cloud; temp URLs and public containers serve objects over HTTPS.
Identity	institution derived from the record's prose, not from an identity field, and no signup was executed: time. request-rate: not published. Gate: ACCESS allocation (institutional email required; Explore is the lightest at 'Overview' requirements, reviewed but not a full panel). academic
Limits	write-gated review source write-gated reviewed but not a full panel) source per-object-cap: Swift, so large objects need segmentation; no single documented byte cap. Retention: storage is allocation-lifetime. request-rate: not published. Gate: ACCESS allocation (institutional email required; Explore is the lightest at 'Overview' requirements, reviewed but not a full panel).
Binding	write-gated the write is a queue with a person or a rule in it, so the upload rate is set by somebody else
Interface	s3-compatible, cli s3
Tooling	'The Jetstream2 object store utilizes OpenStack Swift and is S3 compatible. You can utilize it via Horizon or the command line interface (CLI). From the CLI, you can use the OpenStack CLI's container and object commands, the AWS CLI's s3api, or other compatible tools.' Temp-URL keys give signed GET and signed PUT for a single object.
Composes with	1 TB default per allocation, but storage is credit-purchased, so the multiplier is ACCESS credits across project types (Explore 400k / Discover 1.5M / Accelerate 3M) and multiple requests (Explore and Discover explicitly allow 'Multiple requests allowed'). A 400k-credit Explore project = 400 GB above the default if spent purely on storage — the credit exchange rate, not a per-account cap, is the ceiling.
Reliability	Docs state plainly 'Jetstream2 is not primarily a storage service; large-capacity storage is beyond the scope of Jetstream2' — treat as a 1-50 TB tier, not an archive.
Notes	'By default, all allocations receive 1 TB (1000 GB) of Jetstream2 Storage quota.' Additional storage is bought with ACCESS credits at '1 ACCESS credit == 1 GB', and the default is a floor, not additive: 'the default 1 TB is replaced by a discrete allocation, not added on top of it.' Explore projects carry 400,000 credits; Discover 1,500,000; Accelerate 3,000,000 — so storage up to hundreds of TB is purchasable with credits, subject to justification review.
Evidence rung	reported One page read moves it to documented.
Checked	2026-10-21 (inherited); stale on 2026-11-04

Evidence (4)

date	source	what it proved
2026-10-21	docs.jetstream-cloud.org/general/quotas/	'By default, all allocations receive 1 TB (1000 GB) of Jetstream2 Storage quota', '1 ACCESS credit == 1 GB', 'the default 1 TB is replaced by a discrete allocation, not added on top of it'
2026-10-21	docs.jetstream-cloud.org/general/object/	'The Jetstream2 object store utilizes OpenStack Swift and is S3 compatible', temp URL for GET and PUT
2026-10-21	allocations.access-ci.org/project-types	Explore 400,000 / Discover 1,500,000 / Accelerate 3,000,000 credit limits; 'Multiple requests allowed' for the first three tiers
2026-10-21	allocations.access-ci.org/get-your-first-project	not published

Unknown or withheld values (6)

$.evidence[3].proved withheld
$.free_tier.notes process
$.per_object_cap.notes not-extracted
$.per_object_cap.stated not-extracted
$.retention.notes not-extracted
$.retention.stated not-extracted

Jetstream2 Compute

fails: identityinstitutionno cardDwrite-gated

docs.jetstream-cloud.org/general/vmsizes/ · GPU cloud · compute/jetstream2 · JSON · compare

Free tier	Jetstream2 prices every instance in ACCESS service units at 1 SU per vCPU per hour on CPU flavours and 2 SU per vCPU per hour on GPU and Large Memory flavours. A full A100 card flavour (g3.xl, 32 vCPU, 120 GB RAM, 40 GB GPU RAM) costs 64 SU per hour; a half-card (g3.large, 16 vCPU, 20 GB GPU RAM) costs 32 SU per hour; a quarter-card (g3.medium, 8 vCPU, 10 GB GPU RAM) costs 16 SU per hour. The smallest ACCESS tier, Explore, carries 400,000 credits, so 400,000 / 64 = 6,250 hours of a full A100 card, 12,500 hours of a half card, or 400,000 vCPU-hours on CPU flavours. unit hours; metered on wall-clock; credit-converted-allocation
Price	none stated
Per-object cap	not applicable
Retention	not applicable
Egress	not stated
Identity	institution not published
Limits	write-gated not published source
Binding	write-gated
Interface	unknown inferred from the tooling the provider documents; not probed
Tooling	not stated
Composes with	This is the conversion the ACCESS record lacked: an Explore allocation is not 400,000 abstract credits but 6,250 A100-hours or 400,000 vCPU-hours, which turns the ACCESS tier from a benchmark allowance into roughly a year of a single always-on A100 at 16 hours a day. It composes badly with the free GPU vendors, because the same workload that fits a 40 GB card on Jetstream2 fits a 16 GB T4 elsewhere only after splitting.
Reliability	no reliability event recorded
Notes	This finding changes dossier/compute/access.json: that record states the 400,000 credit limit but does not convert it, so a reader cannot tell whether Explore buys an afternoon or a year. The division is shown above and uses only rates from the two vendor pages. The cheapest paid shape is not applicable: Jetstream2 sells nothing for cash, and the credits are not purchasable, so the alternative to the institutional gate is not money. Note that stopped instances are still charged 75 percent and shelved instances are charged nothing, which changes the effective hours for an interactive workload. No account was created, so the rung is documented rather than measured.
Evidence rung	documented
Checked	2026-10-22 (live); stale on 2026-11-21

Evidence (5)

date	source	what it proved
2026-10-22	docs.jetstream-cloud.org/general/access/	"1 ACCESS Credit = 1 Jetstream2 SU"; SU consumption is "1 SU per vCPU_core-hour" on CPU and "2 SUs per vCPU_core-hour" on Jetstream2-GPU and Large Memory, quoted
2026-10-22	docs.jetstream-cloud.org/general/vmsizes/	g3.xl is 32 vCPU, 120 GB RAM, NVIDIA A100 with 40 GB GPU RAM at 64 SU per hour; g3.large is 16 vCPU, 20 GB GPU RAM at 32 SU per hour; g3.medium is 8 vCPU, 10 GB GPU RAM at 16 SU per hour, quoted from the flavour tables
2026-10-22	docs.jetstream-cloud.org/faq/alloc/	"To use Jetstream2, your account must belong to an ACCESS allocation that is active on a Jetstream2 resource", quoted
2026-10-22	docs.jetstream-cloud.org/general/vmsizes/	"The three instance types are all separate ACCESS resources ... Having access to one does NOT include access to all", quoted
2026-10-22	allocations.access-ci.org/project-types	Explore ACCESS credit limit is 400,000, accepted anytime, quoted

More fields (1)

{
 "wave2": {
  "class": "academic-cloud",
  "free_tier_kind": "credit-converted-allocation",
  "shape": {
   "vcpu": 32,
   "ram_gib": 120,
   "gpu_class": "NVIDIA A100 40 GB",
   "gpu_count": 1
  }
 }
}

Unknown or withheld values (13)

$.binding_note withheld
$.egress.metered egress-unknown
$.egress.terms not-stated
$.identity_cost.detail process
$.interface interface-unknown
$.limits[0].value withheld
$.limits_note withheld
$.per_object_cap.notes process
$.per_object_cap.stated not-applicable
$.reliability_note none-observed
$.retention.notes process
$.retention.stated not-applicable
$.tooling not-stated