Multi-tenant forced onto a customer that needed isolation
Logical separation inside a shared system, presented as sufficient when the customer actually required physical isolation.
SAAS PLATFORMS · SINGLE-TENANT
A dedicated instance, not a scoped slice of a shared one
Single-tenant means each customer gets their own isolated instance of the application and database, rather than sharing infrastructure with every other customer. Nothing about that deployment is touched by another customer's traffic, data or downtime.
THE RANGE OF PRACTICE
What isolation forced onto a shared system looks like, and what fully isolated looks like
Described by behaviour, not by a score.
Separate database, shared application layer
Some isolation exists, but the running application itself is still shared infrastructure.
A dedicated instance, application and database both
Nothing about the deployment is shared with another customer's traffic, data or downtime.
WHERE WE SIT
Scoped honestly, not defaulted to multi-tenant
From
When a customer, a regulator or a contract requires complete infrastructure separation, single-tenant is scoped as the honest answer rather than a multi-tenant system presented as close enough. The trade-off is real: infrastructure cost per customer runs higher than a shared deployment, which is why the choice is made deliberately, not by default.
STRAIGHT ANSWERS
Questions about single-tenant architecture
The ones that come up before anyone signs anything.
Each customer gets their own isolated instance of the application and database, rather than sharing infrastructure with every other customer. Nothing about that customer's deployment is touched by another customer's traffic, data or downtime.
When a customer, a regulator or a contract requires complete infrastructure separation, not just logical separation inside a shared system. Some industries and some contracts do not accept "your data is scoped correctly inside a shared database" as sufficient, and single-tenant is the honest answer at that point.
No. The application code is the same, deployed as its own running instance per customer, not maintained as a fork per customer that would drift apart over time. One codebase, many isolated deployments.
More per customer, because infrastructure is not shared. From
Send us your website address. We will tell you what is wrong with it.
A technical review covers speed, security, how search engines see your platform, and what your current setup really costs each year. Two days, no charge, no obligation.