libSQL
maintenanceby Turso · since 2022 · also known as libsql, sqld
Turso's open-contribution SQLite fork with native vectors, a network server and embedded replicas.
maintenance. Turso has shifted development to Turso Database (Rust rewrite) and recommends it for new projects; libSQL still gets fixes and releases (0.10.0, Oct 2026).
Overview
libSQL is an open-source, open-contribution fork of SQLite created by Turso (formerly ChiselStrike) in 2022, because upstream SQLite does not accept outside patches. It keeps the SQLite file format and C API while adding a network server (sqld) with HTTP and WebSocket protocols, embedded replicas that sync a local copy from a remote primary, native vector columns with DiskANN indexes, ALTER TABLE extensions and WASM user-defined functions. It powers the classic Turso Cloud and many edge deployments. Turso now points new projects to Turso Database, its Rust rewrite, so libSQL receives fixes and occasional releases rather than major new features.
Strengths & trade-offs
Strengths
- +Drop-in SQLite compatibility with a network server added
- +Embedded replicas give microsecond local reads synced from a remote primary
- +Native vector type and ANN index without extensions
- +Open to outside contributions, unlike upstream SQLite
- +Database-per-tenant pattern is cheap and practical
Trade-offs
- −Development focus has moved to Turso Database
- −Still single-writer per database
- −Divergence from upstream SQLite means extensions and tools may lag
- −Self-hosted sqld has less documentation than Turso Cloud
Great for
- +Edge and serverless apps needing SQLite over the network
- +Per-tenant databases in SaaS
- +Local-first apps with synced embedded replicas
- +Small RAG and semantic-search apps using native vectors
Think twice for
- −New greenfield projects (Turso recommends Turso Database)
- −Write-heavy concurrent workloads
- −Large analytical datasets
Capabilities
Native or official first-party support · 12 of 25 tracked
Scale & consistency
- Comfortable data size
- Small · ≤ 100 GB
- Horizontal scaling
- Manual
- Multi-region
- Read replicas
- Transactions
- Full ACID
- Consistency
- Strong, Eventual
- Schema
- Flexible
- Architecture
- Embedded, Client server, Primary replica
- Query languages
- SQL
Single primary per database; scale by using many small databases (per tenant) and embedded read replicas.
Deployment
Ecosystem
Alternatives to libSQL
Ground-up Rust rewrite of SQLite with concurrent writes, async I/O, CDC and vector search.
libsql vs turso-database →The in-process SQL engine that ships in every phone, browser and OS: one file, zero servers.
libsql vs sqlite →Managed SQLite-compatible cloud for database-per-tenant apps, with embedded replicas and offline sync.
libsql vs turso →Serverless SQLite for Cloudflare Workers, priced per row read and written, with read replicas and time travel.
libsql vs cloudflare-d1 →Lightweight distributed database that replicates SQLite over Raft behind a simple HTTP API.
libsql vs rqlite →Real PostgreSQL compiled to WebAssembly: an embeddable Postgres for browsers, Node, Bun and Deno.
libsql vs pglite →libSQL FAQ
What is libSQL?
libSQL is a relational database by Turso, first released in 2022. libSQL is an open-source, open-contribution fork of SQLite created by Turso (formerly ChiselStrike) in 2022, because upstream SQLite does not accept outside patches. It keeps the SQLite file format and C API while adding a network server (sqld) with HTTP and WebSocket protocols, embedded replicas that sync a local copy from a remote primary, native vector columns with DiskANN indexes, ALTER TABLE extensions and WASM user-defined functions. It powers the classic Turso Cloud and many edge deployments. Turso now points new projects to Turso Database, its Rust rewrite, so libSQL receives fixes and occasional releases rather than major new features.
Is libSQL open source?
Yes. libSQL is open source. License: MIT License.
Does libSQL support ACID transactions?
Yes. libSQL supports full ACID transactions, with strong, eventual consistency.
Does libSQL scale horizontally?
libSQL has no built-in sharding; scaling out means partitioning data in your application. It is comfortable at small scale (≤ 100 GB). It supports cross-region read replicas.
How can I run libSQL?
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 libSQL best for?
libSQL is a strong fit for edge and serverless apps needing SQLite over the network; per-tenant databases in SaaS; and local-first apps with synced embedded replicas. Think twice for new greenfield projects (Turso recommends Turso Database).
What are the best alternatives to libSQL?
Common alternatives to libSQL include Turso Database (Limbo), SQLite, Turso, Cloudflare D1 and rqlite. The right choice depends on your workload, scale and hosting; WhichDB's smart match ranks them against your requirements.
Is libSQL still maintained?
libSQL is in maintenance mode. Turso has shifted development to Turso Database (Rust rewrite) and recommends it for new projects; libSQL still gets fixes and releases (0.10.0, Oct 2026).
How popular is libSQL?
libSQL ranks #90 of 844 databases on the WhichDB Score (29.1/100), and #28 among relational databases. The score combines public adoption signals such as package downloads, GitHub activity, job posts and developer discussion.