Cosmoner Docs
Pricing

Object Storage Pricing

How the three tier allowances are measured, how usage above them is billed, the monthly overage limit, and how CDN delivery is metered on top.

Object storage uses prepaid tiers, with usage above a tier's allowance billed as overage.

WhatRateDetail
StarterUSD 5 / month25 GB storage · 10 GB egress · 500K requests
GrowthUSD 20 / month100 GB storage · 50 GB egress · 2M requests
ScaleUSD 75 / month500 GB storage · 250 GB egress · 5M requests
EnterpriseUSD 300 / month2 TB storage · 1 TB egress · 20M requests
Storage above the planUSD 0.20 / GB · moPer GB stored past the allowance, for the time it is stored
Egress above the planUSD 0.12 / GBPer GB served past the period's allowance
Requests above the planUSD 0.02 / 10K requestsPer 10,000 requests past the period's allowance
CDN deliveryUSD 0.12 / GBMetered on top of the tier, only while the CDN is enabled
CDN requestsUSD 0.015 / 10K requestsHTTPS 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

As long as the bucket stays within all three, the tier price is the whole bill for 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.

A bucket keeps the allowances its tier had when you created it or last changed its tier. If a tier's allowances change later, buckets already on it keep what they have until you change their tier.

Going over an allowance

The bucket keeps working when it goes past an allowance. What it uses above the allowance is billed as overage, at the rates in the table above:

  • Storage — per GB above the allowance, for as long as it is stored over the month. 10 GB above the allowance for half the period costs the same as 5 GB above it for the whole period.
  • Egress — per GB served above the period's allowance.
  • Requests — per 10,000 requests above the period's allowance.

Each allowance is checked on its own, and overage is measured once a day. At 80% of any allowance you are warned in-app and by email, once per billing period.

The storage rate is the same per-GB rate the Starter and Growth tiers include storage at, so going over a little costs no more than the tier itself would. If a bucket regularly runs well past its allowance, the next tier is usually cheaper — the overage line on your invoice shows when that point comes.

Monthly overage limit

Each bucket can have a limit on how much overage it runs up in one billing period, set from the bucket's page. You choose what happens when the overage reaches it:

  • Alert — the billing contact is emailed, once per period. The bucket keeps working and its overage keeps being billed.
  • Block — the billing contact is emailed and the bucket's files can no longer be read or written, through access keys, public links and the CDN alike, until the next billing period starts. Listing and deleting files still work, and nothing is deleted. Storage above the allowance is still billed while the bucket is blocked, since the data is still kept.

Overage is checked once a day, so the limit applies at the first check after it is reached, not the moment it is. Raising or removing the limit, switching to Alert, or upgrading the tier unblocks a blocked bucket straight away.

A bucket has no limit unless you set one.

Changing tier

Upgrades take effect immediately and are prorated against the current period. The bucket takes the new tier's allowances from that moment.

A downgrade is only possible if current usage already fits inside the target tier's allowances.

CDN delivery

The CDN is an opt-in add-on, metered separately from the tier's allowances. 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. It works on private buckets too, and can be limited to chosen folders.

Turning the CDN off removes the added cost. The bucket stays reachable on its regular public URL if public access is on.

Deleting a bucket

Deleting stops the billing and credits the unused part of the period. The objects are destroyed with the bucket.

On this page