What is multi-tenant architecture?
A setup where many customers share one application and database, kept apart by access rules rather than by separate infrastructure.
Multi-tenant — Multi-tenant architecture runs many customers on one shared application and database, separated by software rules rather than by separate servers. It is cheaper to operate and is how most SaaS is built.
Why it matters
A multi-tenant system keeps every customer's data inside the same running app, and often the same physical database. Code in the app, and usually access rules at the database layer, decide which rows each customer's users can see. This is the dominant way SaaS products are built. It is far cheaper to run one shared system for thousands of customers than to run a separate copy of the application for each one.
The trade-off shows up when a customer has real needs around keeping data apart. A contractual promise that their data never physically touches another customer's. A regulatory need for a dedicated environment. Multi-tenant systems can meet many compliance bars. They rely on the correctness of the access rules separating customers. A bug in that logic affects every tenant at once, rather than one. A common misunderstanding is assuming an "enterprise" tier means a separate database. In most multi-tenant SaaS products it means more seats or features on the same shared servers everyone else uses.
How multi-tenant systems separate customers
- 1
One application instance is deployed
One running copy of the software serves every customer.
- 2
Customer data shares a database
Most or all customers' records live in the same physical database.
- 3
Each row is tagged to its tenant
Records carry a tag linking them to the customer they belong to.
- 4
Access rules enforce separation
Queries are scoped so a user only ever sees their own tenant's rows.
- 5
Application logic reinforces the boundary
The app layer adds another check on top of the data layer's rules.
The mistake to watch for
Questions
- How is multi-tenant different from single-tenant?
- Multi-tenant runs many customers on one shared application and database, separated by software rules. Single-tenant runs each customer in a dedicated database and application instance, kept apart physically rather than only by access rules.
- Is multi-tenant less secure than single-tenant?
- Not inherently. It depends on whether the access rules that keep tenants apart are correct. A flaw in that logic can expose data across customers. That is a different risk from single-tenant's physical split.
- Why do most SaaS products use multi-tenant architecture?
- It is far cheaper to run and look after one shared system for many customers than to run a separate instance per customer. That keeps costs down and makes updates simpler to ship.