Database for React: what 73 makers' products chose
Among 73 makers' products built with React that we know the database of, PostgreSQL leads: 32 of them (44%), 5.6× its share among all makers' products (8%). Next come Firebase (16) and Supabase (15). React makers pick MongoDB 1.9× as often as makers overall.
Where the data lives: a whole backend platform (database, auth and storage in one project), a managed database you reach from your own code, or the raw engine on your own server. Postgres is the default unless you have a reason to pick otherwise; analytics and graph databases sit next to it for workloads it handles poorly, not instead of it. How your code talks to it is its own decision (Database Access & ORMs).
What makers on React chose
| Option | React products | All makers | Free for | At 10,000 users |
|---|---|---|---|---|
| 32 (44%) | 8% | — | — | |
| 16 (22%) | 15% | ~2,000 users | $9.66/moBlaze (pay as you go) | |
| 15 (21%) | 45% | ~500 users | $25/moPro | |
| 14 (19%) | 10% | ~500 users | $58/moAtlas Dedicated M10 | |
| 4 (5%) | 4% | — | — | |
| 3 (4%) | 2% | — | — | |
| 2 (3%) | 1% | — | — | |
| 1 (1%) | 4% | ~630 users | $29/moProfessional | |
| 1 (1%) | 8% | None | $22/moLaunch | |
| 1 (1%) | 2% | None | $7.40/moPostgres PS-5 (single node) | |
| 1 (1%) | 1% | — | — | |
| 1 (1%) | 2% | ~13,000 users | — | |
| 1 (1%) | 2% | None | — | |
| 1 (1%) | 0% | — | — | |
| 1 (1%) | 1% | — | — |
Live makers' products with a source for both: that they're built with React, and what they use for database. A product using two options counts in both; not market share. "All makers" is the option's share among every maker's product that made this decision.
Costs are the cheapest plan that fits, from each vendor's pricing page, at the usage our stack planner assumes for a product with that many users. Free for: the users its cheapest plan a business can use stays free for; plans for personal use only, like a non-commercial hobby tier, don't count.
Which to pick, by situation
- You want the database, auth and file storage in one project, and plain SQL you can take elsewhere
Supabase 15 here - You're building a live, collaborative app entirely in TypeScript
Convex 1 here - Your traffic is bursty or you run many preview deploys, and idle hours shouldn't cost much
Neon 1 here - You already run your own server and want a flat monthly cost
PostgreSQL 32 here
PostgreSQL
Run it yourself32 React products here (44%), against 8% of all makers' products.
In ReplitBest forThe engine behind most of the hosted options above, run on your own server or container for full control and a flat cost.
Trade-offBackups, upgrades, failover and connection pooling are yours to set up and watch.
“Postgres was the second database we added, and honestly, it needs no introduction. This OSS RDBMS is massive, reliable, and just incredible to work with.”
- It is rock-solid, keeps data consistent with strong transactions, and handles complex relational queries well. 4 sources
- With pgvector, embeddings live next to relational data, so AI features need no separate vector database. 4 sources
- Built-in full-text search lacks corpus-wide relevance ranking like BM25 and can need very large indexes. 2 sources
- It has no loose index scan, so SELECT DISTINCT over large tables needs manual workarounds. 2 sources
“PostgreSQL serves as our primary database, offering powerful SQL querying and reliable data storage for managing structured data and transactions.”
DatabaseMaker says so · source ↗“Google Workspace Discord GitHub AWS PostgreSQL REdis InfluxDB Python Flask …”
DatabaseMaker says so · source ↗“Database for all your commerce data.”
DatabaseMaker says so · source ↗“Offered a robust, scalable database for structured data storage and querying.”
DatabaseMaker says so · source ↗“Postgres was the second database we added, and honestly, it needs no introduction. This OSS RDBMS is massive, reliable, and just incredible to work with.”
DatabaseMaker says so · source ↗“Listed in their tool stack on Starter Story”
DatabaseMaker says so · source ↗“The best relational database!”
DatabaseMaker says so · source ↗“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.”
DatabaseMaker says so · source ↗“Listed in their tool stack on Starter Story”
DatabaseMaker says so · source ↗“Great solution for a SQL database. Our first choice.”
DatabaseMaker says so · source ↗
Firebase
Backend platform16 React products here (22%), against 15% of all makers' products. Free up to about 2,000 users. About $9.66 a month at 10,000 users (Blaze (pay as you go)).
llms.txtIn Lovable, RorkBest forMobile apps that need offline sync and client-side SDKs.
Trade-offA document store without SQL joins; hard to migrate off.
“Our engineering rock of Gibraltar? How to best phrase this!?”
- Auth, Firestore, Cloud Functions and hosting wire up in minutes, the fastest path to a working backend for a solo developer. 2 sources
- Real-time sync across devices, with offline caching that remains stronger than most all-in-one rivals. 2 sources
- A server-side change made the iOS SDK crash apps everywhere, exposing the risk of a closed SDK you cannot control. 4 sources
- It feels neglected and bolted onto Google Cloud, and it cannot be self-hosted, so leaving means a full migration. 3 sources
“Our engineering rock of Gibraltar? How to best phrase this!?”
DatabaseMaker says so · source ↗“Listed in their tool stack on Starter Story (platform)”
DatabaseMaker says so · source ↗“Listed in their tool stack on Starter Story”
DatabaseMaker says so · source ↗“Listed in their tool stack on Starter Story (platform)”
DatabaseMaker says so · source ↗“Listed in their tool stack on Starter Story (platform)”
DatabaseMaker says so · source ↗“Listed in their tool stack on Starter Story (trello)”
DatabaseMaker says so · source ↗“Firebase is super cool. We love how easy it was to integrate and how easy it is to mix and match their various products together. Yes the documentation isnt the easiest to read, but now with Gemini built in, its really easy to get answers (and advice) to any query you might have.”
DatabaseMaker says so · source ↗“Listed in their tool stack on Starter Story (trello)”
DatabaseMaker says so · source ↗“Listed in their tool stack on Starter Story (platform)”
DatabaseMaker says so · source ↗“Auth and realtime sync for user sessions across dashboard, chat, and CLI.”
DatabaseMaker says so · source ↗
Supabase
Backend platform15 React products here (21%), against 45% of all makers' products. Free up to about 500 users. About $25 a month at 10,000 users (Pro).
llms.txtMCPCLIIn Bolt, Lovable, Rork, v0Best forPostgres plus auth, storage and realtime in one project.
Trade-offAuth, storage and database in one vendor makes leaving harder later, and free projects pause after a week without activity.
“Supabase provided a simple way to add real-time presence without building and maintaining a separate backend, which was ideal for a mostly static web project.”
- One project covers Postgres, auth, storage and realtime, so a solo founder ships without stitching vendors or hiring a backend team. 4 sources
- It is real Postgres with SQL, row-level security and pgvector rather than a proprietary store. 4 sources
- Row-level security policies are hard to get right, so many apps end up exposing data publicly. 4 sources
- Reliability has been shaky for some, and it is not really built for self-hosting in practice. 1 source
Status page: 25+ incidents in the last 90 days, 6 major (its own page, 2026-10-19).
“Hey everyone! 👋 Founder here again. Great question about the backend stack! We chose Supabase for Rankfender after evaluating all four options, and here's why: 1. PostgreSQL from day one. Unlike Convex (NoSQL) or Appwrite (document-based), Supabase gives us full SQL power with ACID compliance . For a data-heavy platform tracking AI answers and keyword performance, we needed relational integrity and complex queries—Postgres delivers that out of the box . 2. Open-source = no vendor lock-in. Railway is great for deployment flexibility, but it's more of a PaaS than a full BaaS—we'd have to build auth, storage, and realtime ourselves . Supabase gives us the "batteries-included" backend (auth, realtime, storage, edge functions) and we can self-host if needed . That matters for enterprise clients down the road. 3. Real-time capabilities. We monitor AI-generated answers as they appear—that requires live data sync. Supabase's real-time subscriptions (built on Postgres logical replication) give us this without extra infrastructure . 4. Growing ecosystem. With customers like Mozilla, GitHub, and 1Password using it , we knew Supabase could scale with us. The branching feature integrated with Git is also a lifesaver for our development workflow . Why not the others? Railway: Too low-level. We'd spend weeks building auth and storage instead of focusing on AI visibility features. Convex: Great for real-time apps, but the NoSQL model and less mature auth meant more complexity for our relational data . Appwrite: Solid option, but the document database approach didn't fit our SQL-heavy needs, and real-time felt less battle-tested . At the end of the day, Supabase hit the sweet spot: PostgreSQL power + Firebase-like speed + open-source flexibility. It let us build fast without painting ourselves into a corner. 🚀 Happy to dive deeper if anyone has follow-up questions!”
DatabaseMaker says so · source ↗“I chose Supabase for its powerful real-time capabilities and PostgreSQL backend. It allowed me to sync voting results across all users instantly without the complexity of managing a custom WebSocket server.”
DatabaseMaker says so · source ↗“Supabase provided a simple way to add real-time presence without building and maintaining a separate backend, which was ideal for a mostly static web project.”
DatabaseMaker says so · source ↗“I't has all the dev requirements as like auth , database , storage ,etc .”
DatabaseMaker says so · source ↗“Supabase helps us move fast. It gives us Firebase-style features—auth, real-time, and a managed database—but with SQL and open-source power. Great for building and scaling.”
DatabaseMaker says so · source ↗“Needed a database for licenses and storage for the DMG without managing infrastructure. Supabase handled it all in one dashboard. It runs on PostgreSQL, so you get real SQL and queries. License keys, download usage, and DMG storage in a public bucket were set up in minutes with the clean JS client. Firebase uses NoSQL, which feels awkward for relational data like licenses and orders. PlanetScale lacks built-in storage, and Amazon Web Services (RDS + S3 + IAM) would’ve taken a full weekend. Supabase took an afternoon.”
DatabaseMaker says so · source ↗“Our realtime backbone. Device logs, agent events, and test states sync instantly thanks to Supabase’s rock-solid infra.”
DatabaseMaker says so · source ↗“Absolutely love it - so easy and awesome!”
DatabaseMaker says so · source ↗
MongoDB
Managed database14 React products here (19%), against 10% of all makers' products. Free up to about 500 users. About $58 a month at 10,000 users (Atlas Dedicated M10).
llms.txtBest forDocument-shaped data and teams already fluent in Mongo.
Trade-offNo joins or schema by default, so relational data and migrations take discipline you'd get for free in Postgres.
“Our data structure was changing every hour in the beginning, and Mongo was the only thing that did not break every time we pivoted.”
- The flexible document model lets fast-changing products evolve their data without rigid migrations. 4 sources
- Atlas starts on a free tier and handles scaling, backups and monitoring, so there is little database to manage. 4 sources
- Its history of unsafe defaults and lost writes left a lasting reputation that still keeps many developers away. 4 sources
- Anything beyond simple reads and writes is hard, and aggregation pipelines feel primitive next to SQL, which costs more over time. 2 sources
Status page: 13 incidents in the last 90 days, 5 major (its own page, 2026-10-19).
“Flexible document database built for modern apps.”
DatabaseMaker says so · source ↗“MongoDB brings flexibility and power to our data management”
DatabaseMaker says so · source ↗“Our data structure was changing every hour in the beginning, and Mongo was the only thing that did not break every time we pivoted.”
DatabaseMaker says so · source ↗“All of the information relevant & essential for the developers is collected in a free MongoDb database.”
DatabaseMaker says so · source ↗“Unlike PostgreSQL or MySQL, MongoDB provides dynamic schema, perfect for evolving data models.”
DatabaseMaker says so · source ↗“We use Atlas to incorporate and we use Google Apps for our Gmail.”
DatabaseMaker says so · source ↗“Flexible document database built for modern apps.”
DatabaseMaker says so · source ↗“MongoDB provides the document data model maps to how you think and code. Break out of rigid, tabular data structures with flexible documents that map directly to objects in your code. Embed related data into a single document to increase performance and minimize computational cost.”
DatabaseMaker says so · source ↗“easy to use with pre built charts you can customize”
DatabaseMaker says so · source ↗
ClickHouse
Analytics (OLAP)4 React products here (5%), against 4% of all makers' products.
llms.txtMCPIn LovableBest forFast aggregate queries over billions of rows of events, logs or metrics, self-hosted or on ClickHouse Cloud.
Trade-offBuilt for bulk inserts and scans, not frequent row updates or transactions; runs next to your main database, not instead of it.
“ClickHouse OSS was one of the very initial database we supported. Amazing OSS drivers and support.”
Status page: 15 incidents in the last 90 days, 1 major (its own page, 2026-10-19).
“Thanks Clickhouse for the best realtime data warehouse”
DatabaseMaker says so · source ↗“ClickHouse OSS was one of the very initial database we supported. Amazing OSS drivers and support.”
DatabaseMaker says so · source ↗“Chosen for analytics due to its blazing-fast query performance.”
DatabaseMaker says so · source ↗
Snowflake
Analytics (OLAP)3 React products here (4%), against 2% of all makers' products.
llms.txtBest forA managed data warehouse that joins data from your app, billing and other sources, on the AWS, Azure or Google Cloud region you choose.
Trade-offNo free tier after the 30-day trial, and compute is billed by how long warehouses run, so sizing and auto-suspend need watching; more than most small apps need before their data outgrows Postgres.
Status page: 25 incidents in the last 90 days, 19 major (its own page, 2026-10-19).
Also chosen, and not seen yet
Fewer React products here: MySQL (2), Convex (1), Neon (1), PlanetScale (1), DuckDB (1), Tinybird (1), Neo4j (1), Cloudflare D1 (1), BigQuery (1).
Real options for database not seen among these React products yet: Turso.
Who switches, and to what
Public GitHub pull requests whose title says "X to Y", by developers in general, not only on React.
- Firebase → Supabase 297 pull requests · how they moved
- Supabase → Neon 170 pull requests · how they moved
- Supabase → Firebase 113 pull requests · how they moved
- MongoDB → Supabase 75 pull requests · how they moved
- Neon → Supabase 63 pull requests · how they moved
- Supabase → Convex 50 pull requests · how they moved
Getting database right
Pick a managed Postgres unless you have a reason not to. Turn on backups before your first real user, and use the provider's connection pooler from serverless functions.
- Never restoring a backup until the day you need one — the first bad migration or stray DELETE is a bad time to learn the backup is missing or too old.
- Opening a fresh database connection in every serverless function call, which runs Postgres out of connections under modest traffic; use the provider's connection pooler.
- Changing the schema by hand in the production console instead of through migrations, so local, preview and production databases quietly drift apart.
The rest of the React stack
What makers' React products chose for their other decisions, the most common pick for each:
- Hosting: Vercel 68 of 147
- Transactional Email: SendGrid 64 of 109
- Payments: Stripe 76 of 87
- Web Analytics: Google Analytics 54 of 66
- LLM API: OpenAI API 23 of 38
- Product Analytics: PostHog 17 of 37
- Lifecycle Email: Loops 10 of 19
- Workflow Automation: Zapier 15 of 17
Questions
What do most React apps use for database?
Among 73 makers' products built with React that we know the database of, PostgreSQL leads: 32 of them (44%), 5.6× its share among all makers' products (8%). Next come Firebase (16) and Supabase (15). React makers pick MongoDB 1.9× as often as makers overall.
What does database cost for a React app with 10,000 users?
On our usage model at 10,000 users, Firebase comes to about $9.66 a month (Blaze (pay as you go)); Supabase comes to about $25 a month (Pro); MongoDB comes to about $58 a month (Atlas Dedicated M10); Convex comes to about $29 a month (Professional). Prices are from each vendor's pricing page.
Which database option stays free longest for a React app?
Tinybird: on our usage model its cheapest plan stays free up to about 13,000 users.
How this is counted: a product is on React when a live-product source says so (the maker, its website, a customer story or a subprocessor list), and the same for its database. How evidence is collected.