Turso
SQLite at the edge — libSQL fork with replication to 30+ regions, embedded-replicas pattern.
VISIT TURSOQuick facts
- CategorySQLite at edge
- EngineSQLite
- PricingFreemium
- LicenseMIT (libSQL is MIT)
- Created2022
- GitHub stars13.5k
- PostgresNo
- Edge-readyYes
Bundled features: Multi-region replication
What it is
Turso is SQLite at the edge — libSQL (a SQLite fork) replicated to 30+ regions globally with the embedded-replicas pattern (read locally, write through). Generous free tier, pay-per-row pricing. Used heavily for edge-rendered apps where read latency matters more than write strength.
Best for
- Edge-rendered apps where reads dominate writes
- Multi-region apps that want low-latency reads everywhere
- JAMstack-flavoured workloads with database-as-config patterns
When not to pick it
Skip Turso for write-heavy workloads — the embedded-replicas pattern is read-optimised. Skip for apps that need transactional guarantees across regions.
My take
Turso is the cleanest answer for edge-rendered SQLite. The embedded-replicas pattern is the right abstraction for read-dominant apps. Pricing model is the trade-off; pay-per-row gets surprising at scale.
Links
Compare Turso side-by-side
Similar tools you should also consider
If Turso is your pick — the next conversation is short
The 30-min call is where your database choice becomes a real architecture, a migration plan if you are switching, and a price range you can take to your stakeholders. Describe your stack, your scale, your data shape. I tell you whether Turso is genuinely your fit.