What does object storage cost? Storage, requests and traffic
Object storage costs more than just gigabytes: requests, outbound traffic and retention periods all count towards the total price.
The costs of object storage consist of storage volume, number of requests, outbound data traffic and extra features such as versioning and replication. Calculate each component separately with your own usage. A low storage price says little if requests or data traffic weigh heavily.
Who is it for: Technical buyers and developers who want to model the total cost of object storage before choosing a provider.
What cost types make up object storage?
Almost every provider charges for one or more of the following components. The names differ, but the structure is comparable.
- Storage volume: the amount of data you keep, usually measured as an average over a period.
- Requests: the number of API calls, often split into writes, reads and management actions.
- Data traffic: mainly outbound traffic (egress) to the internet or other regions.
- Extra features: versioning, replication, storage classes, retrieval of cold data and any minimum retention periods.
How do you calculate the total cost?
Use a formula with your own variables. Call the storage volume V, the storage rate T_o per unit per period, the number of requests R with rate T_r per unit, the outbound traffic E with rate T_e and a fixed component F for features or minimum commitment. Then: total = V x T_o + R x T_r + E x T_e + F.
Fill in realistic assumptions. How much data changes, how often are objects read, how much goes through a CDN and how much directly to users? Also calculate with growth: V increases, and with versioning the volume grows faster than your new data.
Where are the surprises?
Many small objects turn requests into a large cost item, because each object requires a separate call. Combining data into larger files reduces that number.
Outbound traffic becomes important as soon as data is read a lot: media files, downloads and analysis by systems outside the provider. A migration or a restore from a backup can also produce a large one-off egress charge. When you switch providers, the Data Act rules apply to providers that serve customers in the EU.
Minimum retention periods and retrieval costs in cold storage classes make cheap storage expensive if you reach for it too often. If you delete an object before the period has expired, you often still pay for the remaining period.
How do you compare providers fairly?
Build a model in a spreadsheet with your volumes and read patterns. Have every provider run through the same scenarios: normal use, peak month, full restore and exit. Ask about costs that are not on the price list, such as support, minimum contracts and costs for private network connections.
Cost items and what drives them
| Cost item | Determined by | Limit it by |
|---|---|---|
| Storage | Volume and retention period | Lifecycle rules and colder classes for old data |
| Requests | Number of objects and read frequency | Bundling small objects and using caching |
| Outbound traffic | How much data leaves the service | CDN, compression and processing close to the data |
| Versions and replication | Change frequency and number of copies | Limiting retention on old versions |
| Restore and exit | Size of the dataset | Calculating restore and exit scenarios in advance |
Who is it not ideal for?
- A choice based solely on storage price does not suit workloads with many requests or a lot of outbound traffic.
- For small, stable datasets, the time spent on an extensive cost model often does not outweigh the difference between providers.
- If you work with strongly fluctuating volumes, use scenario ranges instead of a single average.
Frequently asked questions
Why is my bill going up while my storage volume stays the same?
With the same volume, requests or outbound traffic may increase, or the volume of old versions may be growing. Check the breakdown per cost item.
Is cold storage automatically cheaper?
Only if the data is rarely read. Retrieval costs, delay and minimum retention periods can cancel out the advantage with regular use.
What is the difference between inbound and outbound traffic?
Inbound traffic is data you send to the service; that is often exempt from charges. Outbound traffic leaves the service and is more often metered separately.
How do I handle deletion and retention?
Set retention deliberately. Without lifecycle rules, old versions remain and you keep paying for data that nobody needs any more.
