Alternatives to Turso
Compare the same workload. Check the differences behind the price.
Turso
SQLite-compatible databases priced by stored data and row operations.
$0 / month
Free
Official pricing · Checked 2026-10-05
Cost breakdown and exclusions
- Monthly subscription: $0
- Remote database calls only; no embedded replica sync.
- Embedded replica synchronization and enterprise features.
What this comparison covers
One database without replication or embedded sync. D1 and Turso use SQLite-compatible engines; Supabase uses PostgreSQL. These are cost alternatives, not interchangeable runtimes. Supabase models one Micro instance; its performance is not inferred from row counts.
Evaluating 4 products from 4 published in this category. USD monthly equivalents, before tax. Features and service compatibility need separate evaluation.
- Rows read
- 100,000,000 rows / month
- Rows written
- 1,000,000 rows / month
- Database storage
- 5 GB / month
- Database data transfer
- 10 GB / month
3 alternatives in this comparison
Cloudflare D1
Managed SQLite with row-based metering.
$5.00 / month
$5.00 more per month
- Workers Paid + D1: $5.00/month at reference usage.
- Includes the required $5 Workers subscription. If Workers is already in your stack, that subscription is shared. Free daily row limits are not modeled.
- Worker request/CPU usage to call the database and sharding across multiple databases.
Official source · Checked 2026-10-05
Compare with Turso →Supabase Database
PostgreSQL with dedicated compute and a bundled backend.
$25.00 / month
$25.00 more per month
- Pro · one Micro instance: $25.00/month at reference usage.
- Includes first Micro instance through the $10 compute credit. Fixed compute capacity; row volume alone cannot prove this instance is sufficient. Pro subscription can be shared with Supabase Auth.
- Larger compute, replicas, point-in-time recovery, provisioned IOPS and other backend features.
Official source · Checked 2026-10-05
Compare with Turso →Neon
Serverless Postgres with autoscaling, database branching, and scale-to-zero.
Not modeled
Savings cannot be established at this workload.
- Free Tier: Estimate unavailable at reference usage.
- Neon requires compute-unit hours. Row counts, storage and transfer do not establish compute use or Free plan eligibility.
- This pricing model is not supported.
- Compute usage and capacity are not collected by this category. No complete Neon price can be calculated.
Official source · Checked 2026-10-08
Compare with Turso →Questions before you decide
Are these drop-in replacements for Turso?
No compatibility is implied by sharing the Databases category. Check the selected plans, workload assumptions, API compatibility and required features before switching.