PostgreSQL vs Turso
Of the 1,263 makers' products we know the database of, 98 chose PostgreSQL (8%) and 13 Turso (1%); 1 uses both. Among the 397 launched in 2026, PostgreSQL is in 1% and Turso in 0%, against 7% and 1% of those launched in 2024 or earlier. They're different kinds of tool, run it yourself and managed database, so the counts don't measure the same choice. On GitHub, 4 public pull requests moved projects from PostgreSQL to Turso, and 6 the other way.
Two sides of the database decision: run it yourself and managed database. When each fits, what it costs, who moves from one to the other, and what makers who chose it say.
Which fits you
- 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.
- SQLite at the edge, or one database per customer.
Use it whenEach customer should get their own isolated database, or reads need to happen close to users worldwide.
Trade-offSQLite semantics — one writer at a time, fewer extensions — suit read-heavy apps better than write-heavy ones.
At a glance
| Used by | 98 makers' products · 622 open-source projects | 13 makers' products · 36 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 | — | $5.99/mo Developer |
| Moved to it on GitHubpull requests since Oct 2024 | 6 from Turso | 4 from PostgreSQL |
| Downloads | 51.8M/wk+31% vs npm | 2.8M/wk+99% vs npm |
| Pricing | Free and open source under the PostgreSQL License; you pay only for the server or managed service that runs it. | Free tier; paid plans by databases and usage. · paid from $4.99/mo |
| 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 | |||
|---|---|---|---|
| 40 | 4 | All 382 Next.js products' picks → | |
| 32 | 0 | All 73 React products' picks → | |
| 6 | 0 | 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 | 11% 3 | 0% 0 | 27 |
| 2023 | 5% 2 | 3% 1 | 38 |
| 2024 | 7% 19 | 1% 4 | 270 |
| 2025 | 9% 28 | 2% 6 | 323 |
| 2026 | 1% 2 | 0% 1 | 397 |
Who moves from one to the other
Public pull requests on GitHub since Oct 2024 whose title says "PostgreSQL to Turso" or the reverse — real code changes, by developers in general rather than makers only.
- web: theme votes, page views and cookbook sales move from Turso to Postgresprofullstack/hqtui · 2026-09-25
- Move the waitlist from Turso to Postgresprofullstack/opensourcelegends.com · 2026-09-25
- Migrate from Turso to Postgres (happy path)tryy3/warera-tools · 2026-09-19
- Port DB from SQLite/Turso to Postgres on Neon (#96, #97, #98)zachradtka/nextopp · 2026-05-27
- Switch from Turso to Vercel Postgres (no extra signup)AlaudaAI/google-review-skill · 2026-02-16
- change vote from turso to Postgres test using filter by label = Milodatum-cloud/datum.net · 2025-06-18
- Migrate Payload DB from Postgres to Turso SQLitehephatech/feelings.bar · 2026-07-29
- Migrate database from Netlify (Postgres) to Turso (SQLite)smkdwiguna/dwiguna-info · 2026-06-08
- feat(repo): migrate database from Neon Postgres to Turso (libSQL)johinsDev/loyalty-app · 2026-05-27
- 133 f migrates from postgres to tursoacmutsa/ClubKit · 2025-03-03
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.
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.
Lightweight, distributed SQLite that just works. Perfect for edge setups and production use cases.
We wanted to build application that has single tenant databases for each organization. Turso handles that super nicely. In addition the ability to have embedded replicas is killer feature for building local RAG.
Turso is amazing for edge databases—blazing-fast reads/writes, easy dev setup, and scales globally without the usual backend headaches. Perfect for modern apps. We used it for Analytics, great experience overall.
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
- It keeps SQLite's simplicity while scaling for edge and serverless apps, and moving from local development to hosted is easy. PHHN
- A database per tenant and embedded replicas make single-tenant designs and local-first or offline apps straightforward. PHPH 2HN
- The Rust rewrite adds async I/O, concurrent writes, encryption, change data capture and vector search while staying SQLite file-compatible. HNHN 2HN 3HN 4
- The Rust rewrite is still beta, with panics, data-corrupting bugs and thin test coverage that undermine trust for production. HNHN 2HN 3HN 4
- The split between libSQL and the new Turso packages is confusing, and libSQL showed memory leaks on large write jobs. HNHN 2HN 3
- Compatibility with SQLite is incomplete; for example, another process cannot read a WAL database it has open. HNHN 2
Who uses each
What makers pair each with
Neither quite right?
See the whole database decision →Questions
PostgreSQL or Turso: which do makers choose?
Of the 1,263 makers' products we know the database of, 98 chose PostgreSQL (8%) and 13 Turso (1%); 1 uses both. Among the 397 launched in 2026, PostgreSQL is in 1% and Turso in 0%, against 7% and 1% of those launched in 2024 or earlier. They're different kinds of tool, run it yourself and managed database, so the counts don't measure the same choice. On GitHub, 4 public pull requests moved projects from PostgreSQL to Turso, and 6 the other way. Choose PostgreSQL if you already run your own server and want a flat monthly cost; choose Turso if SQLite at the edge, or one database per customer.
When should I pick PostgreSQL over Turso?
Pick PostgreSQL if: You already run your own server and want a flat monthly cost.
Are people switching from PostgreSQL to Turso?
Public GitHub pull requests since 2024-10-02: 4 from PostgreSQL to Turso, 6 from Turso to PostgreSQL.

