---
title: Multi-Tenant Architecture
description: Software design pattern where multiple customers (tenants) share the same application infrastructure.
url: https://www.factualminds.com/glossary/multi-tenant-architecture/
publishDate: 2026-06-13
updateDate: 2026-06-13
---

# Multi-Tenant Architecture

> Software design pattern where multiple customers (tenants) share the same application infrastructure.

## Definition

**Multi-tenant architecture** runs one application instance serving many customers (**tenants**) while enforcing data and configuration isolation between them. It is the default economic model for SaaS: shared infrastructure amortizes cost across tenants. Isolation can be **silo** (separate resources per tenant), **pool** (shared resources with logical separation), or **bridge** (pooled standard tiers, siloed enterprise tiers). On AWS, isolation maps to account-per-tenant, database-per-tenant, schema/row-level separation, partition-key design in DynamoDB, or S3 prefix boundaries — each with different cost, compliance, and operational trade-offs.

## When to use it

- **SaaS products** where per-customer dedicated infrastructure would make unit economics impossible at scale
- Platforms with homogeneous workloads where tenants share the same feature set and upgrade cadence
- **Bridge models** when you need low-cost pooled tiers plus premium isolated tiers for regulated enterprise customers
- GenAI products serving many customers from shared inference infrastructure with strict per-tenant data boundaries

## When not to use it

- **Single-tenant enterprise deals** where contractually each customer receives dedicated infrastructure — that is single-tenancy, not multi-tenancy
- **Healthcare or fintech pool models** when regulation or customer contracts require hard isolation silos exceed what row-level security provides
- Teams without automated **tenant provisioning** — manual per-tenant infrastructure does not scale multi-tenant operations
- Workloads where noisy-neighbor performance in a shared pool violates SLAs for premium customers

## Tips

- Choose isolation model from **compliance and contract requirements first**, cost second — reversing the order forces painful re-architecture
- Enforce tenant context at the **lowest practical layer** — middleware tenant ID checks fail when one query bypasses the ORM
- Use **IAM-scoped roles or STS session tags** for silo models; partition keys and RLS for pool models on RDS/Aurora
- Instrument **per-tenant metrics** (latency, error rate, cost) before tenant count makes debugging impossible
- Plan **tenant offboarding and data deletion** workflows early — GDPR and enterprise contracts require provable erasure

## Gotchas

### Serious

- **Pool model data leaks:** A missing `WHERE tenant_id = ?` clause exposes another customer’s data — the classic SaaS incident pattern.
- **Compliance mismatch:** Pooling PHI or PCI data without assessor-approved controls fails audit even if engineering “trusts” the app layer.
- **Noisy neighbor at scale:** Shared DynamoDB tables or RDS instances without per-tenant throttling let one tenant exhaust capacity for all.

### Regular

- **Silo cost linearity:** Database-per-tenant silos simplify isolation but RDS management overhead grows with tenant count.
- Bridge tier migrations (pool → silo) need explicit upgrade paths — customers outgrow pools mid-contract.
- Feature flags per tenant without configuration governance create untestable combinatorial states.

## Official references

- [SaaS Lens — Well-Architected](https://docs.aws.amazon.com/wellarchitected/latest/saas-lens/saas-lens.html) — SaaS-specific architectural guidance
- [Tenant isolation strategies](https://docs.aws.amazon.com/wellarchitected/latest/saas-lens/tenant-isolation.html) — silo, pool, and bridge patterns on AWS

## Related FactualMinds content

- [SaaS Multi-Tenancy on AWS: Silo vs Pool vs Bridge Model](/blog/saas-multi-tenancy-on-aws-silo-vs-pool-vs-bridge-model/)
- [AWS for SaaS Companies](/industries/saas/)

## Related AWS Services

- generative-ai-on-aws
- aws-cloud-cost-optimization-services

## Related Posts

- saas-multi-tenancy-on-aws-silo-vs-pool-vs-bridge-model

---

*Source: https://www.factualminds.com/glossary/multi-tenant-architecture/*