Multi-Tenancy

Multi-tenancy is an architecture in which one running instance of an application serves many customers, or tenants. Each tenant sees its own data and settings as if it had a private system, but the underlying compute, storage, and code are shared. It is the dominant model for software-as-a-service.

How It Works

Isolation can be implemented at several levels. A shared database with a tenant identifier column is the most efficient but requires careful query scoping. A schema-per-tenant approach gives stronger separation within one database. A database-per-tenant or even cluster-per-tenant model maximizes isolation at higher cost. Many systems mix these, placing large or regulated tenants on dedicated resources while pooling smaller ones. Access control, encryption keys, and request routing all become tenant-aware, and every data path must enforce that one tenant can never read another's data.

Why It Matters

Multi-tenancy drives the economics of SaaS. Sharing infrastructure across many customers cuts per-customer cost, simplifies updates since everyone runs the same version, and improves utilization. The trade-off is risk and complexity: a bug or misconfiguration can leak data across tenants, a noisy tenant can degrade others' performance, and tenant-specific customization is harder. Strong isolation, per-tenant rate limiting, and rigorous testing are essential. The opposite model, single-tenancy, gives each customer a dedicated instance for maximum isolation and customization at higher operational cost.

Related Terms

Multi-tenancy underpins platform-as-a-service and serverless offerings, and intersects with virtual private clouds and security controls for isolation.