Turso

SQLite-lineage database platform for running very large numbers of small per-tenant databases, with an MIT-licensed engine.

As of 30 August 2026, Turso has a free plan and paid plans start at $4.99/month. Turso's argument is that a database per tenant is the cleanest isolation you can get, and SQLite makes one cheap enough to create a million of them. Softwr lists it under Databases.

Visit siteVisit Turso

Overview

What Turso does

Turso is a database platform built on the SQLite lineage. Three related things carry the name. SQLite itself is the original engine. libSQL is Turso's MIT-licensed fork of SQLite, created because SQLite, though public domain, does not accept outside contributions. Turso Database is a newer rewrite of SQLite in Rust, also MIT, which runs in-process and has an experimental Postgres frontend. Turso Cloud is the managed platform that hosts databases of both kinds, adding branching, backups, analytics and an HTTP API. Embedded replicas are a distinctive part of the model: an application keeps a local copy of the database file, reads from it at local file speed, and forwards writes to the primary, with the replica synchronising afterwards. The distinguishing idea is per-tenant isolation at a price that makes it practical. In a shared Postgres, tenant isolation is a WHERE clause and a code review; a per-tenant database gives you a real boundary, per-tenant backup and restore, per-tenant deletion that actually deletes, and a noisy neighbour who can only affect themselves. Doing that on Postgres means either a schema per tenant, which becomes unmanageable in the thousands, or a cluster per tenant, which is unaffordable. A SQLite database is a file, so the marginal cost of the ten-thousandth is close to nothing. That is a genuine architectural capability rather than a repackaging, and it is why Turso appears in multi-tenant SaaS and in agent products that want a scratch database per session. The buyers are teams building multi-tenant applications and agent infrastructure who want isolation without operating a fleet of database servers. The trade-off is that you inherit SQLite's model wholesale. One writer per database means a single tenant's write concurrency does not scale, and there is no sharding a hot tenant. Cross-tenant queries do not exist, since ATTACH is deprecated on the cloud, so any report spanning customers has to be assembled elsewhere. Schema migrations fan out across every database and must be idempotent and resumable, and multi-database schemas, the feature intended to solve exactly that, is itself deprecated. So is Data Edge, the multi-region edge replication that was Turso's original pitch, which means a good deal of the writing about Turso describes a product that no longer works that way.

What people use it for

Multi-tenant SaaS where each customer gets their own database for real isolation, per-tenant restore and clean deletion
Agent or session infrastructure that creates a throwaway database per task and destroys it afterwards
Local-first and offline-capable applications where an embedded replica serves reads at file speed and syncs when connectivity returns
Embedding a SQLite-compatible engine in a product where the public domain original's closed contribution model is a problem

The honest half

Where it falls short

Concrete and checkable, so you can decide whether any of them matter to you. This is the half of a review a vendor will not write about Turso.

SQLite allows one writer per database, so a single tenant's write throughput cannot be scaled horizontally and a busy tenant serialises against itself with no sharding option.
Per-tenant databases mean per-tenant migrations, so every schema change becomes a fan-out job that must be idempotent and resumable, and multi-database schemas, the feature meant to solve this, is deprecated.
There are no cross-database queries; ATTACH is deprecated on the cloud, so any report or analytic spanning tenants must be assembled in your application or in a separate warehouse you also operate.
Data Edge, the multi-region edge replication that was Turso's original positioning, is deprecated, so a large share of the tutorials and articles describing Turso as an edge database describe behaviour you can no longer rely on.
Three engine lineages share the name, SQLite, the libSQL fork and the Rust rewrite, and the Rust engine is still maturing, so SQLite compatibility needs verifying against your specific pragmas, extensions and query patterns; the cloud already restricts journal_mode and busy_timeout and makes user_version read-only.

Cross-shopped

What people choose instead of Turso

Each pairing was judged by two reviewers asking whether a buyer would genuinely weigh the two against each other. The ones that failed were deleted rather than published.

Tursovs
Cockroach Labs
Cockroach Labs: The cloud-native distributed SQL database
Tursovs
PostgreSQL
PostgreSQL: The world's most advanced open source relational database
Tursovs
Airtable
Airtable: Create apps that perfectly fit your team's needs
Tursovs
Amazon Aurora
Amazon Aurora: MySQL and PostgreSQL-compatible relational database built for the cloud

Pricing

What Turso costs

Taken from the vendor's own pricing page. Prices move, so check before you buy.

Free

100 databases
5 GB storage
500M monthly rows read
Overage charges apply

Developer

$4.99 /mo

Unlimited databases
9 GB storage
2.5B monthly rows read
Overage charges $0.75/GB storage, $1 per billion rows

Scaler

$24.92 /mo

Unlimited databases
24 GB storage
100B monthly rows read
Overage charges $0.50/GB storage, $0.80 per billion rows

Pro

$416.58 /mo

Unlimited databases
50 GB storage
250B monthly rows read
Priority email and Slack support
BYOK encryption, HIPAA, SOC2 compliance
SSO access

Capabilities

Features

Per-tenant databases
Creating a database is cheap enough to give every customer, workspace or agent session its own
MIT licence
Both libSQL and the Rust Turso Database engine are MIT licensed with no competing-use restriction
Embedded replicas
A local copy of the database served at file speed, with writes forwarded to the primary and synchronised back
SQLite compatibility
Existing SQLite SQL, drivers and tooling largely apply, with documented exceptions on the cloud
HTTP access
SQL over HTTP for serverless runtimes that cannot hold a persistent connection
Branching
Copies of a database for development, testing or preview environments
Point-in-time restore
Backups and restore to an earlier moment, per database rather than per cluster
In-process engine
Turso Database runs inside the application process with bindings for Rust, JavaScript, Python and Java
Platform API
Programmatic creation, configuration and deletion of databases, which is what makes per-tenant provisioning practical
Experimental Postgres frontend
The Rust engine has begun speaking the Postgres protocol as well as SQLite's

Answered, with sources

Questions people ask

Each answer names the page it came from, so you can check it rather than take our word for it.

Is Turso just hosted SQLite?

Not exactly. It hosts databases built on the SQLite lineage: libSQL, an MIT fork of SQLite, and Turso Database, a newer Rust rewrite. The platform adds branching, backups, an HTTP API and programmatic database creation.

Can I really run a million databases?

That is the design goal and the platform API exists to make provisioning and deletion programmatic. The practical constraints are the ones that come with it: migrations fan out, and nothing can query across databases.

How do embedded replicas handle read-after-write?

Reads come from the local replica and writes go to the primary, so a read immediately after a write can return stale data unless you wait for a sync. Application code has to account for that rather than assume it.

What licence is it under?

libSQL and Turso Database are both MIT. Turso Cloud is a commercial managed service built on them, so the engine is genuinely open even though the platform is not.

Is Turso still an edge database?

No. Data Edge, the multi-region edge replication feature, is deprecated. The current positioning is per-tenant and embedded databases, and older material describing edge replication is out of date.

Keep looking

Where to go from Turso

Best Databases software for

Compare Turso with

Other Databases software

Airtable
Create apps that perfectly fit your team's needs
Free, then $20/month per editor11 researched notes
SurrealDB
Multi-model database combining documents, graphs, vectors and time-series
Free plan9 researched notes
Cockroach Labs
The cloud-native distributed SQL database
Free plan14 researched notes
PostgreSQL
The world's most advanced open source relational database
Free plan11 researched notes
Amazon Aurora
MySQL and PostgreSQL-compatible relational database built for the cloud
Free plan12 researched notes
MotherDuck
Serverless analytics data warehouse built on DuckDB
Free, then $250/mo9 researched notes
EMQX
Erlang MQTT broker for large IoT fleets, relicensed to BSL with production free use limited to one node
Free, then $234/mo12 researched notes
DuckDB
MIT-licensed analytical SQL database that runs inside your process, with no server, no dependencies and one writer at a time.
Free plan14 researched notes
Nile
PostgreSQL database platform built for multi-tenant SaaS applications
Free, then $15/mo11 researched notes
SQLite
Small, fast, self-contained SQL database engine
Free plan10 researched notes
Teradata
Long-established enterprise MPP data warehouse, rebranded in 2026 as the Autonomous Knowledge Platform, sold for cloud, on-premises and hybrid.
Pricing on request14 researched notes
Apache Kafka
Open-source distributed event streaming platform
Open source10 researched notes
Instaclustr
NetApp-owned managed service for Cassandra, Kafka, OpenSearch, PostgreSQL and Cadence with a bring-your-own-cloud model
Pricing on request12 researched notes
Knack
Hosted no-code database and web app builder priced by stored records and storage, with unlimited user accounts on every plan.
From $59/mo14 researched notes
LanceDB
Embedded retrieval library over the Apache 2.0 Lance columnar format, with proprietary Cloud and Enterprise tiers for serving at scale.
Pricing on request14 researched notes
Marqo
AI-native product discovery platform for ecommerce
Pricing on request11 researched notes
Ninox
The database for teams
Free plan10 researched notes
Nile
PostgreSQL database platform built for multi-tenant SaaS applications
Free, then $15/mo11 researched notes

Softwr does not host reviews and shows no star rating for Turso, because a rating we did not collect is not ours to publish. What is here is the pricing and platform detail from the vendor’s own pages, limitations we could state concretely, and alternatives a reviewer confirmed people weigh against it. Tell us if any of it is wrong.

Best Databases software alternatives

View all Databases software