Residency and sovereignty as a default, per database.
Regulated workloads need data to live in specific places, under specific controls. When each customer or record set has its own database, residency becomes a property you set per database rather than a separate deployment you operate. One platform can serve many jurisdictions at once without commingling data.
How sovereignty works on Turso
Residency per database
Assign each database to a region-specific group, so data lives only where it is allowed to.
Customer-held keys
Per-database encryption with keys you control means data is unreadable without them.
Your cloud, your boundary
BYOC deployment keeps data inside your own AWS, GCP, or Azure account.
Mapping to requirements
Per-database residency maps to GDPR data localization and to national sovereignty rules. Per-database encryption and customer-held keys support HIPAA and similar regimes. SOC 2 Type II covers the controls behind the managed service. Because the controls attach to each database, you can prove that a given customer's data never left a given jurisdiction.
Compliance signals SOC 2 Type II, GDPR, HIPAA-ready, BYOC on AWS, GCP, and Azure.
Try Turso for yourself
Spin up your first database in under a minute on the free Starter plan, or fork the open-source Turso Database on GitHub.
