The pillars
Row-level isolation
Tenant separation enforced by the database on every query, not in the interface.
Immutable event history
Append-only, time-stamped records of key project and quote events, per tenant.
Granular roles
Per-tenant permission matrices, module by module.
Encryption
Data protected in transit and at rest, per modern standards.
The details
TENANT ISOLATION
Enforced at the database row on every queryEvery table carries a tenant key, and row-level security policies check it against the authenticated user. A cross-tenant read is not a bug we catch; it is a query the database refuses to run.
TESTING
Isolation is tested as a release gateA suite of 61 self-asserting isolation tests runs against the database, checking every table for row-level security and every policy for a tenant key. Any failure blocks release.
ACCESS CONTROL
Role-based permissions per tenantEach tenant controls its own permission matrix, module by module. Access checks run in the database on every query, never in the interface alone.
DATA OWNERSHIP
Your data is exportable on requestA full structured export, whenever you ask for one. Leaving is easy, which is why staying is a choice.
AVAILABILITY
Published in the open, with a rolling 90-day recordEach part of Ssabi is checked every five minutes from outside our own network, and the result is published at ssabi.com/status along with any incidents. The record starts the day it starts; Ssabi does not offer a service-level agreement, and does not quote a figure it has not measured.