Storage tiers exist because how often you touch data matters as much as how much of it you have. Paying hot-storage prices for files you open once a year is wasted spend; storing actively-served files in a cold tier means slow, sometimes costly retrieval right when you need them fast. Here's how to think about the trade-off.
The four tiers at a glance
| Tier | Best for | Typical retrieval | Relative cost |
|---|---|---|---|
| Hot | Actively served website/app data, live client sites | Instant | Highest |
| Cool | Data accessed weekly or monthly: recent backups, media libraries | Instant to seconds | Lower |
| Cold | Data accessed rarely: older backups, logs past their active window | Minutes | Lower still |
| Archive | Data you must retain but almost never touch: compliance records, closed accounts | Hours | Lowest |
Start from the question, not the data type
It's tempting to sort by file type ("put backups in cold, put site assets in hot") but the better question is: if I needed this file right now, how much would the wait matter?
- If a customer-facing page would break or slow down without it: hot.
- If it's a safety net you hope never to need urgently, but might need within a business day: cool or cold.
- If retrieving it in a few hours would still count as "fast enough": archive.
Use lifecycle rules instead of manual sorting
Most data gets colder over time on its own; a backup taken today is hot in the sense that you might restore from it tomorrow, but by week six you're very unlikely to need that specific snapshot quickly. Set a lifecycle rule so objects move automatically:
Example lifecycle policy
0–14 days: Hot
15–90 days: Cool
91–365 days: Cold
365+ days: ArchiveThis way you don't have to remember to reclassify anything; the storage tier follows the age of the object, and you only pay hot-tier prices for the window where speed actually matters.
A quick worked example
A hosting company storing 50 TB of client backups might reasonably split it: 5 TB hot (this week's backups, in case of an urgent restore), 15 TB cool (the last two months), and 30 TB cold or archive (everything older, kept for compliance). Mixing tiers this way, rather than putting all 50 TB in hot storage, is usually where the bulk of storage cost savings comes from, often more than switching providers alone.
Not sure how your data should be tiered?
Tell us about your data and access patterns in the questionnaire; we'll recommend a tiering setup as part of your quote.
Get a tailored quote