Appwrite vs Firebase
Of the 1,263 makers' products we know the database of, 187 chose Firebase (15%) and 8 Appwrite (1%). Among the 397 launched in 2026, Appwrite is in 0% and Firebase in 9%, against 1% and 19% of those launched in 2024 or earlier.
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.
Which fits you
- A Firebase-style backend — database, auth, storage, functions and messaging — that is open source and can be self-hosted.
Use it whenYou want a Firebase-like SDK experience but need the option to run it on your own servers.
Trade-offIts own document-style database API rather than plain SQL; self-hosting runs many containers.
- 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.
At a glance
| Used by | 8 makers' products · 3 open-source projects | 187 makers' products · 78 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) |
| Downloads | 59.6k/wk−45% vs npm | 9.5M/wk−22% vs npm |
| Pricing | Free to self-host; Appwrite Cloud has a free plan and paid per-project plans with usage limits. | Free Spark plan; pay-as-you-go Blaze plan. · paid from Pay as you go (Blaze) |
| Free tier | Yes | Yes |
| Open source | Yes · self-hostable | No |
Which makers on your framework pick
Makers' products built with each framework that chose either one, for database.
| Framework | |||
|---|---|---|---|
| 0 | 32 | All 382 Next.js products' picks → | |
| 0 | 16 | All 73 React products' picks → | |
| 0 | 3 | All 27 Astro 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 | 0% 0 | 19% 5 | 27 |
| 2023 | 3% 1 | 21% 8 | 38 |
| 2024 | 1% 4 | 19% 51 | 270 |
| 2025 | 1% 2 | 13% 41 | 323 |
| 2026 | 0% 1 | 9% 37 | 397 |
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.
Imagine is powered by Appwrite Cloud as its core infrastructure layer. We use Appwrite’s databases, auth, storage, messaging, and realtime services to generate production-ready applications, and Appwrite Sites to handle hosting and global distribution for every app Imagine creates.
Rubium has it's back-end fully powered by Appwrite Cloud, we always trusted the team and their awesome services thanks to the great documentation, ease of use and security compliance.
We used Appwrite to handle all the heavy backend stuff - user accounts, database, storage. It saved us time and headaches, so we could focus on building the actual product.
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.
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
Who uses each
What makers pair each with
Neither quite right?
See the whole database decision →Questions
Appwrite or Firebase: which do makers choose?
Of the 1,263 makers' products we know the database of, 187 chose Firebase (15%) and 8 Appwrite (1%). Among the 397 launched in 2026, Appwrite is in 0% and Firebase in 9%, against 1% and 19% of those launched in 2024 or earlier. Choose Appwrite if A Firebase-style backend — database, auth, storage, functions and messaging — that is open source and can be self-hosted; choose Firebase if mobile apps that need offline sync and client-side SDKs.

