A software architecture where a single application instance serves multiple separate clients (tenants), each with isolated data and often customized configuration. The standard model for SaaS products.
Multi-tenant architecture is a software design pattern in which a single instance of an application serves multiple separate clients — called tenants — while keeping each tenant's data completely isolated from the others. The same codebase and infrastructure serve all clients, but each client's data, settings, and users are logically (or physically) separated. This is the standard architecture for SaaS products: every customer of Salesforce, HubSpot, or Shopify is a tenant on the same multi-tenant platform.
The contrast is single-tenant architecture, where each client gets a completely separate instance of the application — separate servers, separate databases, separate deployments. Single-tenant provides maximum isolation and can be customized per client, but at significantly higher infrastructure cost and maintenance overhead. Multi-tenant is far more cost-efficient at scale because infrastructure is shared across clients.
Multi-tenant architecture is a consideration for businesses that are building SaaS products, franchising an operational platform, or building an agency-model service that will serve many clients through the same software. For most internal business applications — tools for your own team and clients — a simpler single-tenant or shared-database approach is more appropriate and far less complex to build and maintain.
The key technical challenges of multi-tenant architecture: data isolation (ensuring tenant A can never see tenant B's data), customization management (allowing tenant-specific configuration without forking the codebase), and scaling (handling different load profiles from different tenants without one affecting others). These are solved problems, but they require deliberate architecture decisions from the start of the build.