Object Storage Pricing
How the three tier allowances are measured, what happens when you exceed one, and how CDN delivery is metered on top.
Object storage uses prepaid tiers.
| What | Rate | Detail |
|---|---|---|
| Starter | $5 / month | 25 GB storage · 10 GB egress · 500K requests |
| Growth | $20 / month | 100 GB storage · 50 GB egress · 2M requests |
| Scale | $75 / month | 500 GB storage · 250 GB egress · 5M requests |
| Enterprise | $300 / month | 2 TB storage · 1 TB egress · 50M requests |
| CDN delivery | $0.12 / GB | Metered on top of the tier, only while the CDN is enabled |
| CDN requests | $0.015 / 10K requests | HTTPS requests served from the edge |
Three allowances, one price
Every tier bundles three allowances together:
- Storage — bytes held in the bucket
- Egress — bytes served out of the bucket
- Requests — operations against the bucket
The tier price is the whole bill for the bucket. You do not pay per GB or per request on top of it.
This matters when choosing a tier: weigh all three, not just storage. A small dataset with heavy read traffic can need a larger tier than a large archive nobody touches.
Exceeding an allowance
The three allowances are checked independently — exceeding any one of them is enough to trigger the sequence below.
- At 80% of any allowance, you are warned in-app and by email.
- Past 110%, the bucket is suspended: reads and writes are blocked.
Suspension preserves your data. The bucket stays visible and nothing is deleted. Upgrading the tier reactivates it immediately.
The 10% band above the allowance is deliberate headroom, so a bucket that drifts slightly over does not stop serving without warning.
Changing tier
Upgrades take effect immediately and are prorated against the current period.
A downgrade is only possible if current usage already fits inside the target tier's allowances — otherwise the bucket would be suspended the moment the change applied.
CDN delivery
The CDN is an opt-in add-on and the one part of object storage that is metered. When enabled, delivery is billed on:
- bytes delivered from the edge
- HTTPS requests served by the edge
This is charged in addition to the tier, and only for what the CDN actually serves. The CDN requires the bucket to allow public access.
Turning the CDN off removes the added cost. The bucket stays reachable on its regular public URL.
Deleting a bucket
Deleting stops the billing and credits the unused part of the period. The objects are destroyed with the bucket.