Firebase vs Supabase
Of the 1,263 makers' products we know the database of, 573 chose Supabase (45%) and 187 Firebase (15%); 3 use both. Among the 397 launched in 2026, Firebase is in 9% and Supabase in 63%, against 19% and 33% of those launched in 2024 or earlier. Firebase is the more common pick among React products (16 vs 15). At our calculator's default usage, Firebase comes to $9.66 a month and Supabase $25, at list prices. On GitHub, 297 public pull requests moved projects from Firebase to Supabase, and 113 the other way.
Two backend platform options for database. When each fits, what it costs, who moves from one to the other, and what makers who chose it say.
FirebaseBackend platformllms.txtIn Lovable, Rork
SupabaseBackend platformllms.txtMCPCLIIn Bolt, Lovable, Rork, v0Which fits you
- Mobile apps that need offline sync and client-side SDKs.
Use it whenYou're shipping a mobile app first and want the client to read and write data directly, including while offline.
Trade-offA document store without SQL joins; hard to migrate off.
- You want the database, auth and file storage in one project, and plain SQL you can take elsewhere
Use it whenYou want one service for most of the backend and a SQL database you can take with you.
Trade-offAuth, storage and database in one vendor makes leaving harder later, and free projects pause after a week without activity.
At a glance
| Used by | 187 makers' products · 78 open-source projects | 573 makers' products · 90 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 | $9.66/mo Blaze (pay as you go) | $25/mo Pro |
| Moved to it on GitHubpull requests since Oct 2024 | 113 from Supabase | 297 from Firebase |
| Downloads | 9.5M/wk−22% vs npm | 25.4M/wk+91% vs npm |
| Pricing | Free Spark plan; pay-as-you-go Blaze plan. · paid from Pay as you go (Blaze) | Free tier (inactive projects pause); paid plans per project plus usage. · paid from $25/mo |
| Free tier | Yes | Yes |
| Open source | No | Yes · self-hostable |
| Incidents, 90 daysfrom its status page | no public status feed | 25+ (6 major) |
Which makers on your framework pick
Makers' products built with each framework that chose either one, for database.
| Framework | |||
|---|---|---|---|
| 32 | 171 | All 382 Next.js products' picks → | |
| 16 | 15 | All 73 React products' picks → | |
| 3 | 7 | All 27 Astro products' picks → | |
| 1 | 3 | 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 | 19% 5 | 19% 5 | 27 |
| 2023 | 21% 8 | 34% 13 | 38 |
| 2024 | 19% 51 | 34% 92 | 270 |
| 2025 | 13% 41 | 54% 174 | 323 |
| 2026 | 9% 37 | 63% 252 | 397 |
Cost as you grow
Both cost $0 up to 0.5 GB; from 1 GB Firebase costs less ($0 vs $25); from about 20 GB Supabase does ($27 vs $28).
The numbers, plan by plan
| Database size | Firebase | Supabase |
|---|---|---|
| 0.5 | $0 Spark (free) | $0 Free |
| 1 | $0 Spark (free) | $25 Pro |
| 5 | $5.16 Blaze (pay as you go) | $25 Pro |
| 8 | $9.66 Blaze (pay as you go) | $25 Pro |
| 20 | $28 Blaze (pay as you go) | $27 Pro |
| 50 | $73 Blaze (pay as you go) | $36 Pro |
| 100 | $148 Blaze (pay as you go) | $70 Pro |
| 500 | $748 Blaze (pay as you go) | $345 Pro |
Who moves from one to the other
Public pull requests on GitHub since Oct 2024 whose title says "Firebase to Supabase" or the reverse — real code changes, by developers in general rather than makers only.
- Migrate shared state from Supabase to Firebaseryanlay/tcfdlabschool.github.io · 2026-10-01
- Migrate database from Supabase to Firebase FirestoreubcWiCS/marketing-manager · 2026-09-30
- Migrate backend from Supabase to Firebase (specs + steering)livanuj/homemade_Uno · 2026-09-29
- Migrate backend from Supabase to Firebase: Firestore, Auth, Functions and client adapterJanStoutBlack/rankride · 2026-09-28
- feat: migrate backend from Supabase SQL to Firebase Firestore NoSQLparthasdey2304/paisa-lainden · 2026-09-27
- feat: migrate auth from Supabase to Firebase with Google OAuthSushma-1206/ai-pr-copilot · 2026-09-26
- feat: migrate Supabase to Firebase - fixes 504 timeoutAdinath-Jagtap/TripTogether · 2026-09-26
- feat: migrate admin data from Supabase to Firebasebustmartin05/barriguita · 2026-09-25
- feat(auth): migrate from Supabase to Firebase Authenticationfer-araujo/solarpanel-system · 2026-09-22
- Migrate backend from Supabase to FirebaseJoeK1973/RC-Endurance-Pit-Wall · 2026-09-22
- feat migrate auth and data from Firebase to Supabasezabdax/callimachus · 2026-10-02
- feat: migrate from Firebase to Supabase with offline-first support an…xabhishek54/personal-finance-tracker · 2026-09-30
- Start Firebase to Supabase migrationapurbabhaiya/Apurba-Roy · 2026-09-29
- Foundation: connect Firebase sessions to Supabase toolkit accountswinningj26-prog/aiStudio-BudgetPlanner · 2026-09-29
- Foundation: connect Firebase identity to Supabase account servicewinningj26-prog/aiStudio-BudgetPlanner · 2026-09-29
- Migrate from Firebase to Supabase for auth, database, and storagekaitodecode/nyated.adikurniawan.com · 2026-09-27
- Firebase to self-hosted Supabase migration + accumulated Beta feature worksandschi/StreamCast-Pro · 2026-09-26
- Migrate authentication provider from Firebase to Supabasesametboy112-ctrl/JOKERWEB · 2026-09-25
- Migrate the backend from Firebase to Supabase PostgreSQL with RLSmonarch7107/Mohammed-Fazil-Cattery- · 2026-09-24
- Remove Firebase completely and migrate to Supabaseyouknowwalid/MD-WALID-RAHMAN · 2026-09-24
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.
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.
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.
Firebase was chosen because its Realtime Database and seamless integration allow the application to instantly sync AI tutoring feedback directly to a user's device.
One Postgres with RLS on every table is the reason a solo founder can ship contracts, invoices and a client portal without a backend team. Auth, storage and realtime came for free.
For powering our backend and database. Managing user uploads and conversion jobs efficiently is critical, and Supabase's real-time capabilities keep everything running smoothly! 🔥
Supabase is CatDoes' backend. We use their database, auth, storage, and real-time features. A platform like CatDoes requires a stable and scalable backend, and Supabase is providing that!
Loved and watch-outs
Themes that recur in makers' words and Hacker News comments, each linked to what it summarises.
- Auth, Firestore, Cloud Functions and hosting wire up in minutes, the fastest path to a working backend for a solo developer. PHHN
- Real-time sync across devices, with offline caching that remains stronger than most all-in-one rivals. PHHN
- The free tier and serverless pricing keep costs near zero when starting out. PHPH 2
- A server-side change made the iOS SDK crash apps everywhere, exposing the risk of a closed SDK you cannot control. HNHN 2HN 3HN 4
- It feels neglected and bolted onto Google Cloud, and it cannot be self-hosted, so leaving means a full migration. HNHN 2HN 3
- Client-accessible databases guarded only by optional security rules are a common cause of data leaks. HNHN 2
- One project covers Postgres, auth, storage and realtime, so a solo founder ships without stitching vendors or hiring a backend team. PHPH 2PH 3PH 4
- It is real Postgres with SQL, row-level security and pgvector rather than a proprietary store. PHPH 2PH 3PH 4
- Open source and self-hostable, which reduces vendor lock-in. PHPH 2HNPH 3
Who uses each
What makers pair each with
Neither quite right?
See the whole database decision →Questions
Firebase or Supabase: which do makers choose?
Of the 1,263 makers' products we know the database of, 573 chose Supabase (45%) and 187 Firebase (15%); 3 use both. Among the 397 launched in 2026, Firebase is in 9% and Supabase in 63%, against 19% and 33% of those launched in 2024 or earlier. Firebase is the more common pick among React products (16 vs 15). At our calculator's default usage, Firebase comes to $9.66 a month and Supabase $25, at list prices. On GitHub, 297 public pull requests moved projects from Firebase to Supabase, and 113 the other way. Choose Firebase if mobile apps that need offline sync and client-side SDKs; choose Supabase if you want the database, auth and file storage in one project, and plain SQL you can take elsewhere.
Can you use Firebase and Supabase together?
3 makers' products we track use both, often one replacing the other or each for a different part of the product: Blink.new, Dreamflow, Lovable.
When should I pick Supabase over Firebase?
Pick Supabase if: You want the database, auth and file storage in one project, and plain SQL you can take elsewhere.
Which is cheaper, Firebase or Supabase?
At database size 8 GB, data transfer 50 GB, document or row reads 10 million reads, document or row writes 2 million writes: Firebase $9.66/mo (Blaze (pay as you go)), Supabase $25/mo (Pro), at list prices.
How do Firebase and Supabase compare in cost as you grow?
Both cost $0 up to 0.5 GB; from 1 GB Firebase costs less ($0 vs $25); from about 20 GB Supabase does ($27 vs $28). Cheapest usable plan at each scale, at list prices.
Are people switching from Firebase to Supabase?
Public GitHub pull requests since 2024-10-02: 297 from Firebase to Supabase, 113 from Supabase to Firebase.