Turso Database (Limbo)
activeby Turso · since 2024 · also known as Limbo, tursodb
Ground-up Rust rewrite of SQLite with concurrent writes, async I/O, CDC and vector search.
Overview
Turso Database, which began in late 2024 as the Limbo project, is an in-process SQL database written in Rust that aims for full SQLite compatibility (file format, SQL dialect and C API) while adding what SQLite lacks: MVCC with BEGIN CONCURRENT for parallel writers, io_uring-based asynchronous I/O, change data capture, encryption at rest, vector functions and Tantivy-powered full-text search. Its bytecode VM is designed to host multiple frontends, and a PostgreSQL dialect and wire-protocol frontend is now in development. Turso recommends it for new projects and is building its cloud around it, but it is still pre-1.0, so treat production use as early-adopter territory.
Strengths & trade-offs
Strengths
- +BEGIN CONCURRENT MVCC allows multiple concurrent writers, unlike SQLite
- +Memory-safe Rust codebase with deterministic simulation testing
- +Asynchronous I/O (io_uring) suited to modern servers and the browser
- +Built-in CDC, encryption and full-text search without extensions
- +Reads existing SQLite database files
Trade-offs
- −Pre-1.0: compatibility gaps and on-disk format changes are still possible
- −Smaller extension ecosystem than SQLite
- −Limited production track record
- −Postgres frontend is experimental
Great for
- +New embedded/edge apps that want SQLite plus concurrent writes
- +Local-first apps syncing to Turso Cloud
- +On-device vector search for AI features
- +Browser apps via WebAssembly
Think twice for
- −Mission-critical production systems needing proven stability today
- −Distributed multi-node deployments
- −Apps depending on niche SQLite extensions
Capabilities
Native or official first-party support · 13 of 25 tracked
Scale & consistency
- Comfortable data size
- Small · ≤ 100 GB
- Horizontal scaling
- None
- Multi-region
- No
- Transactions
- Full ACID
- Consistency
- Strong
- Schema
- Flexible
- Architecture
- Embedded
- Query languages
- SQL
In-process engine; sync to Turso Cloud for replication.
Deployment
Ecosystem
Alternatives to Turso Database (Limbo)
The in-process SQL engine that ships in every phone, browser and OS: one file, zero servers.
turso-database vs sqlite →Turso's open-contribution SQLite fork with native vectors, a network server and embedded replicas.
turso-database vs libsql →Managed SQLite-compatible cloud for database-per-tenant apps, with embedded replicas and offline sync.
turso-database vs turso →Real PostgreSQL compiled to WebAssembly: an embeddable Postgres for browsers, Node, Bun and Deno.
turso-database vs pglite →In-process columnar SQL database: the SQLite of analytics, running inside your app or notebook.
turso-database vs duckdb →Serverless SQLite for Cloudflare Workers, priced per row read and written, with read replicas and time travel.
turso-database vs cloudflare-d1 →Turso Database (Limbo) FAQ
What is Turso Database (Limbo)?
Turso Database (Limbo) is a relational database by Turso, first released in 2024. Turso Database, which began in late 2024 as the Limbo project, is an in-process SQL database written in Rust that aims for full SQLite compatibility (file format, SQL dialect and C API) while adding what SQLite lacks: MVCC with BEGIN CONCURRENT for parallel writers, io_uring-based asynchronous I/O, change data capture, encryption at rest, vector functions and Tantivy-powered full-text search. Its bytecode VM is designed to host multiple frontends, and a PostgreSQL dialect and wire-protocol frontend is now in development. Turso recommends it for new projects and is building its cloud around it, but it is still pre-1.0, so treat production use as early-adopter territory.
Is Turso Database (Limbo) open source?
Yes. Turso Database (Limbo) is open source. License: MIT License.
Does Turso Database (Limbo) support ACID transactions?
Yes. Turso Database (Limbo) supports full ACID transactions, with strong consistency.
Does Turso Database (Limbo) scale horizontally?
Turso Database (Limbo) does not scale horizontally; it runs on a single node, so you scale it up rather than out. It is comfortable at small scale (≤ 100 GB).
How can I run Turso Database (Limbo)?
You can self-host it, embed it in your application, use the vendor's managed cloud and run it at the edge. Managed offerings include Turso Cloud.
What is Turso Database (Limbo) best for?
Turso Database (Limbo) is a strong fit for new embedded/edge apps that want SQLite plus concurrent writes, local-first apps syncing to Turso Cloud and on-device vector search for AI features. Think twice for mission-critical production systems needing proven stability today.
What are the best alternatives to Turso Database (Limbo)?
Common alternatives to Turso Database (Limbo) include SQLite, libSQL, Turso, PGlite and DuckDB. The right choice depends on your workload, scale and hosting; WhichDB's smart match ranks them against your requirements.
How popular is Turso Database (Limbo)?
Turso Database (Limbo) ranks #126 of 844 databases on the WhichDB Score (24.1/100), and #40 among relational databases. The score combines public adoption signals such as package downloads, GitHub activity, job posts and developer discussion.