The Decision You Can't Take Back: Multi-Tenancy for SaaS
Most SaaS CTOs make the multi-tenancy decision implicitly. Here is how to make it deliberately — with the models, the real cost math at $3k ACV, a fillable ADR template, and a decision tree that maps your customer profile to the right answer.
At $3k ACV, the wrong tenancy model can cost you half your revenue.
Database-per-tenant can eat 50% of a $3,000 contract in infrastructure and ops. Shared schema is cheap — until your biggest tenant's data dwarfs everyone else's and it breaks, often inside 18 months. Schema-per-tenant is the hedge. But it only pays off if you know this before you write the first migration, because after that the fix is not a refactor — it is migrating live customer data.
The math, three ways
| Model | Infra + ops / tenant / yr | Share of a $3k contract | Where it breaks |
|---|---|---|---|
| Shared schema | ~$30 | ~1% | One missing tenant-filter leaks every customer; performance walls as the biggest tenant grows (~18 mo) |
| Schema-per-tenant | ~$180 | ~6% | Thousands of schemas strain a single database; the pragmatic hedge for most |
| Database-per-tenant | ~$1,500 | ~50% | Never on isolation; always on margin at low deal sizes |
Illustrative infrastructure + operations cost per tenant per year. Absolute numbers move with your cloud provider, tenant size, and compliance scope — the ratios are what bite.
Why trust this
We have built 50+ SaaS products — and rebuilt enough of them, after a tenancy call that was made implicitly by whoever shipped first, to know this pattern cold. This whitepaper is what we learned, written so you can make the decision deliberately while it is still cheap to make.
What you get
- The 8-page whitepaper — the models, their trade-offs, and a decision tree that maps your customer profile to the right tenancy model.
- A fillable ADR template — make the decision with your team and record why, so it is a choice on the record rather than an accident of the first commit.
- A one-page decision matrix — the quick reference to keep next to the architecture diagram.
- Bonus — a compliance breakdown — what GDPR and HIPAA actually require of your tenancy model, versus what you assume they do.
The compliance myth
Most compliance audits accept schema-per-tenant. If you jumped straight to database-per-tenant "for compliance," you are probably over-engineering — and paying that ~50% tax every month for isolation an auditor never asked for.