SQLite is the most deployed database in the world and the right default for anything embedded, local-first, or single-node. Public domain, zero-config, one file, and battle-tested everywhere from phones to aircraft. The single-writer constraint is real, but WAL mode and the libSQL, Turso, and Cloudflare D1 wave have pushed it into edge and read-heavy production work it could not reach before. Reach for Postgres when you need concurrent writers at scale.
- Public domain, no license, no server, no config to run
- The most widely deployed database engine on the planet
- Single file on disk: trivial to copy, ship, back up, and embed
- Famously tested: millions of test cases per release line
- WAL mode plus libSQL and D1 extend it to edge and production
- One writer at a time: heavy concurrent writes hit a wall
- No client-server model: not built for shared remote access
- Coarse types and looser constraints than Postgres by default
- Scaling out means libSQL, Turso, or D1, not stock SQLite
- Limited ALTER TABLE and no native user or role management
SQLite is a small, fast, self-contained SQL database engine that runs inside the application that uses it, with no separate server process and no configuration. The entire database lives in a single ordinary file on disk, which makes it the default choice for embedded storage and, by some distance, the most widely deployed database engine in the world.
Where it fits
SQLite is built into every major mobile operating system, most browsers, and countless desktop applications, so it likely already runs on every device a developer owns. Its sweet spot is anywhere a full database server would be overkill: embedded device storage, local-first and offline apps, desktop software, and test fixtures that need to spin up and tear down without a running service. Increasingly it also fits production: the libSQL, Turso, and Cloudflare D1 ecosystem has carried SQLite into edge and read-heavy server workloads that once demanded a client-server database.
Cost to adopt
SQLite is dedicated to the public domain. There is no license to accept, no fee, and no server to provision, run, or patch. The authors at Hipp, Wyrick and Company release all code and documentation into the public domain, and offer a paid Warranty of Title only for organizations that need legal proof of usage rights. The real cost is architectural, not financial. SQLite allows one writer at a time, so write-heavy concurrent workloads serialize behind a single lock. WAL (Write-Ahead Logging) mode relaxes this by letting readers proceed during a write, which covers most read-dominated apps. When write concurrency or shared remote access genuinely matters, the answer is either a client-server database or the SQLite-compatible edge layers (libSQL with Turso Cloud, or D1) that add replication on top.
How it compares
PostgreSQL, A full client-server database with rich types, strict constraints, and true write concurrency. Pick it when many writers share one database or you need advanced SQL features.
MySQL, The other default client-server relational database, widely hosted and well understood. Pick it for shared, networked access with concurrent writers, not embedded single-file storage.
Turso, A managed, SQLite-compatible platform built on libSQL, adding replication, edge distribution, and a hosted control plane. Pick it to take SQLite semantics into distributed production.
What changed recently
SQLite continues its steady, conservative release cadence, with version 3.53.2 shipping on 2026-06-03 on the long-running 3.x line. The bigger story sits around the engine rather than inside it. Turso is building a clean-room rewrite of SQLite in Rust (originally codenamed Limbo) with async I/O, built-in vector search, encryption, and MVCC-backed concurrent writes, currently in beta, while the production-ready libSQL fork it maintains powers Turso Cloud today. Cloudflare D1, generally available since late 2024, runs SQLite at the edge with a primary-replica model, and Litestream reached 0.5 with point-in-time recovery by streaming the write-ahead log to S3-compatible storage. Together these have driven a 2026 resurgence of SQLite in serious production.
Sources
- SQLite Home Page, sqlite.org, accessed 2026-06-05 (version 3.53.2, released 2026-06-03)
- SQLite Copyright and Public Domain Dedication, sqlite.org, accessed 2026-06-05
- Introducing Limbo: A complete rewrite of SQLite in Rust, turso.tech
- Cloudflare D1 Overview, developers.cloudflare.com, accessed 2026-06-05