Database · for React

Database for React

Among 53 makers' products we track that are built with React, here's what they chose for database — each counted from a live-product source.

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

Counts are live products with a source, not market share; a product using two options counts in both.

FirebaseBackend platform
llms.txtIn Lovable

Best forMobile apps that need offline sync and client-side SDKs.

Trade-offA document store without SQL joins; hard to migrate off.

15 of the 53 React products here · free tier

PostgreSQLRun it yourself
In Replit

Best 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.

15 of the 53 React products here · free tier · open source

MongoDBManaged database
llms.txt

Best 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.

13 of the 53 React products here · free tier

SupabaseBackend platform
llms.txtMCPCLIIn Bolt, Lovable, v0

Best 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.

12 of the 53 React products here · free tier · open source

ClickHouseAnalytics (OLAP)
llms.txtMCPIn Lovable

Best 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.

3 of the 53 React products here · free tier · open source

ConvexBackend platform
llms.txtCLI

Best forRealtime, collaborative apps written entirely in TypeScript.

Trade-offIts own data model and query API rather than SQL.

1 of the 53 React products here · free tier · open source

MySQLRun it yourself

Best forPHP, Laravel, WordPress and Rails stacks, and teams that already know MySQL well.

Trade-offFewer extensions and advanced types than Postgres, so most new tooling (vectors, JSON-heavy work) targets Postgres first.

1 of the 53 React products here · free tier · open source

DuckDBAnalytics (OLAP)
llms.txt

Best forAnalytical SQL inside your app or script over local or S3-hosted CSV and Parquet files, with no server to run.

Trade-offAn embedded library, so it doesn't serve many concurrent writers like a database server does.

1 of the 53 React products here · free tier · open source

Neo4jGraph
llms.txt

Best forData that is mostly relationships — social graphs, recommendations, knowledge graphs — queried with Cypher.

Trade-offA second database and query language to learn and run; managed AuraDB is priced by memory.

1 of the 53 React products here · free tier · open source

Also real options for database, not seen among these React products yet: Neon, PlanetScale, Turso.