Multi-tenant SaaS: what it is and when it makes sense (vs one system per customer)
September 20, 2026 · 3 min read · genbia
Single-tenant is a system for one company. Multi-tenant is a product that several companies use with their data separated, sometimes their brand, and one codebase you operate. The difference is not a Postgres flag. It is whether your business is a project… or software you sell.
Short definition
In multi-tenant each customer (tenant) sees only theirs: users, orders, config, billing. The vendor deploys once, patches once, and charges by usage or plan. In single-tenant each customer can have their instance, their fork, and a versioning nightmare.
If the case is “this clinic and nobody else,” do not force SaaS. If the case is “I will onboard ten similar operations,” the tenant is the product.
Comparison
| One customer (custom) | Multi-tenant SaaS | |
|---|---|---|
| Fit | Unique, regulated, or rare process | Same flow, many customers |
| Data | One database, one owner | Isolation per tenant, audits |
| Billing | Project / hours retainer | Plans, trials, limits |
| Roadmap | What that contract asks | What scales for everyone |
| Cost of each new customer | High (another project) | Onboarding, not a rewrite |
When yes
- You already sold (or will sell) the same admin to more than one customer.
- The differentiator is the product, not an embedded consultant.
- You need product metrics: activation, churn, usage per tenant.
- You can say no to a custom that breaks the model.
The white-label delivery platform is this pattern: one base, many brands. The WhatsApp CRM too: several teams, one platform.
When no
- One owner and a process that changes every quarter.
- Data-residency rules that require a dedicated instance.
- The first customer demands a fork “because we are special” and there is no second customer.
Then the path is custom software, not a half-SaaS you cannot sell later.
What to design on day one (even if the MVP is thin)
- Tenant identity. Company, not a loose user.
- Permissions. Tenant admin vs staff vs you as operator.
- Limits. What happens if one tenant saturates the API.
- Backups and deletion. A customer leaves: what is wiped and what stays in logs.
- Onboarding. Creating a tenant cannot be an engineering ticket every time.
If AI and n8n come in, they hang per tenant (keys, WhatsApp, webhooks). A global workflow that mixes customers is a privacy incident.
How we approach it
We do not start with “FAANG architecture.” We start with: how many tenants in 12 months, and what they must not see of each other? That chooses schema, billing, and the MVP cut.
GENBIA designs multi-tenant SaaS when the business is the product. If the business is a system for one operation, we build custom and do not pretend it is a marketplace.