Database

Turso vs Neon vs Supabase

Turso, Neon, Supabase side by side: price, free tier, who each one fits and when to skip it.
Item
What it doesHosted SQLite (libSQL) built for one small database per user, tenant or agent.Serverless Postgres that scales to zero and lets you branch the database like code.Postgres database with login, file storage, edge functions and realtime in one project.
Best forA multi-tenant SaaS that wants a separate database for each customer company without paying per database.A founder with several side projects, or one database per customer, who only wants to pay for the hours the database is actually running.A solo founder who wants login, database and uploads in one place, with a region close to their users so the app feels fast.
Skip it ifYou rely on Postgres extensions or tools your team already knows, like pgvector or Supabase.You want database, login and file storage in one mature package: Neon's login and storage are much newer than its Postgres.You plan to leave a free project idle while you validate, since free projects get paused after a week without activity.
SetupNeeds a developer. First database in minutes; one database per customer takes a day or two to automate.Needs a developer. A database ready to connect in minutes; wiring it into the app takes an afternoon.Needs a developer. Login and a first table in an afternoon; access rules and email setup take another day or two.
PriceFree; Developer $4.99/monthFree; Launch is pay-as-you-go with no minimumFree, then Pro from $25/month plus usage
What it costs in practiceA SaaS with 2,000 monthly active users, 3 GB of data and about 1,000 rows read per user a day reads about 60 million rows a month, well within the free 500 million: $0. To avoid being blocked at a limit, Developer is $4.99/month with overages at $1 per extra billion rows read (estimate).A SaaS with 2,000 monthly active users and a 3 GB database needs the Launch plan (free is 1 GB). On the smallest size (0.25 CU) running about 12 hours a day: 0.25 × 365 hours × $0.106 ≈ $10, plus 3 GB × $0.35 ≈ $1. About $11/month; kept on 24 hours a day it's about $20 (estimate).A SaaS with 2,000 monthly active users and a 3 GB database outgrows the free 500 MB, so it goes to Pro: $25/month, which already covers one Micro server, 100k users, 8 GB of disk and 250 GB of egress. Add $10 for a custom domain on login and you're at about $35/month (estimate, in dollars).
Free plan100 databases, 5 GB, 500 million rows read and 10 million written per month.100 projects, 1 GB per project and 100 compute hours per project each month.2 projects, 50k monthly users, 500 MB database and 1 GB of files; paused after a week idle.
Free tier100 DBs, 5 GB, 500M rows read/mo1 GB and 100 CU-hours per project50k MAU, 500 MB DB, 1 GB files
First paid planDeveloper: $4.99/monthLaunch: $0.106/CU-hour + $0.35/GBFree (Pro: $25/mo, 100k MAU included)
Database typeSQLite (libSQL)Serverless PostgresPostgres
Open sourceYes: yesYes: yesYes: yes
Before you build
  • "Rows read" counts every row the query touches, not just what it returns: a lookup on a column without an index reads the whole table.
  • On the free plan, going over any single limit (storage, reads, writes or syncs) blocks your databases until you upgrade.
  • Paid plans also block at the limit unless you turn on overages, which are off by default.
  • Aggregates like count or sum, joins and updates without an index all count a read for every row considered.
  • On the free plan the database always sleeps after 5 minutes idle, and you can't turn that off; the next query wakes it in a few hundred milliseconds.
  • When a free project runs out of its 100 compute hours, the database is suspended until the next month or until you upgrade.
  • Past 1 GB on a free project, inserts and updates start failing; your data is kept, but the app stops saving.
  • The free plan only lets you restore to a point in the last 6 hours; a mistake noticed the next day can't be undone there.
  • Free projects are paused after one week without activity, and you get only 2 free projects across all your organizations.
  • The built-in email only reaches members of your Supabase team, at about 2 emails an hour. Real users get no confirmation or reset email until you plug in your own SMTP.
  • Phone login doesn't send SMS by itself: you open an account with Twilio, MessageBird or Vonage and pay them per message.
  • The free plan has no automatic backups; Pro keeps 7 days, and point-in-time restore is an add-on of about $100/month.
  • The Pro fee is per organization, but each project runs its own server: every extra project adds compute (Micro is $10/month) on top.
Price checked

Checked on Oct 28, 2026 · official pricing

Checked on Oct 28, 2026 · official pricing

Checked on Oct 28, 2026 · official pricing

Prices are read from each official pricing page on the date shown and can change. Always confirm before signing up.

Popular comparisons

Faundr

Picked your tools? Build it with AI, safely.

Faundr keeps your project’s memory, blocks what can’t be undone and tells you if it’s safe to launch, inside Claude Code and Codex.