Updated

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.

Ask your AI about this, with this page as the source:ChatGPT ↗Claude ↗Perplexity ↗

Which fits you

Choose Neon if
  • 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.

Choose PostgreSQL if
  • 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

NeonPostgreSQL
Used by96 makers' products · 20 open-source projects98 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 202441 from PostgreSQL25 from Neon
Downloads3.7M/wk+32% vs npm51.8M/wk+31% vs npm
PricingFree tier; usage-based paid plans. · paid from $0.106 per CU-hourFree and open source under the PostgreSQL License; you pay only for the server or managed service that runs it.
Free tierYesYes
Open sourceYes · self-hostableYes · self-hostable

Which makers on your framework pick

Makers' products built with each framework that chose either one, for database.

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).

LaunchedNeonPostgreSQLProducts
2022 or earlier4% 111% 327
202311% 45% 238
20246% 167% 19270
20257% 239% 28323
202611% 431% 2397

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.

PostgreSQL → Neon41 PRs
When and what they move →

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.

On Neon
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.
Relay, the makerSep 2026 ↗
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.
UseAgents, the makerSep 2026 ↗
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.
Saturn, the makerSep 2026 ↗
60 more on the Neon page →
On PostgreSQL
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.
VisionAR, the makerSep 2026 ↗
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.
Semos.ai Manager Agents, the makerSep 2026 ↗
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.
Skarbe, the makerSep 2026 ↗
41 more on the PostgreSQL page →

Loved and watch-outs

Themes that recur in makers' words and Hacker News comments, each linked to what it summarises.

Neon
Most loved
  • 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
Watch-outs
  • 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
On Product Hunt: 5.0★, 95 reviews · mentioned most: easy setup, serverless architecture, database branching · complaints: high pricing
PostgreSQL
Most loved
  • 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
Watch-outs
  • 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
On Product Hunt: 5.0★, 77 reviews · mentioned most: reliability, performance, scalability

Who uses each

What makers pair each with

SupabaseBackend platformPostgres plus auth, storage and realtime in one project.vs Neon →vs PostgreSQL →
ConvexBackend platformRealtime, collaborative apps written entirely in TypeScript.
FirebaseBackend platformMobile apps that need offline sync and client-side SDKs.
PlanetScaleManaged databaseApps that expect heavy scale and want zero-downtime schema changes.vs Neon →
TursoManaged databaseSQLite at the edge, or one database per customer.vs Neon →vs PostgreSQL →
MongoDBManaged databaseDocument-shaped data and teams already fluent in Mongo.vs PostgreSQL →

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.