Customer boundaries that are physical, not policy.
Financial products carry sensitive records and strict residency and audit requirements. With a database per customer or account, isolation is enforced by the architecture, encryption is set per database, and residency is a property of each store rather than a separate deployment.
Why Turso fits
Hard isolation
Each customer or account in its own database means no shared store to reach across.
Encryption and keys you control
Per-database encryption with customer-held keys supports strict data handling requirements.
Residency and audit
Place data in required jurisdictions and use point-in-time restore and audit logs to meet retention and recovery rules.
SOC 2 Type II, per-database encryption with customer-held keys, BYOC deployment
Build fast, isolate easily
Give every customer or account a database of its own in minutes, with encryption, residency, and audit built in.
