OCI Object Storage offers three storage tiers. Standard is for hot, frequently read data at the highest storage rate and no retrieval fee. Infrequent Access lowers the storage rate in exchange for a per gigabyte retrieval fee and a minimum retention period, suited to backups and data read a few times a year. Archive lowers the storage rate furthest but requires you to restore an object before reading it, with a restore time measured in hours and a longer minimum retention, suited to compliance copies and cold logs. The buyer move is to match each dataset to the tier its real read pattern justifies and to automate the transitions with lifecycle policy rules, because manual tiering never keeps up. OCI egress is materially cheaper than the hyperscalers, but storage tiering is still where the recurring savings sit.
Here is what each tier costs, where naive tiering backfires, and how to automate it.
What does each OCI object storage tier cost you?
The three tiers trade storage rate against how quickly and cheaply you can read the data back.
| Tier | Best for | Storage rate | Retrieval | Catch |
|---|---|---|---|---|
| Standard | Hot, frequently read | Highest | None | None |
| Infrequent Access | Backups, occasional reads | Lower | Per GB retrieval fee | Minimum retention |
| Archive | Compliance, cold logs | Lowest | Restore first, hours | Longest minimum retention |
Rates and retention windows are indicative; verify against current OCI Object Storage pricing before you model a move.
When does Infrequent Access or Archive cost more, not less?
The retrieval fees and minimum retention periods are where naive tiering backfires. If you move data to Infrequent Access and then read it often, the retrieval fees can exceed what you saved on storage. If you put data in Archive and need it back inside the minimum retention window, you pay an early deletion penalty and wait hours for restore. The rule is to tier by genuine read frequency, not by age alone. Data that is old but still queried regularly belongs in Standard or Infrequent Access, not Archive.
How do you automate tiering with lifecycle rules?
OCI Object Storage lifecycle policy rules move or delete objects automatically based on age and prefix. Define rules per bucket: keep recent objects in Standard, transition to Infrequent Access after a set number of days, move to Archive after a longer period, and delete at the end of the retention requirement. Apply rules by prefix so logs, backups, and user uploads each follow the policy their access pattern justifies. Review the rules whenever a workload's read pattern changes, because a rule written for cold data that turns hot will quietly rack up retrieval fees.
A worked example
A Fortune 500 retailer kept years of clickstream and log data in Standard object storage on OCI because no one had set lifecycle rules. An access audit showed objects older than ninety days were read on fewer than one percent of days. Lifecycle rules moving data to Infrequent Access at ninety days and to Archive at one year, with deletion at the regulatory retention limit, cut object storage cost on that bucket by more than half, with retrieval fees a small fraction of the saving because the cold data was genuinely cold. Figures are verified against billing data and anonymised.
Frequently asked questions
How many storage tiers does OCI Object Storage have?
When does Archive storage cost more than it saves?
How do I move data between OCI storage tiers automatically?
Put every object in the right tier
We help enterprises set object storage tiering and lifecycle rules that match real access patterns, as an independent advisory that takes zero provider commissions and answers only to you. Our guarantee: we reduce your cloud spend or we reimburse our service fee, on a Fixed Fee or a no risk Gainshare basis. Download the OCI Universal Credits guide, read the deeper OCI cost optimization guide, and see reading your OCI bill line by line.
Put a defensible number on your cloud spend.
No provider in the room, no published price list. Tell us your footprint and we will scope the savings against your billing data — we reduce your cloud spend or we reimburse our service fee.
The Cloud Spend Navigator: what changed in cloud pricing, commitments, and FinOps — no vendor spin.