Neon vs PostgreSQL
Of the 1,263 makers' products we know the database of, 98 chose PostgreSQL (8%) and 96 Neon (8%). Among the 397 launched in 2026, Neon is in 11% and PostgreSQL in 1%, against 6% and 7% of those launched in 2024 or earlier. They're different kinds of tool, managed database and run it yourself, so the counts don't measure the same choice. Neon is the more common pick among Next.js products (48 vs 40). On GitHub, 25 public pull requests moved projects from Neon to PostgreSQL, and 41 the other way.
Two sides of the database decision: managed database and run it yourself. When each fits, what it costs, who moves from one to the other, and what makers who chose it say.
Which 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 already run your own server and want a flat monthly cost
Use it whenYou already run a server, or want extensions and settings a managed provider doesn't offer.
Trade-offBackups, upgrades, failover and connection pooling are yours to set up and watch.
At a glance
| Used by | 96 makers' products · 20 open-source projects | 98 makers' products · 622 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 | — |
| Moved to it on GitHubpull requests since Oct 2024 | 41 from PostgreSQL | 25 from Neon |
| Downloads | 3.7M/wk+32% vs npm | 51.8M/wk+31% vs npm |
| Pricing | Free tier; usage-based paid plans. · paid from $0.106 per CU-hour | Free and open source under the PostgreSQL License; you pay only for the server or managed service that runs it. |
| Free tier | Yes | Yes |
| Open source | Yes · self-hostable | Yes · self-hostable |
Which makers on your framework pick
Makers' products built with each framework that chose either one, for database.
| Framework | |||
|---|---|---|---|
| 48 | 40 | All 382 Next.js products' picks → | |
| 1 | 32 | All 73 React products' picks → | |
| 1 | 6 | All 13 FastAPI products' picks → | |
| 4 | 2 | All 27 Astro 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 | 11% 3 | 27 |
| 2023 | 11% 4 | 5% 2 | 38 |
| 2024 | 6% 16 | 7% 19 | 270 |
| 2025 | 7% 23 | 9% 28 | 323 |
| 2026 | 11% 43 | 1% 2 | 397 |
Who moves from one to the other
Public pull requests on GitHub since Oct 2024 whose title says "Neon to PostgreSQL" or the reverse — real code changes, by developers in general rather than makers only.
- Switch Phase 0 Postgres from Compose to Neonthomasnoe/fulfillment-exception-triage · 2026-09-19
- fix(render): move dev Postgres to external NeonMemoFlow/memoflow-api · 2026-09-14
- infra: move local Postgres to Neon, add staged startup for resource-c…pranav2004-bit/DECENTRALISED-SLOT-BOOKING-SYSTEM-USING-BECKN-PROTOCOLS · 2026-09-01
- feat(infra): cut Postgres over to Neon (CAL-152, Teams-only)caseyluna/hoop-brain · 2026-08-30
- Move production Postgres from Render free tier to Neonadab-tech/globalopportunities · 2026-08-25
- Port Postgres from Fly to Neonjeffko77/learn2drive · 2026-08-21
- Move DB hosting from Render Postgres to Neonconorlum/ValoMaths · 2026-08-17
- CI builds its own Postgres instead of talking to NeonDantheMan1991/superapp · 2026-08-15
- Move the database off Render's expiring free Postgres to Neon, and back it upradim-zhor/mini-ground-station · 2026-08-03
- feat(infra): migrate Postgres to Neon and object storage to Cloudflare R2AlaskanTuna/SolarSim · 2026-07-30
- fix(db): migrate off Neon (402 quota) to DO Managed PostgresCitrateNetwork/citrate-explorer · 2026-09-30
- Switch local DB setup from Neon to Docker Compose Postgreshenrilhos/compasso · 2026-09-21
- infra: migrate production database from Neon to Railway Postgreskayibabe/qwantej · 2026-09-19
- Switch DB client from Neon HTTP to postgres.js for Supabasedoommir/novapath-website · 2026-09-10
- Migrate database from Neon to self-hosted Postgres on k3sLeadKitchen/platform · 2026-09-04
- Migrate analytics DB from Neon to Railway Postgresckrohg/a2w-control · 2026-08-23
- docs(plan): move Postgres off Neon to Render Postgres (Plan 26)hh2110/thandkoi-clinics · 2026-08-17
- feat(db): move off the Neon driver to plain Postgresbeydemirfurkan/todox · 2026-08-15
- docs: rename Neon storage to Neon Postgresmastra-ai/mastra · 2026-08-11
- Revise why-neon.md to emphasize Lakebase Postgresneondatabase/website · 2026-07-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.
Postgres is rock-solid. It handles complex data relationships gracefully and gives us the querying power we need as we scale. For relational data, it’s hands down the best choice for us.
We picked PostgreSQL over MongoDB and dedicated vector databases because one proven database handles our relational data, JSON and agent memory, with no extra stores to run.
PostgreSQL is our go-to database because of its reliability, scalability, and powerful support for structured data, making it ideal for managing and syncing customer data across multiple platforms.
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
- It is rock-solid, keeps data consistent with strong transactions, and handles complex relational queries well. PHPH 2PH 3PH 4
- With pgvector, embeddings live next to relational data, so AI features need no separate vector database. PHPH 2PH 3PH 4
- Extensions and features like PostGIS, JSON support and advanced indexing cover geospatial and semi-structured data too. PHPH 2PH 3
- Built-in full-text search lacks corpus-wide relevance ranking like BM25 and can need very large indexes. HNHN 2
- It has no loose index scan, so SELECT DISTINCT over large tables needs manual workarounds. HNHN 2
- Timestamp versus timestamptz and AT TIME ZONE behavior are easy to get wrong, with edge-case bugs around daylight saving. HNHN 2HN 3
Who uses each
What makers pair each with
Neither quite right?
See the whole database decision →Questions
Neon or PostgreSQL: which do makers choose?
Of the 1,263 makers' products we know the database of, 98 chose PostgreSQL (8%) and 96 Neon (8%). Among the 397 launched in 2026, Neon is in 11% and PostgreSQL in 1%, against 6% and 7% of those launched in 2024 or earlier. They're different kinds of tool, managed database and run it yourself, so the counts don't measure the same choice. Neon is the more common pick among Next.js products (48 vs 40). On GitHub, 25 public pull requests moved projects from Neon to PostgreSQL, and 41 the other way. Choose Neon if your traffic is bursty or you run many preview deploys, and idle hours shouldn't cost much; choose PostgreSQL if you already run your own server and want a flat monthly cost.
When should I pick Neon over PostgreSQL?
Pick Neon if: Your traffic is bursty or you run many preview deploys, and idle hours shouldn't cost much.
When should I pick PostgreSQL over Neon?
Pick PostgreSQL if: You already run your own server and want a flat monthly cost.
Are people switching from Neon to PostgreSQL?
Public GitHub pull requests since 2024-10-02: 25 from Neon to PostgreSQL, 41 from PostgreSQL to Neon.

