Reference Glossary
Multi-tenant architecture
A software design where one shared instance of the application serves multiple customers (tenants), with each customer's data logically isolated but running on common infrastructure.
Why it matters in a DAM
Most cloud DAM vendors run multi-tenant architecture because it's how they keep subscription pricing affordable — one codebase and one set of servers serving many customers at once, rather than provisioning dedicated infrastructure per client. The practical consequence for a DAM buyer is that a platform-wide outage or bug affects every tenant simultaneously, and some highly regulated buyers specifically require single-tenant deployment instead, where their data runs on infrastructure not shared with other customers, even at a cost premium.
A worked example
Common mistake
Assuming 'cloud DAM' automatically means multi-tenant and therefore automatically insufficient for a compliance requirement — some vendors offer single-tenant cloud deployment as a distinct, higher-cost option, which is worth asking about explicitly rather than ruling out cloud DAM entirely based on an assumption.
Multi-tenant architecture means a single running instance of the DAM software — one codebase, one set of application servers — serves many different customer organizations at once, with each customer’s assets, metadata, and users kept logically separated within that shared system rather than each customer getting dedicated infrastructure of their own.
This is the default architecture behind most cloud DAM subscriptions because it’s economically efficient for the vendor: infrastructure costs are spread across many customers instead of provisioned individually per client, which is part of why cloud DAM subscriptions can be priced accessibly compared to standing up dedicated infrastructure. The isolation between tenants is logical, not physical — enforced in software through permissions and data partitioning, not by running on separate hardware.
The trade-off worth understanding before buying: a bug, outage, or security incident affecting the shared platform can, in principle, touch every tenant at once, which is why some regulated buyers (government, defense, certain financial and healthcare contexts) require single tenant deployment instead — their own dedicated instance, isolated from other customers even though it’s still vendor-hosted. Single-tenant deployment usually costs more and is typically offered only at enterprise pricing tiers, so it’s worth confirming explicitly with a vendor rather than assuming a ‘cloud DAM’ answer settles the question either way.
Frequently asked
What does multi-tenant architecture mean for a DAM?
One running instance of the DAM software serves many different customer organizations at once, with each customer's assets, metadata, and users kept logically -- not physically -- separated within the shared system.
Why do most cloud DAM vendors run multi-tenant architecture?
It's economically efficient: infrastructure costs are spread across many customers instead of provisioned individually per client, which is part of why cloud DAM subscriptions can be priced accessibly.
What's the risk trade-off of multi-tenant architecture?
A bug, outage, or security incident affecting the shared platform can, in principle, touch every tenant at once, since isolation between tenants is enforced in software rather than by separate hardware.
Who typically requires single tenant deployment instead of multi-tenant?
Regulated buyers -- government, defense, and certain financial and healthcare contexts -- who need their own dedicated instance isolated from other customers, even though it's still vendor-hosted.
Does "cloud DAM" always mean multi-tenant?
Not necessarily -- some vendors offer single-tenant cloud deployment as a distinct, higher-cost option, so it's worth asking about explicitly rather than ruling out cloud DAM entirely based on that assumption.
What's the cost difference between multi-tenant and single-tenant deployment?
Multi-tenant is generally lower cost per customer due to shared infrastructure, while single tenant carries a premium price and is typically offered only at enterprise pricing tiers.