Multi-tenant architecture
Tenant boundaries enforced at the data layer rather than trusted to application code remembering a filter.
The feature set is the part founders think about. The part that decides whether the business is operable is tenant isolation, billing that reconciles, usage metering you can defend on an invoice, and the ability to onboard a customer without an engineer being involved.
Fig. 01Multi-tenant architectureIllustrative
Typical stack
These three are extremely expensive to retrofit. Tenant isolation in particular determines your data model, your query patterns and your compliance story — changing it after launch means migrating live customer data.
An explicit isolation model. Shared schema, schema-per-tenant or database-per-tenant, chosen deliberately against your compliance and scale needs.
Billing that reconciles. Subscription state, usage records and invoices that agree with each other, because disputes are won with data.
Self-serve onboarding. Signup, provisioning and first run without manual steps, or your cost per customer never falls.
Operational tooling from the start. Support staff able to inspect a tenant's state without running SQL against production.
Tenant boundaries enforced at the data layer rather than trusted to application code remembering a filter.
Plans, trials, proration, upgrades, dunning and failed-payment recovery, integrated with a payment provider.
Accurate, auditable usage records that support consumption pricing and survive a customer challenging the invoice.
Signup, workspace provisioning, invitations and guided first run that do not require a human on your side.
Workspace roles, granular permissions and, where enterprise customers require it, SSO and audit logging.
An internal console for impersonation, plan changes and diagnostics, with its own audit trail.
Isolation and billing are architectural decisions, not features. They come before the feature list, because everything else is shaped by them.
Every engagement ends with artefacts you own outright and can hand to another team without calling us first.
The product and its infrastructure as code. Reproducible environments, in your accounts, under your control.
A documented isolation model. Written down and testable, so a future engineer cannot quietly break the tenant boundary.
Billing reconciliation tooling. The means to prove that what was metered, what was invoiced and what was collected agree.
An internal support console. So that answering a customer question does not require production database access.
It depends on what your customers will ask in security review. Shared schema is cheapest to run; database-per-tenant is easiest to defend and to delete on request. We make the recommendation against your actual buyers, not in the abstract.
No — we integrate a payment provider. Building subscription billing from scratch means owning tax, dunning and card compliance for no advantage.
Yes, starting with an assessment. The two things we look at first are how tenant isolation is enforced and whether billing reconciles, because those are the expensive problems.
We build the technical controls those audits look for — access control, audit logging, encryption, change management. We are not auditors and do not issue certifications; the audit itself is between you and an accredited firm.
Tell us who the customer is and how you intend to charge. Those two answers determine most of the architecture, and it is cheaper to get them right now.