What is a single-tenant CRM?
In a shared CRM, one missing filter in the vendor's code is all that sits between your deals and another company's.
Want to see it first? Book a demo
Single-tenant CRM — A single-tenant CRM is a CRM in which each customer's data lives in its own separate database, rather than as rows in a database shared with other customers. Its purpose is isolation you can point to: a copy of the data you can export whole, place in a region you choose and delete as one unit.
What changes when your data has its own database
Most cloud CRMs are multi-tenant. Every customer's records share one set of tables, and an account ID on each row keeps them apart. That works, but the wall is a rule in the vendor's code. In a single-tenant CRM the wall is the database itself.
You feel the difference at three moments. On export you get the real database, not a set of filtered CSV files. In a security review you can say where the data sits, because data residency is a setting on your own database. And when you leave, deletion removes one whole database rather than rows scattered across a shared one.
Agencies care most. If you run a CRM for each of your clients, single-tenancy keeps every client's records in a separate database. Handing a client their data means handing over one database.
Single-tenant vs multi-tenant vs self-hosted CRM
| Single-tenant (managed) | Multi-tenant | Self-hosted | |
|---|---|---|---|
| Where your data lives | Its own database | Rows in a shared database | Your own servers |
| What separates customers | Separate databases | Account ID and code rules | Separate installs |
| Who runs the servers | The vendor | The vendor | You |
| Export on leaving | A full database dump | The vendor's export tools | You already hold it |
| Region choice | Per customer | Per vendor cluster | Wherever you host |
How a single-tenant CRM sets up a new customer
- 1
An instance is requested
One per customer or client.
- 2
A database is created
In the region chosen at setup.
- 3
The app connects to it
Same app, pointed at that database.
- 4
Data only lands there
Nothing mixes with other customers.
- 5
Export or delete acts on all of it
A dump or a wipe of one database.
The mistake to watch for
Single-tenancy on every plan
SalesCrew gives each client instance its own Supabase project: Postgres, file storage and functions, in the region you pick at setup. Export is a full Postgres dump plus CSV from every list, and backups run daily. API keys sit in Vault inside that same project. It's included from Core at $299 a month with unlimited seats, as the pricing page shows.
Questions
- What is the difference between single-tenant and multi-tenant CRM?
- A multi-tenant CRM keeps every customer in one shared database, split by an account ID on each row. A single-tenant CRM gives each customer a database of its own. The separation then lives in the infrastructure rather than only in the application's code.
- Does single-tenant mean I have to host the CRM myself?
- No. A managed single-tenant CRM creates and runs your separate database in the vendor's cloud. You get isolation and a full export without managing servers. Self-hosting is a different choice that puts the servers on you.
- Why do agencies choose a single-tenant CRM?
- Each client's records stay in their own database, so no client's data sits beside another's. When a client leaves, you hand over one complete database. Regions can differ per client when their buyers need it.
- Is row-level security the same as single-tenancy?
- No. Row-level security is a database rule that filters which rows a user can see inside a shared table. Single-tenancy puts each customer in a separate database. Many single-tenant CRMs use row-level security too, to control what each user inside one customer can see.