Spokes.wiki Search About
Software Application source ↗ source url updated Thu Jul 16 2026 00:00:00 GMT+0000 (Coordinated Universal Time)

Turso

An in-process, SQLite-compatible OLTP database written in Rust — a full rewrite of SQLite (not a fork), succeeding the earlier libSQL fork as the maker’s primary direction. Turso is the embedded end of this spoke’s embedded↔distributed spectrum: the database is a library linked into the application, no server process, the opposite pole from PlanetScale’s 768-server fleet.

Compatibility

Turso keeps SQLite compatibility at three levels — SQL dialect, on-disk file format, and the C API — though the team is explicit that 100% compatibility isn’t reached yet. libSQL remains production-ready, but Turso is the rewrite the project is betting on. Reliability is pursued through Deterministic Simulation Testing and Antithesis integration, aiming at SQLite’s own bar.

What the rewrite adds over stock SQLite

The Rust rewrite is a chance to add what SQLite lacks:

  • Concurrent writes — BEGIN CONCURRENT backed by MVCC (multi-version concurrency control), lifting the classic single-writer limit.
  • Native async I/O — on Linux via io_uring.
  • Change data capture (CDC) — real-time tracking of modifications.
  • Vector search (exact) and full-text search (via the tantivy library).
  • Multi-language bindings — Go, JavaScript, Java, .NET, Python, Rust, and WebAssembly.
  • Built-in MCP server in the CLI — nine standardized tools letting an AI assistant query, CRUD, and modify schema directly. (A seam to ../agentic-tooling-wiki: the OLTP engine reaching toward agents, mirroring seekdb‘s “state store for agents” from the other direction.)

Maturity

v0.7.0 (July 2026), MIT-licensed, ~22.9k★, ~85% Rust. Beta — not yet 1.0 — but already in production at Turso Cloud, Kin AI, and Spice.ai.

Why it’s here

Turso is a row-oriented embedded OLTP engine — the very sibling that ../analytical-databases-wiki carves out (DuckDB is also embedded, but columnar/OLAP; Turso is the OLTP embedded counterpart). It anchors the embedded pole of operational-databases and, with planetscale-768-servers, brackets the range from “database-as-a-library” to “database-as-a-fleet.”

operational-databases · online-transaction-processing · planetscale-768-servers · database-sharding · analytical-databases · synthesis

Related pages

Links to

Linked from