Database for Next.js: what 382 makers' products chose
Among 382 makers' products built with Next.js that we know the database of, Supabase leads: 171 of them (45%). Next come Neon (48) and PostgreSQL (40). Next.js makers pick Neon 1.7× and Convex 1.7× 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 Next.js chose
| Option | Next.js products | All makers | 2026 launches | Free for | At 10,000 users |
|---|---|---|---|---|---|
| 171 (45%) | 45% | 54% | ~500 users | $25/moPro | |
| 48 (13%) | 8% | 21% | None | $22/moLaunch | |
| 40 (10%) | 8% | 1% | — | — | |
| 35 (9%) | 10% | 6% | ~500 users | $58/moAtlas Dedicated M10 | |
| 32 (8%) | 15% | 3% | ~2,000 users | $9.66/moBlaze (pay as you go) | |
| 26 (7%) | 4% | 13% | ~630 users | $29/moProfessional | |
| 17 (4%) | 4% | 2% | — | — | |
| 12 (3%) | 2% | 4% | None | $7.40/moPostgres PS-5 (single node) | |
| 12 (3%) | 2% | 0% | — | — | |
| 8 (2%) | 2% | 0% | ~13,000 users | — | |
| 5 (1%) | 2% | 0% | None | — | |
| 4 (1%) | 1% | 0% | ~5,900 users | $5.99/moDeveloper | |
| 4 (1%) | 1% | 0% | — | — | |
| 4 (1%) | 1% | 0% | — | — | |
| 2 (1%) | 1% | 0% | — | — |
Live makers' products with a source for both: that they're built with Next.js, 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. "2026 launches" is its share among the 107 Next.js products launched that year: a tool that came first has products from every year since, so its total runs ahead.
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 171 here - You're building a live, collaborative app entirely in TypeScript
Convex 26 here - Your traffic is bursty or you run many preview deploys, and idle hours shouldn't cost much
Neon 48 here - You already run your own server and want a flat monthly cost
PostgreSQL 40 here
Supabase
Backend platform171 Next.js products here (45%), 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.
“The absolute goat. I wouldn't ever want to miss Supabase for any of my projects, really. Postgres is awesome as always, Supabase Auth is a true game changer.”
- 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
Does it work with Next.js server-side rendering? Yes. Server-rendered apps keep the session in cookies, and the @supabase/ssr package together with supabase-js handles this for Next.js and other JavaScript frameworks. Supabase docs ↗
Status page: 25+ incidents in the last 90 days, 6 major (its own page, 2026-10-19).
“Probably the best way to build a project fast and solid. Realtime gives you mad flexibility without the headaches. Makes the app way smoother and snappier”
DatabaseMaker says so +1 · source ↗“Great solution if you need a managed PostgreSQL database.”
DatabaseMaker says so +1 · source ↗“An excellent, super easy to use databse with so many great integrations – truly an awesome Open Source company!”
DatabaseMaker says so +1 · source ↗“Managed Postgres with a great DX, built-in connection pooling, and easy scaling.”
DatabaseMaker says so +1 · source ↗“Supabase played a key role in building Linkeddit’s backend. Its real-time database and seamless authentication integrated effortlessly into our SaaS. While Firebase was an option, we chose Supabase for its open-source flexibility and powerful user data management. The ease of use and real-time capabilities made it the perfect fit for handling our platform’s dynamic user interactions.”
DatabaseMaker says so +1 · source ↗“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 ↗“The setup speed and reliability of Supabase and Firebase are very impressive.”
DatabaseMaker says so · source ↗“Supabase really helped me a lot to spin up the backend in a matter of a few days. By supporting Apple-Sign-In by I was able to build a truly native app.”
DatabaseMaker says so · source ↗“Supabase powers our real-time database and storage. From auth to hosting, it’s been rock solid.”
DatabaseMaker says so · source ↗
Neon
Managed database48 Next.js products here (13%), against 8% of all makers' products. About $22 a month at 10,000 users (Launch).
llms.txtMCPCLIIn v0Best forServerless Postgres that scales to zero, with a branch per preview deploy.
Trade-offCold starts after idle periods add latency to the first query, and heavy always-on workloads can cost more than a fixed server.
“Serverless Postgres + database branching let us spin up per-cluster preview environments on demand - no idle cost, perfect fit for how Radar Cloud actually works.”
- Postgres scales to zero when idle, so early products and staging databases cost almost nothing until traffic arrives. 2 sources
- Branching copies the production database in seconds, so migrations and preview environments are tested against real data. 4 sources
- Separating compute from storage costs latency and performance compared with Postgres on local NVMe. 2 sources
- Parts of the stack, like autoscaling and some tooling, are not supported or openly licensed for self-hosting. 2 sources
“Neon’s serverless Postgres gives us elastic, managed databases with zero-downtime branching—perfect for rapid iteration.”
DatabaseMaker says so +1 · source ↗“Great service, flexibility, reliability”
DatabaseMaker says so +1 · source ↗“Postgres, the Apple way.”
DatabaseMaker says so +1 · source ↗“Neon gives Open Analytics a fast, scalable Postgres foundation without adding infrastructure complexity for our team.”
DatabaseMaker says so +1 · source ↗“Incredible serverless database with branching that scales to 100 and 0”
DatabaseMaker says so +1 · source ↗“Needed a database that could handle variable workloads without paying for idle capacity. Neon's serverless Postgres scales with usage, which made it a perfect fit for a platform where brand generation sessions are intensive but unpredictable.”
DatabaseMaker says so +1 · source ↗“Our backend is on Neon and we like using it so far”
DatabaseMaker says so · source ↗“Easy to access all databases and great user experience.”
DatabaseMaker says so · source ↗“Huge shoutout to the Neon team. Building a platform that handles dynamic storefronts for hundreds of agencies means our database load is incredibly spikey. Neon’s serverless Postgres allows us to scale to zero when a store is quiet and handle massive traffic surges during a client launch without us ever touching a config file. It’s the only way to build AI-first infrastructure in 2026.”
DatabaseMaker says so · source ↗“My postgres database provider, easy to implement and to work with.”
DatabaseMaker says so · source ↗
PostgreSQL
Run it yourself40 Next.js products here (10%), 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 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.”
- 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
“Postgres is rock-solid and scales with us effortlessly. Its reliability and ecosystem make it a no-brainer over other databases.”
DatabaseMaker says so · source ↗“pgvector is easy to use, and generally postgres is super easy to setup and run, especially with supabase!”
DatabaseMaker says so · source ↗“The GOAT open-source database.”
DatabaseMaker says so · source ↗“Reliable database storing memory data with full-stack integration for user management.”
DatabaseMaker says so · source ↗“PGVector's native vector operations with PostgreSQL's ACID compliance works perfectly. We're storing millions of embeddings with sub-millisecond similarity search using cosine distance. The async connection pooling handles concurrent connections, while the vector indexing makes our query super fast. Having vector search, full-text search, and relational data in one database eliminates the complexity of managing multiple data stores.”
DatabaseMaker says so · source ↗“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.”
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 ↗“PostgreSQL gives us the best balance between well-structured data persistency and clean code principles”
DatabaseMaker says so · source ↗“Superexpert.AI uses this database -- used the pgvector extension to support vector embeddings in the database.”
DatabaseMaker says so · source ↗
MongoDB
Managed database35 Next.js products here (9%), 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.
“Big thanks to MongoDB and Realm! Your support has supercharged Aupair Valley’s development. Excited for our journey ahead! #TechPartnership 🚀👨👩👧👦”
- 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).
“We chose MongoDB for thegro.ai because modern outbound data isn’t clean or predictable — it’s dynamic, layered, and constantly evolving. From enriched lead profiles to campaign signals and CRM activity, we needed a flexible schema that could adapt as our product grows. MongoDB gives us the speed, scalability, and structure we need to handle complex AI-driven workflows without rigid constraints.”
DatabaseMaker says so +1 · source ↗“Modelence backends are powered by MongoDB”
DatabaseMaker says so +1 · source ↗“Our Tech Stack Node.js and express MongoDB Nginx Reactjs Nextjs Digitalocean”
DatabaseMaker says so +1 · source ↗“It stores all the data of the locker and files securely”
DatabaseMaker says so · source ↗“Always a great way to start with a small NoSQL document database. MongoDB Atlas allows us to start with a free tier and flexibly adapt as we scale up our monitoring, traffic, and storage requirements. MongoDB also allows us to be quite flexible with our schema definition as our product changes a lot initially.”
DatabaseMaker says so · source ↗“MongoDB's high-performance, schema-flexible, and highly scalable database solution has been instrumental in architecting our robust, cutting-edge backend. Thank you for providing the reliability and innovation that underpins our success in building Kotae.”
DatabaseMaker says so · source ↗“The flexibility to iterate on new AgentPulse features without migration headaches has been essential for shipping fast.”
DatabaseMaker says so · source ↗“All of the information relevant & essential for the developers is collected in a free MongoDb database.”
DatabaseMaker says so · source ↗“MongoDB powers our data layer with flexibility and performance. Its document-based structure allows us to manage event, attendee, and organizer data efficiently while ensuring scalability as Ostivities continues to grow.”
DatabaseMaker says so · source ↗“I tried extremely hard to use SQL databases and supabase... I simply could not get them to work well and did not have the time to learn what optimization mistakes I was making.. NoSQL was the way for me.”
DatabaseMaker says so · source ↗
Firebase
Backend platform32 Next.js products here (8%), 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.
“Key role in helping us deliver results in real time, because the analysis streams onto the page as it completes instead of making founders wait for a finished report.”
- 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
“Maybe I'm old, but Firebase offering is amazing. Firestore NoSQL is so powerful with the right schema design.”
DatabaseMaker says so +1 · source ↗“Controlling our Auth and DB”
DatabaseMaker says so · source ↗“Solid auth, database structure, and real-time updates.”
DatabaseMaker says so · source ↗“Our engineering rock of Gibraltar? How to best phrase this!?”
DatabaseMaker says so · source ↗“Firebase powers the backbone of uList, ensuring robust real-time data handling, secure authentication, and scalable backend infrastructure. It's the unsung hero making our app fast and reliable.”
DatabaseMaker says so · source ↗“Firebase for storing the data for seamless sync.”
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 ↗“We use Firebase to power the backend of our app, helping us handle authentication, real-time data updates, and seamless deployment. It’s been a game-changer in allowing us to scale quickly and focus on building a better experience for our users. Big thanks to Firebase for making dev life smoother!”
DatabaseMaker says so · source ↗“Listed in their tool stack on Starter Story (platform)”
DatabaseMaker says so · source ↗
Convex
Backend platform26 Next.js products here (7%), against 4% of all makers' products. Free up to about 630 users. About $29 a month at 10,000 users (Professional).
llms.txtCLIBest forRealtime, collaborative apps written entirely in TypeScript.
Trade-offIts own data model and query API rather than SQL.
“Love their UI, their reactivity is insanely good. Was initially with supabase, but have shifted to convex now. Also don't like writing SQL, so Convex was a no-brainer.”
- Real-time sync is built in, so dashboards, comments and leaderboards update for every user without refreshes or extra plumbing. 2 sources
- Database, server functions and auth in one service replace a whole backend stack for a one-person team. 3 sources
- It works unlike a conventional database; joins are written imperatively in JavaScript and SQL-oriented tools integrate awkwardly. 2 sources
- It does not work offline, and optimistic updates must be written by hand. 1 source
Status page: 6 incidents in the last 90 days, 4 major (its own page, 2026-10-19).
“A backend that feels like state, not a database. Lets a small team ship features that would normally need three engineers.”
DatabaseMaker says so +1 · source ↗“Awesome Database, very nice to work with. It's a really good fit database for LMS and the real time is a nice feature.”
DatabaseMaker says so +1 · source ↗“Real-time updates results in beautiful UX”
DatabaseMaker says so · source ↗“Helped us create a fast and scalable backend, ensuring that every node, connection, and update in Graphify happens instantly. Without Convex, handling dynamic knowledge graphs would be a major challenge.”
DatabaseMaker says so · source ↗“I love convex. What more can I say?”
DatabaseMaker says so · source ↗“For making realtime collaboration simple”
DatabaseMaker says so · source ↗“Great dev docs and easy to user”
DatabaseMaker says so · source ↗“By far the most important shoutout, It's our entire backend: database, realtime sync, server functions. But more importantly, Convex's @convex-dev/agent, @convex-dev/rag, @convex-dev/rate-limiter do a lot in ReleaseDock. Convex also has the best usage tracking & analytics UX so you can track your performance as your project grows. The best in class in my humble opinion.”
DatabaseMaker says so · source ↗“Easy deployments and built-in realtime that works without any issues”
DatabaseMaker says so · source ↗“TL;DR - Blazing fast, flexible, reliable, affordable. Everything from documents, databases, caching, vectors and even all our AI functions - all in one place. Shortened our development by years!”
DatabaseMaker says so · source ↗Also chosen, and not seen yet
Fewer Next.js products here: ClickHouse (17), PlanetScale (12), Snowflake (12), Tinybird (8), Neo4j (5), Turso (4), MySQL (4), BigQuery (4), DuckDB (2).
Who switches, and to what
Public GitHub pull requests whose title says "X to Y", by developers in general, not only on Next.js.
- 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 Next.js stack
What makers' Next.js products chose for their other decisions, the most common pick for each:
- Hosting: Vercel 1,078 of 1,312
- Transactional Email: Resend 493 of 830
- Payments: Stripe 288 of 359
- LLM API: OpenAI API 222 of 301
- Authentication: Clerk 176 of 211
- Web Analytics: Google Analytics 105 of 197
- Product Analytics: PostHog 123 of 168
- Lifecycle Email: Loops 87 of 108
Questions
What do most Next.js apps use for database?
Among 382 makers' products built with Next.js that we know the database of, Supabase leads: 171 of them (45%). Next come Neon (48) and PostgreSQL (40). Next.js makers pick Neon 1.7× and Convex 1.7× as often as makers overall.
What does database cost for a Next.js app with 10,000 users?
On our usage model at 10,000 users, Supabase comes to about $25 a month (Pro); Neon comes to about $22 a month (Launch); MongoDB comes to about $58 a month (Atlas Dedicated M10); Firebase comes to about $9.66 a month (Blaze (pay as you go)). Prices are from each vendor's pricing page.
Which database option stays free longest for a Next.js 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 Next.js 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.