MySQL vs PostgreSQL
Of the 1,263 makers' products we know the database of, 98 chose PostgreSQL (8%) and 10 MySQL (1%); 2 use both. Among the 397 launched in 2026, MySQL is in 0% and PostgreSQL in 1%, against 1% and 7% of those launched in 2024 or earlier.
Two run it yourself options for database. When each fits, what it costs, who moves from one to the other, and what makers who chose it say.
Which fits you
- PHP, Laravel, WordPress and Rails stacks, and teams that already know MySQL well.
Use it whenYour framework, host or existing data already assumes MySQL, or you're joining a codebase built on it.
Trade-offFewer extensions and advanced types than Postgres, so most new tooling (vectors, JSON-heavy work) targets Postgres first.
- 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 | 10 makers' products · 208 open-source projects | 98 makers' products · 622 open-source projects |
|---|---|---|
| Downloads | 14.1M/wk+15% vs npm | 51.8M/wk+31% vs npm |
| Pricing | Free (open source Community Edition); managed versions are sold by cloud providers. | 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 | |||
|---|---|---|---|
| 4 | 40 | All 382 Next.js products' picks → | |
| 2 | 32 | All 73 React products' picks → | |
| 1 | 6 | 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 | 0% 0 | 11% 3 | 27 |
| 2023 | 0% 0 | 5% 2 | 38 |
| 2024 | 1% 2 | 7% 19 | 270 |
| 2025 | 1% 3 | 9% 28 | 323 |
| 2026 | 0% 0 | 1% 2 | 397 |
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.
This relational database is known for its reliability and extensive adoption. It benefits from a large community and ample resources for support and learning. By adhering to SQL standards, it eases development and migration processes. Additionally, it provides flexible scalability options, both horizontal and vertica…
We needed a structured and reliable database to handle team interactions and activity tracking effortlessly. It’s the pizza vault where every slice sent, received, and celebrated is safely stored! 🍕📦
The database tables are using MySQL which are simple yet robust.
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.
- 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
MySQL or PostgreSQL: which do makers choose?
Of the 1,263 makers' products we know the database of, 98 chose PostgreSQL (8%) and 10 MySQL (1%); 2 use both. Among the 397 launched in 2026, MySQL is in 0% and PostgreSQL in 1%, against 1% and 7% of those launched in 2024 or earlier. Choose MySQL if PHP, Laravel, WordPress and Rails stacks, and teams that already know MySQL well; choose PostgreSQL if you already run your own server and want a flat monthly cost.
Can you use MySQL and PostgreSQL together?
2 makers' products we track use both, often one replacing the other or each for a different part of the product: First Street, Labelbox.
When should I pick PostgreSQL over MySQL?
Pick PostgreSQL if: You already run your own server and want a flat monthly cost.

