A backend platform with a realtime document database, authentication, functions, hosting and analytics, aimed at getting a mobile application working quickly.
Do not rebuild this — but understand what you are actually buying, because it is one specific thing. **Offline sync that resolves conflicts**: a mobile application writes while disconnected, and when the connection returns the changes merge without the developer reasoning about it. That is genuinely difficult, and it is why this platform is chosen for mobile work. WHEN TO KEEP PAYING - A mobile application that must work offline and sync afterwards - A team that needs something running this month WHEN TO BUILD, AND WHAT IT LOOKS LIKE - A web application, or a mobile one that is online most of the time. Then a small server with SQLite covers it, and the shape is under Appwrite and PocketBase elsewhere in this catalogue - If you do need offline, the honest answer is an existing local-first sync library rather than writing merge semantics yourself FIRST, LOOK AT THE BILL - Priced per read, per write and per gigabyte transferred. A listener on a collection that re-reads on every change can cost more than a server would - Audit your reads before deciding anything. Most surprising invoices in this category are one query in a loop - No aggregate queries, so counting things means maintaining counters, and those counters are where consistency bugs live WHAT TO WATCH WHATEVER YOU CHOOSE - **Security rules are your entire authorisation layer**, and they are easy to get wrong in a way that exposes a whole collection. Write tests for them — the emulator supports it — and test the negative case: sign in as one user and try to read another's document - The client talks to the database directly, so any logic that must not be bypassed belongs in a rule or a function, never in the application - Vendor lock-in is real here: the query model, the rules and the functions do not port. Decide early whether you would ever need to leave, and keep a schema you could actually export THE EXIT TO KEEP OPEN Export your data on a schedule to storage you control, in a format you can read without the platform. That single job is the difference between a decision and a marriage. THE ONE-LINE VERSION Buy it for offline mobile sync. Audit your reads, test your security rules, and keep an export running.
What you lose
- Offline persistence with automatic conflict resolution on mobile, which is genuinely hard and is why people stay
- Realtime listeners that scale without you operating anything
- Crash reporting and analytics wired into the same SDK
If you would rather not build
- Appwrite, closest in shape
What it costs
as published on their pricing page
| Plan | Billed monthly | Billed yearly | Last read |
|---|---|---|---|
| — | $25/mo | — | — |
Their pricing page is where these came from. Seeing a different price? Tell us.
The escape hatch
open source · no votes, no paid placement
Supabase
$0Postgres with auth, storage and realtime, self-hostable.
supabase/supabasefree · open source
PocketBase
$0One binary covering the same job at a much smaller scale.
pocketbase/pocketbasefree · open source
Why this verdict
our own opinion · changed only by a person
30/100
Verdict no at 30. The database is replaceable; the offline SDK is the part that quietly does the most work and takes the longest to rebuild.
History
tracked since 10 Aug 2026 · nothing is ever overwritten
Questions about Firebase
answered from the record above
Is Firebase free?
No — the plan we track is $25 a month. Pay as you go with a free allowance; a small application typically lands around $25/month, rising with reads and writes.
Can you replace Firebase by building your own?
KEEP IT. The value is the network, the data or the infrastructure. Keep paying. Replacement score 30 out of 100, build time longer than it saves. Read what you lose before you decide.
How much does Firebase cost?
$25 a month on Blaze — $300 a year. Recorded 10 Aug 2026.
What do you lose by replacing Firebase?
Offline persistence with automatic conflict resolution on mobile, which is genuinely hard and is why people stay; Realtime listeners that scale without you operating anything; Crash reporting and analytics wired into the same SDK. If any of those carry weight for you, keep paying.
Is there an open-source alternative to Firebase?
Yes: Supabase, PocketBase. The prompt on this page is for when you want it your way instead.
Related entries
same category first, most replaced first
Every week, something stops being worth paying for.
New verdicts, prices that moved, entries added. One email a week. Unsubscribe in one click. Nothing is being sent yet — your address is kept here, and the first issue is the first thing it is used for.
free forever · no tracking pixel · stored here, never passed to anyone

