Firebase Review

Firebase is the backend mobile teams still reach for first, because the iOS, Android, and web SDKs get a signed-in user and a synced document store running before anyone has written a server.

The buying question in 2026 is whether the bill stays predictable once listeners and Cloud Functions are in production, since an alert does not stop the spend. This review prices Spark and Blaze, then sets them next to Supabase, Appwrite, AWS Amplify, Convex, and Nhost.

Toolradar data: the September 2026 low-code backend ranking evaluated 109 tools, and it lists Supabase as an open-source Firebase alternative.

Firebase and Supabase both have directory pages there. A separate serverless ranking evaluated 53 tools the same month, with Convex outside the top 10.

How we compared: vendor pricing and product pages read on September 23, 2026. Firestore unit prices are Google Cloud's list rates for us-central1 (Iowa), the region selected on that pricing page.

Firebase is Google's mobile and web app development platform, a set of managed products on one Google Cloud project. Authentication, Cloud Firestore, Realtime Database, Cloud Storage, Cloud Functions, Hosting, App Hosting, and SQL Connect share that project, so the mobile app calls one stack and one bill.

Analytics, Crashlytics, Cloud Messaging, Performance Monitoring, Remote Config, and App Distribution stay no-cost on both plans. Firestore is a schemaless document database, so you ship without migrations and pay in reads instead of seats.

Realtime Database is the older JSON tree, and it is still the simpler offline sync when the data is one nested object. SQL Connect, marked new on the product list, attaches Cloud SQL for PostgreSQL when the data is relational, and it does not turn your documents into tables.

There is no seat fee, and the meter is reads, writes, storage, egress, function time, and monthly active users only if you turn on Identity Platform. App Hosting is the newer deploy path, GitHub in and Cloud Run underneath, while classic Hosting remains the static CDN.

If that git-push loop is the whole requirement, the Vercel review is the closer comparison than another database.

You create a project, register an iOS, Android, or web app, and drop in the client SDK. Security Rules, not a server you wrote, decide which documents a signed-in user can touch. That loop is why a prototype lands before a backend repo exists.

The rough edge is that the client talks to the database directly. A rule that calls get() or exists() bills those extra document reads. A query offset bills every skipped document, which makes deep pagination expensive.

A listener bills a read when a result is added, updated, or dropped, and a reconnect after 30 minutes offline is billed like a fresh query.

Cloud Functions hold the logic that must not live on the device, and they are absent on Spark, so a webhook needs a billing account. Linking that account moves the project to Blaze, and unlinking it moves the project back. Phone sign-in has required that billing link since September 2024, so a texted code cannot stay on Spark.

On Spark, crossing a plan limit in a calendar month shuts the app off for the rest of that month. On Blaze the same traffic is billed, and a budget alert does not reject the request. For other ways to run that code, see serverless platforms.

Firebase publishes two plans, not a seat grid, so you forecast usage rather than headcount. Spark needs no card, and Blaze keeps those allowances, then bills what you use past them. If the billing account is eligible, Blaze includes $300 in credit.

Google retired the old flat Flame plan in February 2022, so there is no fixed monthly ceiling left.

In us-central1, document reads are $0.03 per 100,000 and writes are $0.09 per 100,000, after the daily free reads and free writes. The caps reset around midnight Pacific time and do not roll forward, so a quiet week does not pay for a busy Tuesday.

A day with 1,000,000 reads past the free reads costs $0.30, and a day with 1,000,000 writes past the free writes costs $0.90. Only one database per project gets the free 1 GiB, so a second database pays from the first byte.

A team of five and a team of twenty pay the same Firebase bill, because there is no seat line. Convex Professional is the contrast: five developers are $125 a month and twenty are $500 before usage.

Supabase Pro, Appwrite Pro, and Nhost Pro are organization fees, so headcount does not move them, and Supabase Team and Nhost Team are each $599 a month when you need the compliance tier.

Prices below were verified on each vendor's pricing page alongside those Firestore rates. EU Convex deployments are 1.3 times the US list, and the included US usage does not apply there.

Firebase fits a mobile team that wants offline sync and Google's client SDKs, and a web team that will live with documents, security rules, and a usage bill. Spark covers Auth, Firestore inside the daily caps, Hosting, Crashlytics, and messaging with no card, which holds until server logic or a texted login forces a billing account.

It is the wrong default when the data is relational and you want SQL you can dump, because leaving means rewriting the client rather than exporting tables. SQL Connect is Cloud SQL with a trial, not a conversion of your documents, so stored documents stay on the read meter.

For a Postgres host you pick on its own, read Postgres hosting and keep a database client in the workflow.

Skip Firebase when you need a hard cost ceiling or a server you run yourself. Blaze will not stop at a budget, so the alert pages a human and the requests keep succeeding.

Supabase and Appwrite both document a Docker install, covered with the self-hosting tools roundup, and Appwrite's guide includes a DigitalOcean image that is a VM rather than another hosted backend (DigitalOcean review).

Crashlytics will not replace traces either, so cross-service latency starts with the Datadog review and the monitoring tools list. Devshot's daily brief is where a meter change like Remote Config's September price belongs. Subscribe free if you want that note in the inbox.