Sovereign by default, deployed in your cloud.

Public sector data carries strict residency, control, and auditability requirements. Per-database residency keeps data in-jurisdiction, BYOC keeps it inside your own cloud account, and per-database encryption keeps it under keys you hold.

Why Turso fits

Residency per database

Data lives only in the jurisdictions you allow.

Your cloud, your controls

BYOC deployment runs Turso inside your own AWS, GCP, or Azure account.

Auditability and recovery

Audit logs and point-in-time restore support oversight and continuity requirements.

SOC 2 Type II, per-database encryption with customer-held keys, BYOC deployment

Build fast, isolate easily

Deploy Turso inside your own cloud account in minutes, with residency and keys under your control.