Turso

Turso is built on LibSQL, a fork of SQLite maintained by the Turso team that adds network access and replication to the embedded database engine that powers hundreds of millions of applications. The pitch is that SQLite's simplicity — a single file, zero configuration, no separate server process — can be extended to a globally distributed, edge-deployed database without requiring developers to adopt an entirely different data model or query language. Turso instances can be replicated to dozens of points of presence around the world, allowing read queries to be served from an edge location close to the user while writes are serialised through the primary, dramatically reducing latency for globally distributed applications.

The architecture that enables edge replication introduces coordination requirements that single-instance SQLite does not have. Write operations must be acknowledged by the primary replica before they are considered committed, which means write latency is bounded by the network round trip to the primary's location. The Turso platform layer manages replica discovery, connection routing, and schema synchronisation across the replica set for each database. SDK-level abstractions in the official client libraries handle the routing logic, but they depend on Turso's platform API to discover the topology of the replica set correctly at connection time.

When Turso infrastructure has problems, the failure mode depends on which layer is affected. Platform API degradation prevents new connections from resolving the correct replica location, causing connection initialisation to fail before any query is attempted. Replication lag during high-write periods can cause reads from edge replicas to return stale data, a correctness issue rather than an availability one. The Turso console and CLI — used for database provisioning, schema inspection, and token management — can be unavailable independently of the database service. Write failures on the primary surface as database errors in the application and do not automatically fall back to reads.

Outage.gg tracks Turso service status using community reports from developers. If connections are failing, the CLI is returning errors, or replica latency has increased unexpectedly, the live status page shows what others on the platform are experiencing.