Storage tiering

Storage tiering is the practice of placing files on different classes of cloud storage depending on how often they need to be read, not how important they are. A DAM platform — or the cloud storage layer underneath it — typically defines a handful of tiers, from an always-on “hot” class down to a “deep archive” class that can take hours to retrieve from. Each step down the ladder cuts the per-gigabyte storage price substantially, and each step down also adds latency or a retrieval fee when someone actually needs the file.

For a DAM specifically, tiering matters because asset libraries grow in a very lopsided way: a small fraction of files (this quarter’s campaign, current product photography) get opened constantly, while the bulk of the archive — last year’s shoots, retired packaging, superseded video edits — sits untouched for months or years. Automatically moving that untouched majority to a cheaper tier is one of the few storage cost levers a DAM admin can pull without deleting anything or degrading the experience for active work.

The failure mode is applying tiering rules that only look at asset age, ignoring actual access patterns. A three-year-old brand guideline PDF or an ICC color profile that print vendors download every month is technically “old” but functionally hot. If it gets swept into a cold tier by a blanket age-based rule, every request for it now costs money and takes minutes instead of being instant — a frustrating regression that’s invisible until someone actually needs the file under deadline.

The concept holds across providers even though the tier names themselves differ: