A real boundary, not a column in a table.
Most cloud software separates customers with a tenant ID and a careful `WHERE` clause. SimplCRM gives every customer their own database, so the separation survives a bug in the application.
- A database per customer
- Encrypted credentials
- Cloud or on-premise
SimplCRM isolates customers at the database level: each workspace has its own database rather than sharing tables filtered by a tenant column. Integration credentials are encrypted with per-workspace keys, significant record changes are recorded in an audit trail, and the whole system can run on your own servers instead of the cloud.
How it is built
- Tenant isolation
- A separate database per customer, provisioned at signup
- Credential storage
- Encrypted with per-workspace keys, decrypted only in use
- Passwords
- Minimum twelve characters, hashed; length preferred over character rules
- Access control
- Per person and per branch, enforced in reports and exports too
- Audit
- Who changed what and when, exportable on plans that include it
- Hosting
- Managed cloud, or on-premise on your own infrastructure
- Your own SMTP and IMAP servers, so mail never has to leave your provider
Why a database each
What is wrong with a tenant column?
Nothing, until one query forgets it. Shared-table multitenancy puts every customer’s rows in the same table and relies on the application adding a filter to every single query, for ever. One missed filter in one report is a data leak. A separate database makes the boundary the database’s job rather than the developer’s memory.
Does that make it slower or more expensive?
It makes provisioning slightly more work and backups more granular — a single customer can be restored without touching anyone else, which is usually an advantage. For businesses of the size SimplCRM serves, the isolation is worth considerably more than the overhead.
Where does the data physically live?
In the cloud deployment, on managed infrastructure; on-premise, wherever you put it. Businesses with contractual or policy requirements to keep customer data inside their own network run the same product on their own servers rather than a cut-down version of it.
Questions people ask
Is my data separated from other customers’ data?
Yes, at the database level. Every SimplCRM customer gets their own database rather than a shared table with a tenant column, so one customer’s query cannot read another customer’s rows even if the application has a bug. It is a boundary the database enforces, not one the code remembers to.
Can SimplCRM run on our own servers?
Yes. The same code runs as a hosted cloud workspace or on-premise inside your own network, for businesses whose policies or contracts require customer data to stay on their infrastructure.
How are integration credentials stored?
Encrypted, with per-workspace keys, so a mail password or an API secret is not readable from the database on its own. Credentials are decrypted only when a connection is being made.
Is there an audit trail?
Yes. Changes to significant records are recorded with who made them and when, and on plans that include audit export the trail leaves the system in a form you can hand to an auditor.
Questions from your IT team?
Send them to us. We would rather answer them before you buy than after.