What sets single-tenant and multi-tenant apart
Sooner or later, choosing a DAM system raises an architecture question that looks technical at first glance but has very practical consequences: does your company run on infrastructure shared with other customers: or on its own, dedicated instance?
In a multi-tenant setup, several customers share the same underlying infrastructure. Each company sees only its own data and users: the separation is logical, not achieved through separate systems. In a single-tenant setup, by contrast, a company gets its own instance, fully separated from other customers. Neither is a difference in quality: it's a deliberate choice between speed of onboarding and individual control, affecting isolation, configurability, update cadence, and operating cost.
Multi-tenant at Agravity GlobalDAM
Our multi-tenant model runs on shared, Azure-native infrastructure and is deliberately designed for a fast, straightforward start. Users: admin, editor, or viewer: are unlimited and included without separate licensing, storage is provided under a fair-use principle, and the full standard feature set of Agravity GlobalDAM is included, GDPR-compliant.
The key benefit: updates, new features, and security patches are rolled out centrally for all multi-tenant customers together: no rollout project of your own, no maintenance window you have to plan. That makes this model the natural starting point for companies that want to get productive quickly without making infrastructure decisions upfront. In exchange, you accept a shared UI and metadata language: multilingual interfaces remain reserved for the single-tenant and Enterprise models: plus sign-in through a shared login provided by Agravity (Microsoft Entra External ID) rather than a connection to your own Entra ID tenant, and the standard interface in Agravity's branding rather than your own.
Single-tenant and Enterprise: your own instance
Larger organizations often have different requirements for isolation and configuration than a shared setup can offer. That's exactly what our single-tenant model is for: a dedicated instance with its own test and production environment. Updates aren't rolled out to everyone automatically at once: they go to the test environment first, and only move to production after your approval. On top of that: single sign-on into your own Microsoft Entra ID tenant, your own branding (logo, colors, a custom domain on request), optional custom functions, no limits on users or storage, a multilingual UI with unlimited metadata languages, and an interactive AI admin guide.
The Enterprise model builds on the same principle and goes a step further: an additional dedicated development environment on request, full white-labeling with your own frontend templates ("bring your own frontend templates"), custom functions built in rather than optional, and, where needed, globally distributed infrastructure for teams across multiple locations. Technically, it isn't different software: it's the same Agravity GlobalDAM platform as the multi-tenant model, just provisioned, configured, and operated independently on its own update schedule.
Which model fits your company?
There's no one-size-fits-all recommendation: but there are a few guiding questions. If you want to get started quickly, have no particular regulatory or organizational requirements around isolation, and can work with one UI language, multi-tenant is the natural entry point. If your company needs its own instance for compliance or security reasons, wants to connect single sign-on to your existing Microsoft Entra ID landscape, needs its own brand identity instead of Agravity's standard interface, wants to use custom functions, or works internationally across multiple languages, that points toward single-tenant or Enterprise.
You'll find the full comparison of all three operating models, including feature scope, on our pricing page. If you're unsure which model fits your organization, your IT landscape, and your compliance requirements, we're happy to talk it through with you, without obligation.