Loading...
Quick Definition
Multi-tenancy is an architecture where a single instance of infrastructure or software serves multiple customers or teams (tenants) while keeping their data isolated. It improves resource efficiency and cost-sharing but requires careful allocation to attribute shared costs fairly.
Multi-tenancy is an architecture where a single deployment of a system serves many customers, called tenants, with each tenant's data and configuration isolated logically rather than physically. It is the standard economics of SaaS: one platform, shared by all, instead of one stack per customer.
Sharing is what makes software margins work, since infrastructure is pooled and utilization stays high. The challenges are isolation, one tenant must never see another's data or degrade another's performance, and attribution: when everyone shares the same databases and clusters, knowing what each customer costs requires deliberate per-tenant cost measurement through metering and allocation.
Example. A SaaS company meters per-tenant usage of compute, storage, and API calls, then discovers its largest enterprise customer costs more to serve than it pays. The next contract renewal is priced on data instead of instinct.
Kubernetes namespaces and quotas are common isolation tools when tenants share clusters. The Cloud Unit Economics Guide covers per-tenant costing, and the fintech attribution case study shows attribution at work.
Logically: per-tenant identifiers in data, scoped permissions, quotas, and rate limits. Higher tiers sometimes get dedicated infrastructure.
A tenant whose workload degrades others on shared infrastructure. Quotas, rate limits, and QoS classes keep neighbors quiet.
Pricing, prioritization, and margins. Without it, your biggest customer may quietly be your least profitable