Isolated tenant platform
Multi-tenant model where each customer has its own database, not a tenant_id column in shared tables.
Detail
There are three classic multi-tenancy models: (1) shared database with a tenant_id column on every table, (2) schema-per-tenant in a shared database, (3) database-per-tenant. cifraHQ Enterprise chose the third. It is more expensive in infrastructure, but the only one offering real isolation: a buggy query cannot read another customer’s data, backups restore independently, upgrades schedule per tenant, and regulators accept more easily that data does not mix. The tenant_id column is doomed to be forgotten in some query; physical isolation is not. This matters in LATAM for data localization requirements and the concentration of customers in regulated sectors (financial, healthcare, government).
How does cifraHQ model Isolated tenant?
Let’s schedule a 45-minute technical session with your team to see it in product.