Updated

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.

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

Which fits you

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

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

MySQLPostgreSQL
Used by10 makers' products · 208 open-source projects98 makers' products · 622 open-source projects
Downloads14.1M/wk+15% vs npm51.8M/wk+31% vs npm
PricingFree (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 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).

LaunchedMySQLPostgreSQLProducts
2022 or earlier0% 011% 327
20230% 05% 238
20241% 27% 19270
20251% 39% 28323
20260% 01% 2397

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 MySQL
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…
Amploo, the makerSep 2026 ↗
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! 🍕📦
PizzaTime, the makerSep 2026 ↗
The database tables are using MySQL which are simple yet robust.
Snippeta, the makerSep 2026 ↗
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.

MySQLOn Product Hunt: 5.0★, 6 reviews
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

Used by both — often one replacing the other, or each for a different part of the product

What makers pair each with

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

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.