Neon vs Supabase
Of the 1,263 makers' products we know the database of, 573 chose Supabase (45%) and 96 Neon (8%); 5 use both. Among the 397 launched in 2026, Neon is in 11% and Supabase in 63%, against 6% and 33% of those launched in 2024 or earlier. They're different kinds of tool, managed database and backend platform, so the counts don't measure the same choice. At our calculator's default usage, Neon comes to $22 a month and Supabase $25, at list prices. On GitHub, 63 public pull requests moved projects from Neon to Supabase, and 170 the other way: more move to Neon, though fewer products use it in total.
Two sides of the database decision: managed database and backend platform. When each fits, what it costs, who moves from one to the other, and what makers who chose it say.
SupabaseBackend platformllms.txtMCPCLIIn Bolt, Lovable, Rork, v0Which fits you
- Your traffic is bursty or you run many preview deploys, and idle hours shouldn't cost much
Use it whenYou want every pull request's preview deploy to get its own copy of the database.
Trade-offCold starts after idle periods add latency to the first query, and heavy always-on workloads can cost more than a fixed server.
- You want the database, auth and file storage in one project, and plain SQL you can take elsewhere
Use it whenYou want one service for most of the backend and a SQL database you can take with you.
Trade-offAuth, storage and database in one vendor makes leaving harder later, and free projects pause after a week without activity.
At a glance
| Used by | 96 makers' products · 20 open-source projects | 573 makers' products · 90 open-source projects |
|---|---|---|
| Cost at default usagedatabase size 8 GB, data transfer 50 GB, document or row reads 10 million reads, document or row writes 2 million writes | $22/mo Launch | $25/mo Pro |
| Moved to it on GitHubpull requests since Oct 2024 | 170 from Supabase | 63 from Neon |
| Downloads | 3.7M/wk+32% vs npm | 25.4M/wk+91% vs npm |
| Pricing | Free tier; usage-based paid plans. · paid from $0.106 per CU-hour | Free tier (inactive projects pause); paid plans per project plus usage. · paid from $25/mo |
| Free tier | Yes | Yes |
| Open source | Yes · self-hostable | Yes · self-hostable |
| Incidents, 90 daysfrom its status page | no public status feed | 25+ (6 major) |
Which makers on your framework pick
Makers' products built with each framework that chose either one, for database.
| Framework | |||
|---|---|---|---|
| 48 | 171 | All 382 Next.js products' picks → | |
| 1 | 15 | All 73 React products' picks → | |
| 4 | 7 | All 27 Astro products' picks → | |
| 1 | 3 | All 13 FastAPI products' picks → |
New launches vs older products
A tool that came first has products from every year since, so its total runs ahead. Here is what products launched each year chose, as a share of those that made the database decision (by the year they launched on Product Hunt).
| Launched | Products | ||
|---|---|---|---|
| 2022 or earlier | 4% 1 | 19% 5 | 27 |
| 2023 | 11% 4 | 34% 13 | 38 |
| 2024 | 6% 16 | 34% 92 | 270 |
| 2025 | 7% 23 | 54% 174 | 323 |
| 2026 | 11% 43 | 63% 252 | 397 |
Cost as you grow
At 0.5 GB Supabase costs less ($0 vs $20); from about 1 GB Neon does ($20 vs $25); from about 50 GB Supabase does ($36 vs $37); from about 100 GB Neon does ($67 vs $70); from about 500 GB Supabase does ($345 vs $457). They're different kinds of tool — managed database and backend platform — so the prices don't buy the same thing.
Who moves from one to the other
Public pull requests on GitHub since Oct 2024 whose title says "Neon to Supabase" or the reverse — real code changes, by developers in general rather than makers only.
- feat(auth): cut over Supabase Auth to Neon Managed AuthMarcelo-teets/Motor-originac-srm · 2026-10-02
- Move backend from Supabase to Neon Postgres with Better Authsaadibnainan/edu-tracker · 2026-10-02
- Migrate CRM data layer from Supabase to NeonOverclock-Accelerator/Medline · 2026-10-01
- Migrate CRM routes from Supabase to Neon PostgresOverclock-Accelerator/overclock-tool-calling · 2026-10-01
- Migrate snapshot storage from Supabase to Neon Postgresafhaque/MeridianHealth-App · 2026-10-01
- Migrate LandmarketThai from Supabase to Neonlandmarketthai/landmarketthai · 2026-09-29
- Migrate from Supabase to Neon + host on Cloudflare Workersyannsalvo/nicophoto · 2026-09-28
- Migrate SpendWise from Supabase to Neon and Clerkderlinromero/SpendWise · 2026-09-28
- Migrate database from Supabase to NeonAakash22010/myPortfolio · 2026-09-27
- Migrate WakeMyWay accounts from Supabase to Neonyotamon/WakeMyWay · 2026-09-26
- chore(db): migrate database config from Neon to Supabasekurtlewis-ui/V-and-Sound-Inventory-System · 2026-09-30
- fix(db): move production Postgres from Neon to Supabase (v1.21.2)batashof/JobRadar · 2026-09-30
- Figma Make redesign + move sign-in and data off Neon to SupabaseGeorgeAkai/Lets_Carpool · 2026-09-29
- Switch the database from Neon to Supabase.opensourcepundits/cafe-food-hoppers · 2026-09-20
- Move the board's database from Neon to Supabaseyko79135/holyguide-test-board · 2026-09-19
- feat(db): migrate from Neon to self-hosted Supabasesebascm-dev/sebascm-dev.me · 2026-09-14
- feat: migrate database from Neon to Supabase with updated Prisma conf…codebreakers-gcek/codebreakersgcek · 2026-09-07
- Move email signups from Neon to Supabase; drop the dead routing proxyalpline-labs/alpline-web · 2026-09-06
- feat: move lead storage from Neon to SupabaseCorranForce/throughline-marketing · 2026-09-03
- Migrate workshop storage from Neon to Supabase server syncoomar11/aa · 2026-08-31
What makers say
Makers on using it for database, from Product Hunt and Starter Story interviews, each linked to the source. Products with a page of their own and fuller notes first.
Serverless Postgres with branching is a game changer for solo builders. Scale to zero means no idle costs, and the connection pooling just works. Perfect for an early-stage product.
Neon has been great for managing our database. The branching workflow and serverless Postgres made development smooth and allowed me to iterate quickly while building UseAgents.
Saturn runs all company data on Neon serverless Postgres with Drizzle ORM. 130K+ EDINET documents, instant branching for dev/prod. Perfect for serverless-first architecture on Cloudflare Workers.
One Postgres with RLS on every table is the reason a solo founder can ship contracts, invoices and a client portal without a backend team. Auth, storage and realtime came for free.
For powering our backend and database. Managing user uploads and conversion jobs efficiently is critical, and Supabase's real-time capabilities keep everything running smoothly! 🔥
Supabase is CatDoes' backend. We use their database, auth, storage, and real-time features. A platform like CatDoes requires a stable and scalable backend, and Supabase is providing that!
Loved and watch-outs
Themes that recur in makers' words and Hacker News comments, each linked to what it summarises.
- Postgres scales to zero when idle, so early products and staging databases cost almost nothing until traffic arrives. PHHN
- Branching copies the production database in seconds, so migrations and preview environments are tested against real data. PHPH 2HNHN 2
- The serverless HTTP and WebSocket driver fits Cloudflare Workers and Next.js routes without connection-pool trouble. PHHN
- Separating compute from storage costs latency and performance compared with Postgres on local NVMe. HNHN 2
- Parts of the stack, like autoscaling and some tooling, are not supported or openly licensed for self-hosting. HNHN 2
- With no built-in caching, crawler traffic can burn through the data transfer allowance quickly. HN
- One project covers Postgres, auth, storage and realtime, so a solo founder ships without stitching vendors or hiring a backend team. PHPH 2PH 3PH 4
- It is real Postgres with SQL, row-level security and pgvector rather than a proprietary store. PHPH 2PH 3PH 4
- Open source and self-hostable, which reduces vendor lock-in. PHPH 2HNPH 3
Who uses each
What makers pair each with
Neither quite right?
See the whole database decision →Questions
Neon or Supabase: which do makers choose?
Of the 1,263 makers' products we know the database of, 573 chose Supabase (45%) and 96 Neon (8%); 5 use both. Among the 397 launched in 2026, Neon is in 11% and Supabase in 63%, against 6% and 33% of those launched in 2024 or earlier. They're different kinds of tool, managed database and backend platform, so the counts don't measure the same choice. At our calculator's default usage, Neon comes to $22 a month and Supabase $25, at list prices. On GitHub, 63 public pull requests moved projects from Neon to Supabase, and 170 the other way: more move to Neon, though fewer products use it in total. Choose Neon if your traffic is bursty or you run many preview deploys, and idle hours shouldn't cost much; choose Supabase if you want the database, auth and file storage in one project, and plain SQL you can take elsewhere.
Can you use Neon and Supabase together?
5 makers' products we track use both, often one replacing the other or each for a different part of the product: oghunt, Vybe, xpander.ai, BetterPic, Storyville.
When should I pick Neon over Supabase?
Pick Neon if: Your traffic is bursty or you run many preview deploys, and idle hours shouldn't cost much.
When should I pick Supabase over Neon?
Pick Supabase if: You want the database, auth and file storage in one project, and plain SQL you can take elsewhere.
Which is cheaper, Neon or Supabase?
At database size 8 GB, data transfer 50 GB, document or row reads 10 million reads, document or row writes 2 million writes: Neon $22/mo (Launch), Supabase $25/mo (Pro), at list prices.
How do Neon and Supabase compare in cost as you grow?
At 0.5 GB Supabase costs less ($0 vs $20); from about 1 GB Neon does ($20 vs $25); from about 50 GB Supabase does ($36 vs $37); from about 100 GB Neon does ($67 vs $70); from about 500 GB Supabase does ($345 vs $457). Cheapest usable plan at each scale, at list prices.
Are people switching from Neon to Supabase?
Public GitHub pull requests since 2024-10-02: 63 from Neon to Supabase, 170 from Supabase to Neon.
