Turso vs Cloudflare D1 for Indie Developers (2026)

Verdict: If your app already runs on Cloudflare Workers, use D1: it is a binding, not a connection string, it costs nothing beyond the $5/mo Workers Paid plan at indie scale, and Time Travel backups are always on. If your app runs anywhere else, needs a database on the device, or will create a database per customer across runtimes, use Turso. Both are SQLite underneath, so the bigger decision is which runtime you are committing to.

Every price and limit below comes from Cloudflare's and Turso's own pages, checked on 15 Nov 2026. The opinions in between are ours and are marked.

TL;DR#

• D1 is part of Workers. Free gives 5 million rows read and 100,000 rows written per day; Workers Paid is "a minimum charge of $5 USD per month" and includes 25 billion reads and 50 million writes a month (D1 pricing, Workers pricing).
• D1 scales out, not up. "Each individual D1 database is inherently single-threaded, and processes queries one at a time", capped at 10 GB on Paid (D1 limits).
• Turso is runtime-agnostic. Free has 100 databases and 500 million rows read a month; Developer is $5.99/mo, or $4.99/mo billed yearly (Turso pricing).
• Turso can live on the device. Embedded replicas and the newer Turso Sync put a SQLite file next to your code (embedded replicas).
• Write-heavy apps favour Turso on list price; read-heavy Workers apps favour D1.

Disclosure: ZeroRaised publishes this comparison and is a launch site for bootstrapped products. ZeroRaised has no commercial relationship with Cloudflare or Turso and earns nothing if you sign up for either. Facts come from the linked sources as checked on 15 Nov 2026.

How this differs from our free database roundup#

Our free database hosting guide already lines up the free tiers of both, side by side with eight other vendors. This post goes past the free tier: paid plans, architecture, backups, regions, local dev, lock-in and what each costs once you have customers. If you are still choosing between SQLite and Postgres at all, start with our free Postgres database guide or PocketBase vs Supabase instead.

Architecture: a binding vs a database you dial#

Cloudflare D1#

D1 is reached from a Worker through a binding in your Wrangler config. Cloudflare lists three ways to query it: the Workers Binding API, the REST API and Wrangler commands, and notes that the "REST API primarily interacts with the control plane" (Query D1). In practice your app code runs in a Worker.

Three design facts shape everything else (D1 limits):

• One query at a time per database. "Your maximum throughput is directly related to the duration of your queries." A slow, unindexed query blocks the rest.
• Small databases. The cap is 10 GB on Workers Paid and 500 MB on Free. Cloudflare says D1 "is designed for horizontal scale out across multiple, smaller (10 GB) databases, such as per-user, per-tenant or per-entity databases."
• Lots of them. Workers Paid allows 1,000,000 databases per account, the first 100,000 included; Free allows 10.

Read replication. D1 can create read-only copies "in every supported region" (ENAM, WNAM, WEUR, EEUR, APAC, OC), with no extra storage or compute charge. You must use the Sessions API (withSession()), which gives "sequential consistency for all queries in a session" through bookmarks, and Cloudflare notes it "is only available via the D1 Worker Binding and not yet available via the REST API" (read replication).

Turso#

Turso now has two parts, and the naming confuses people:

• Turso Cloud is the "Fully managed platform for Turso and libSQL databases, with branching, analytics, backups, and more" (Turso docs). You connect over the network from any runtime with a URL and auth token.
• libSQL is the open source SQLite fork behind the original service. Its README says it "is actively maintained, but new features are being developed in Turso" and "If you're starting a new project, you probably want to look into Turso" (libSQL on GitHub).
• Turso Database is the new engine, "A SQL database in Rust: SQLite-compatible", with BEGIN CONCURRENT for MVCC concurrent writes. Its FAQ says "we have not yet reached 1.0", that it "powers production applications today at multiple organizations", and advises keeping independent backups until 1.0 (Turso on GitHub).

Our read: libSQL plus Turso Cloud is the mature path today. Turso Database is promising, especially for concurrent writes, but treat it as pre-1.0 and keep your own backups, as Turso itself advises.

Storage. On AWS regions Turso uses "a diskless architecture where data is backed by a combination of S3-Express One Zone and S3", and "Commits are only acknowledged once data is safely stored" (Turso durability).

Embedded replicas and sync. This is Turso's biggest difference. "Embedded Replicas keep a local read replica of a Turso Cloud database", so reads come from a local file. Writes go to the remote primary, and the writing replica sees its own write immediately. They do not work in "serverless environments without a filesystem" (embedded replicas). For new projects Turso recommends Turso Sync, where reads and writes happen locally and you call push() and pull(); on conflicts "the strategy is "last push wins"" (Turso Sync usage).

Database per tenant or per agent. Turso pitches one database per AI agent for "Complete isolation between agents, independent scaling per agent, improved security" (agent databases). Note that the shared-schema feature, Multi-DB Schemas, "is now deprecated for all new users" (multi-db schemas), so you run migrations across tenant databases yourself.

Plans and limits side by side#

Cloudflare D1#

Sources: D1 pricing, D1 limits, Workers pricing. Free caps reset at 00:00 UTC. D1 charges no egress ("No."), and "If you are not running queries against your database, you are not billed for compute." Workers Paid also includes 10 million requests and 30 million CPU milliseconds a month; Free allows 100,000 requests per day. Other limits worth knowing: 30 second maximum query duration, 100 bound parameters per query and 2 MB maximum row size.

Turso#

Source: Turso pricing. Monthly prices are from the page's structured price data; yearly figures are the per-month prices it shows with annual billing. Enterprise is custom pricing.

The rule that bites: on Free, or a paid plan without overages enabled, "Once you exceed the limit on any single metric (storage, rows read, rows written, or syncs), your databases are blocked, even if the other metrics are still well under quota." Paid plans can turn on overages. "Idle databases cost only storage." And on deleted databases: "Only databases that were deleted while you were on a paid plan are guaranteed to be restorable" (Turso pricing).

Backups, regions and jurisdiction#

D1 Time Travel is "always on", restores to any minute in the window, and "Database history and restoring a database incur no additional costs." Restores are destructive: they overwrite the database in place and cancel in-flight queries. It "does not yet allow you to clone or fork an existing database to a new copy" (Time Travel).

Turso point-in-time restore runs from 1 day on Free to 90 days on Pro, as above.

D1 location. You can set a jurisdiction (eu, fedramp, or us) or a location hint (wnam, enam, weur, eeur, apac, oc). "Jurisdictions can only be set on database creation and cannot be added or updated after the database exists", and D1 runs no databases in South America, Africa or the Middle East (data location).

Turso regions. Turso Cloud "now runs in twelve regions" on AWS, as of 4 Nov 2026: Virginia, Ohio, Oregon, Canada Central, São Paulo, Dublin, Frankfurt, Stockholm, Mumbai, Singapore, Tokyo and Sydney (Turso blog).

Our read: if you sell to EU customers who ask where data sits, D1's eu jurisdiction is a one-line answer, but you must choose it on day one. Turso gives you named AWS regions (Dublin, Frankfurt, Stockholm), which some buyers find easier to put in a DPA.

Developer experience#

ORMs. Drizzle lists connectors for "Turso Cloud, Turso Database, Turso Database Serverless, Turso Database Sync" and "Cloudflare D1" (Drizzle SQLite), and says it "fully supports the Cloudflare D1 database and Cloudflare Workers environment" (Drizzle D1). If you have not picked an ORM yet, our Drizzle vs Prisma comparison covers the trade-offs.

Local dev. Cloudflare says wrangler dev now runs in local mode by default, powered by Miniflare and workerd; local and production data are separated, and data persists between runs. You can point a binding at production with "remote": true, but "Any changes you make when running against a remote database cannot be undone" (D1 local development). Turso recommends opening a local SQLite file with its SDK, or running turso dev, which "will start a local libSQL server"; without --db-file, "Changes will be lost when you stop the server" (Turso local development).

Lock-in and getting your data out#

Both are SQLite, which is the best lock-in insurance you can get: your schema and queries move.

• D1 export: npx wrangler d1 export <database_name> --remote --output=./database.sql writes schema and data to a .sql file. Virtual tables are not supported, and "A running export will block other database requests" (import and export).
• Turso export: turso db export <database> writes a snapshot to a local SQLite file, though "the exported file may not contain the latest changes" (turso db export).

The real lock-in is the runtime. D1 code calls env.DB.prepare() inside a Worker; moving off Cloudflare means rewriting your data layer and your hosting at once. Turso code uses a client you can run on Node, Bun, Deno, a VPS or a phone.

Licences (GitHub, checked today): libSQL and Turso Database are MIT licensed. Cloudflare's runtime, workerd, is Apache-2.0, but D1 itself is a managed service, not something you self-host (libSQL, Turso, workerd).

What it costs: three illustrative examples (ours)#

These are our own sums from the list prices above. They ignore Workers request and CPU charges beyond the included amounts and assume both vendors measure storage the same way, which you should check.

Our read: at indie scale both are cheap, and the difference is a few dollars. Writes are where prices split: D1 charges $1.00 per million rows written past 50 million, while Turso Scaler includes 100 million. Remember that a missing index multiplies rows read on both.

Decision table#

This is our editorial advice based on the facts above.

If you are still choosing a host, our Vercel vs Cloudflare Pages comparison usually settles this question for you.

Our pick#

• Already on Workers: D1. Pay the $5, enable read replication with the Sessions API when you have global users, and keep queries short because each database runs one at a time.
• Anywhere else: Turso Cloud on libSQL, starting on Free and moving to Developer before launch so a spike cannot block your databases.
• Local-first or mobile: Turso, with Turso Sync for new projects, after testing the "last push wins" conflict model against your data.
• Not sure yet: Use Drizzle and plain SQLite SQL so you can move between them later.

Frequently asked questions#

Is Cloudflare D1 free?#

Yes, on the Workers Free plan D1 gives you 5 million rows read and 100,000 rows written per day, 5 GB of total storage and 10 databases, with a 500 MB maximum per database. The caps reset at 00:00 UTC. For production most people move to Workers Paid, which costs a minimum of $5 per month per account and includes far larger monthly D1 allowances.

Is Turso free?#

Turso's Free plan is $0 per month with 100 databases, 5GB of storage, 500 million rows read, 10 million rows written and 3GB of syncs each month, plus 1 day of point-in-time restore. If you exceed any single metric on Free, your databases are blocked until you upgrade, even if the other metrics are under quota.

Can I use Cloudflare D1 outside of Cloudflare Workers?#

Only in a limited way. D1 can be queried through the Workers binding, the REST API or Wrangler, but Cloudflare says the REST API primarily interacts with the control plane, and the Sessions API needed for read replication is only available through the Worker binding. If your app runs on Vercel, Fly, a VPS or a phone, Turso is the more natural fit.

Does Drizzle ORM work with both Turso and D1?#

Yes. Drizzle's docs list connectors for Turso Cloud, Turso Database, Turso Database Sync and Cloudflare D1, and say Drizzle fully supports D1 and the Workers environment through drizzle-orm/d1. That makes Drizzle a reasonable way to keep your schema portable between the two.

Which is cheaper for a small SaaS, Turso or D1?#

It depends on your write volume. In our illustrative examples, a read-heavy app fits inside Turso Free or D1 for the $5 Workers Paid minimum, while an app writing 100 million rows a month (with 8 GB stored) costs about $57 on D1 versus $29 on Turso Scaler, because D1 charges $1.00 per million rows written above 50 million. Run your own numbers on both pricing pages.

Ship it, then launch it#

Whichever database you pick, the next job is getting users. Work through our product launch checklist for bootstrapped makers, then submit your product to ZeroRaised for free. For more no-VC build guides and comparisons, join the ZeroRaised newsletter.

Sources#

• Cloudflare D1 pricing, last checked 15 Nov 2026
• Cloudflare D1 limits, last checked 15 Nov 2026
• Cloudflare Workers pricing, last checked 15 Nov 2026
• D1 read replication, last checked 15 Nov 2026
• D1 Time Travel, last checked 15 Nov 2026
• D1 data location, last checked 15 Nov 2026
• Query D1, last checked 15 Nov 2026
• D1 local development, last checked 15 Nov 2026
• D1 import and export, last checked 15 Nov 2026
• Turso pricing, last checked 15 Nov 2026
• Turso docs introduction, last checked 15 Nov 2026
• Turso Cloud durability, last checked 15 Nov 2026
• Turso embedded replicas, last checked 15 Nov 2026
• Turso Sync usage, last checked 15 Nov 2026
• Turso agent databases, last checked 15 Nov 2026
• Turso multi-db schemas, last checked 15 Nov 2026
• Turso local development, last checked 15 Nov 2026
• turso db export, last checked 15 Nov 2026
• Turso Cloud now runs in Singapore and Frankfurt, last checked 15 Nov 2026
• Drizzle SQLite get started, last checked 15 Nov 2026
• Drizzle Cloudflare D1, last checked 15 Nov 2026
• libSQL on GitHub, last checked 15 Nov 2026
• Turso Database on GitHub, last checked 15 Nov 2026
• workerd on GitHub, last checked 15 Nov 2026