Skip to content

Multi-tenant architecture

Designed into the database from the start.

In brief

Multi-tenancy is a decision you live with for a long time. webbox picks the model on your isolation, compliance and cost requirements. Shared-schema with row-level security suits scale and low cost. Schema-per-tenant is the middle ground. Database-per-tenant is for a regulated customer who requires it. We then build tenant-aware routing, migrations and isolation tests, so the boundary between customers holds as the code changes.

Last updated

← part of SaaS Products

What we deliver

Model selection

Shared-schema, schema-per-tenant or database-per-tenant, chosen on isolation requirements and cost per tenant.

Isolation tests

Automated tests try to reach another tenant's data on every build, so the boundary is checked continuously.

Tenant-aware operations

Migrations, backups, restores and per-tenant data export that keep working as you grow from three tenants to a hundred.

Multi-tenant architecture: FAQ

Which tenancy model is right for us?
Shared-schema with row-level security fits most products and keeps per-tenant cost low. Move to schema or database per tenant when a customer contractually requires physical separation, or when tenants differ enormously in size. It is a cost and compliance trade, and we walk you through both sides.
Can you retrofit multi-tenancy onto our existing app?
Often, yes, but it is a sizeable job and careful scoping matters. We start by auditing where the app would need to know which tenant it is serving. Then we give you the cost before you commit.

More in SaaS Products

SaaS MVP development Subscription & usage billing API-first developmentSaaS scaling & compliance readinessWhite-label & partner editions

Talk to us about Multi-tenant architecture

Tell us the problem. We'll come back with a plan, a price, and who would build it.

Start a project Browse services
  • Free scoping call
  • Reply within 1 business day
  • No lock-in