Databases · working at 10,000 users · rates as read 29 Sept 2026
Take Supabase if you want a backend rather than a database: authentication, storage and realtime on the same bill and the same SDK, at $ 25 / month for Pro with every meter published as a rate you can multiply out. Take Neon if you already have a backend and want Postgres under it: it charges no plan fee at all on Launch ("Neon's paid plans don't require a minimum monthly spend or base fee"), bills $0.106 per CU-hour, and suspends compute when idle, so a staging database costs approximately nothing between deploys. The row that decides it is rarely price: at small scale both are free and at medium scale they are within a few dollars. It is whether the bundled auth and storage are things you will actually use, because on Neon you will pay for them somewhere else, and on Supabase you pay for them whether you use them or not. StackTab sells neither.
Priced for an app where 2% of users pay $20 a month, on the usage a user of that kind typically implies, on the cheapest plan of each service that can carry it.
| Service | |||
|---|---|---|---|
| NeonServerless Postgres that scales compute to zero and branches like git.verified 21 Sept 2026neon.com/pricing | $ | $ | $ |
| SupabasePostgres with auth, storage and realtime bolted on.verified 21 Sept 2026supabase.com/pricing | $ | $ | $ |
| PlanetScaleVitess-backed MySQL and Postgres with online schema changes.drifted, last true 10 Sept 2026planetscale.com/pricing | $ | $ | price not publishedPlanetScale Postgres · drifted |
| TursoSQLite on the edge, one database per tenant without the bill exploding.verified 21 Sept 2026turso.tech/pricing | $ | $ | $ |
- Sorted by the total at
- Serverless Postgres that scales compute to zero and branches like git.verified 21 Sept 2026neon.com/pricing
- 1,000 users
- $
7777 Launch - 10,000 users
- $
7777 Launch - 100,000 users
- $
241241 Launch
- Postgres with auth, storage and realtime bolted on.verified 21 Sept 2026supabase.com/pricing
- 1,000 users
- $
2525 Pro - 10,000 users
- $
2525 Pro - 100,000 users
- $
188188 Pro
- Vitess-backed MySQL and Postgres with online schema changes.drifted, last true 10 Sept 2026planetscale.com/pricing
- 1,000 users
- $
1515 PlanetScale Postgres · drifted - 10,000 users
- $
2121 PlanetScale Postgres · drifted - 100,000 users
- price not publishedPlanetScale Postgres · drifted
- SQLite on the edge, one database per tenant without the bill exploding.verified 21 Sept 2026turso.tech/pricing
- 1,000 users
- $
00 Free - 10,000 users
- $
00 Free - 100,000 users
- $
2525 Growth
A cell reading not published is not missing data. It means the vendor does not publish a rate at that usage on its own pricing page, so no honest figure exists to print.
Change any of those assumptions in the calculator.
Both are managed Postgres, both are excellent, and both will do everything a normal application needs. They are solving slightly different problems.
Neon sells Postgres as a primitive. Supabase sells a backend that happens to be Postgres.
- Scale to zero. Neon suspends compute when nothing is querying and bills storage plus the compute-hours you actually used. For an app with quiet nights, or for the twenty preview environments a team accumulates, that is a materially different bill than paying for an instance that idles.
- Bundled against unbundled. Supabase includes auth, object storage, realtime and edge functions on the same bill. If you would otherwise be paying Clerk and an S3 bucket, compare the whole stack rather than the database line: this is exactly what the recommender does.
- Branching. Neon branches a database the way git branches a repository, cheaply and instantly, and charges $0.002 per branch-hour. For a team running a database per pull request this is the feature, not a nice extra.
- The other two in the table. PlanetScale brings Vitess-scale online schema changes and now offers Postgres. Turso is SQLite at the edge and is priced for one database per tenant, which is a genuinely different architecture rather than a cheaper version of the same one.
| If | Then |
|---|---|
| You want a backend, not just a database | Supabase: auth and storage on the same bill is the point. |
| You have a backend and need Postgres under it | Neon: scale-to-zero and branching are worth more than bundling you will not use. |
| One database per customer | Turso: priced for exactly that shape. |
Yes, and it is a common pairing: Better Auth writes its tables into whichever Postgres you point it at, so you get your own user table with no auth bill on top. The recommender suggests exactly this combination when you ask to keep users in your own database.
On an idle or bursty workload, usually: Neon's compute suspends when nothing is talking to it and there is no base fee on the Launch plan, so the floor is close to zero. On a database that is busy all month, Supabase's flat $ 25 / month with $10 of included compute credit is often the cheaper shape. Neither is cheaper in general, which is why this page prices both rather than naming a winner.
Yes. Both are Postgres you can point any Postgres client at, run migrations against, and take somewhere else: which is the thing that separates this pair from a document store. Supabase is open source and self-hostable on top of that, which makes the option to leave credible rather than theoretical.
It means the compute behind the database suspends when there is no traffic and resumes on the next connection, so you are billed for CU-hours you actually used rather than for a server sitting idle. The cost is a cold start on the first query after a quiet period. On a staging or preview database that is free money; on a low-traffic production API it is a latency decision you should make deliberately.