MySQL vs PostgreSQL
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
| MySQL | PostgreSQL | |
|---|---|---|
| Used by | 6 makers' products · 178 open-source projects | 74 makers' products · 542 open-source projects |
| Downloads | 14.3M/wk+17% vs npm | 45.1M/wk+18% 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 |
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 MySQLWe 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! 🍕📦
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 chose MySQL for its reliability, speed, and flexibility, ensuring efficient data management and scalability for our project.
On PostgreSQLPostgres 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.
Postgres is so nice to work with. pg_dump was a lifesaver when we had to move database providers. Extensions like pgvector make it the best database for building AI apps.
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 reviewsPostgreSQLMost 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
On Product Hunt: 5.0★, 77 reviews · mentioned most: reliability, performance, scalability- 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
Amploo
cmd.haus
Swipeart
CalmerWhat makers pair each with
With MySQLFrontend Framework
MySQL + React:PizzaTimeAgent-First-OrganizationAutoGPTcasdoorchartbrewdoryegghead-nextever-demandever-gauzyever-worksgitpodletterpadand 82 more
Backend Framework
MySQL + Express:chartbrewever-demandever-gauzyever-worksgitpodoneuptimeservercn
SmythOSsoketiaivaapitableappimage.github.ioand 36 more
SmythOSsoketiaivaapitableappimage.github.ioand 36 more
MastraDatabase Access & ORMs
MySQL + SQLAlchemy:AutoGPTTheNinjaRPGAix-DBapi-for-open-llmarboris-novelargbagofwords
CrewAIDaftDB-GPTeyesFinSynthand 29 more
CrewAIDaftDB-GPTeyesFinSynthand 29 more
UnInbox
Bun
create-t3-app
Directus
DubWith PostgreSQLFrontend Framework
PostgreSQL + Next.js:
Byterover
JustPaid
Moneo AI
Morphik
NeuralAgent
Open Paper
Permit.io
Qibble
Skarbe
Superexpert.AI
VisionAR
VizDiffand 6 more
ByteroverJustPaidMoneo AIMorphikNeuralAgentOpen PaperPermit.ioQibbleSkarbeSuperexpert.AIVisionARVizDiffand 6 morePostgreSQL + React:
BaselightBoondockers WelcomeExirioHexpay
Incerto
Layer
MedusaMoneo AINeuralAgent
ReviewradarSaasRockSongstatsand 4 more
BaselightBoondockers WelcomeExirioHexpayIncertoLayerMedusaMoneo AINeuralAgentReviewradarSaasRockSongstatsand 4 morePostgreSQL + Astro:Baselight
Dodo Payments
Supabase
BaselightDodo PaymentsSupabaseHosting
PostgreSQL + Amazon Web Services:
BooleanMaths PulseJustPaidNeuralAgent
TrieveDodo PaymentsLingloop
Neon
BooleanMaths PulseJustPaidNeuralAgentTrieveDodo PaymentsLingloopNeon
ScrapIn
AGG Loop ex-DeposurePostgreSQL + Cloudflare:Reviewradar
PrismaSupabase
ReviewradarPrismaSupabaseTransactional Email
Hexclave (Stack Auth)
ScispaceBackend Framework
PostgreSQL + FastAPI:
Atlas.coNeuralAgentPermit.io
Warestack
Atlas.coNeuralAgentPermit.ioWarestackPostgreSQL + Ruby on Rails:SkarbeSongstats
SkarbeSongstatsNeither quite right?
See the whole database decision →
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.
Turso
MongoDBManaged databaseDocument-shaped data and teams already fluent in Mongo.vs MySQL →vs PostgreSQL →