What is a single-tenant CRM?
One dedicated database per customer, instead of every customer's rows in the same table.
Single-tenant CRM — A single-tenant CRM runs each customer in a dedicated database and application instance rather than sharing one database across customers. It is chosen for data isolation, exportability, residency control and the ability to use the customer's own keys.
Why it matters
In a shared, multi-tenant CRM, every customer's data lives in the same database, kept apart by an account ID on each row. A single-tenant CRM instead gives each customer their own database and application instance. The customer's data is never in the same table as anyone else's, which changes what is possible on export, on residency, and on security review.
For an agency selling CRM access to clients, single-tenancy means a client's export on churn is the actual database, not a set of filtered CSVs pulled out of a shared store. For a buyer with a data residency requirement, it means the database's region is a real, settable fact rather than a claim about where a shared cluster happens to live. Single-tenant does not have to mean self-hosted: a vendor can provision and operate a dedicated instance per customer in its own cloud. In SalesCrew, each client runs in its own Supabase project, provisioned per instance.
What single-tenancy involves
- 1
A new customer signs up
Instead of a row in a shared table, a request for a new instance is created.
- 2
A dedicated database is provisioned
A separate Postgres project, isolated from every other customer's.
- 3
The application is configured against it
Branding, integrations and settings are set for that one instance.
- 4
The customer's data only ever lands there
Nothing they create is stored alongside another customer's records.
- 5
Export or deletion acts on the whole instance
A full database dump, or a full and complete removal, rather than a filtered query.
The mistake to watch for
Questions
- How is a single-tenant CRM different from a multi-tenant one?
- A multi-tenant CRM runs every customer on one shared database and application, separated by an account ID on each row. A single-tenant CRM gives each customer a dedicated database and instance, so isolation is enforced by infrastructure rather than by application logic alone.
- Does single-tenant mean the customer has to manage their own servers?
- No. A vendor can provision a dedicated database per customer and still run and maintain it in its own cloud infrastructure. The customer gets isolation and an exportable database without operating any servers themselves.
- Is single-tenant more expensive to run than multi-tenant?
- Generally yes, since dedicated infrastructure per customer costs more than sharing one database across many. Vendors that offer it usually price it into higher tiers rather than the base plan.