Turso meters five separate dimensions of its edge database

The workload

Turso is built on libSQL, a fork of SQLite designed for replication, and its own pricing page, retrieved 16 September 2026, prices databases by count, storage, and row reads and writes rather than by server size. The workload before adopting it is reading that page closely enough to know which of those metered dimensions a given application will hit first.

What the documents show

Turso's pricing page states, verified, that the Free plan allows up to 100 databases, 5 GB of storage, 500 million monthly row reads, and 10 million monthly row writes, all at $0. The Developer plan, verified, costs $4.99 per month, includes 9 GB of storage (overage $0.75/GB), 2.5 billion row reads (overage $1/billion), and 25 million row writes (overage $1/million), with an unlimited database count. The Scaler plan, verified, costs $24.92 per month with 24 GB of storage, 100 billion row reads, and 100 million row writes included, each with its own overage rate. The page states, verified, that extra usage 'is billed automatically... at per-unit rates that drop as you scale up.' On latency, Turso's own homepage states, self-reported as the vendor's own claim rather than an independent benchmark, that embedded replication lets an application 'read and write locally with zero latency' by syncing a local copy of the database back to the cloud. Turso's documentation describes the mechanism, verified, as 'an embedded database engine that goes anywhere' with push/pull sync, without independently quantifying the homepage's latency claim.

The operating cost

A workload staying under the Free plan's 500-million-read, 10-million-write ceiling pays nothing, verified. A workload exceeding the Developer plan's included 2.5 billion reads pays $1 per additional billion, verified — as an editorial estimate, a founder running 5 billion monthly reads on Developer would owe roughly $2.50 in read overage alone (2.5 billion excess reads multiplied by $1 per billion), on top of the $4.99 base fee.

The stop condition

Turso's pricing page does not name a single stop condition; the editorial one is dimensional rather than a single number, because databases, storage, reads, writes, and syncs can each individually push a workload into overage independent of the others. The practical trigger is checking whichever dimension a given application actually stresses — a read-heavy analytics workload and a write-heavy logging workload will hit different ceilings first on the same plan, and the 'zero latency' claim describes local reads on an embedded replica, not the cost of writes syncing back to the cloud copy.

• Which metered dimension — databases, storage, reads, writes, or syncs — does this workload actually stress first?
• Has the vendor's 'zero latency' claim been checked against this application's own measured read times, rather than taken as given?
• At current growth, how many months remain before the Free plan's 10-million-write ceiling is reached?

This entry states only what Turso's own pages claim about Turso; it does not compare those limits to Cloudflare D1 or any other edge database, since no such vendor's page was opened for this entry.