itsez.dev

Turso

Globally distributed edge SQLite database, built on libSQL.

sqliteedgedistributed
Websiteturso.tech
CategoryData & backend
PricingFreemium
Card requiredNo
Open sourceYes

ABOUT

What is Turso?

Turso brings SQLite to the edge via libSQL, a compatible fork that adds HTTP access, multi-region replication and database sync. Especially useful for multi-tenant architectures where each user has their own database.

BEFORE YOU SIGN UP

What you should know

500 free databasesThe free plan includes 500 instances, making it ideal for multi-tenant or per-user database architectures.
100% SQLite compatibleUses the same API as standard SQLite. Any existing SQLite driver works without changes.
Best for read-heavy appsReads are served from edge replicas, but for write-heavy concurrent workloads other options may be a better fit.
Writes go through a primary nodeWrites are not distributed. All go to the primary node, which can add latency if the client is in a different region.

COMMUNITY

From the forums

In r/sqlite the discussion is interesting: people value the concept of distributed SQLite and the generous free tier for edge projects. The rewrite in Rust quickly generated 9k GitHub stars. The doubts are about production maturity and whether the libSQL model has a future against cloud Postgres.

— Community sentiment · Reddit

ABOUT US

Honest, independent, no fluff.

No paid placements. Just a clear look at what this does, what it costs, and what to know before you commit.

Read more

FAQ

Questions, answered.

How is Turso different from regular SQLite?

Turso uses libSQL, a 100% compatible SQLite fork, with distributed replication, HTTP access and multi-region sync built in.

Is it a good fit for write-heavy apps?

It is ideal for read-heavy, write-light workloads. Writes go through a primary node, which can add latency in write-intensive patterns.