Skip to main content

Firebase

What is Firebase​

Firebase is Google's Backend-as-a-Service (BaaS) platform. It bundles the building blocks of a typical backend into one suite: Cloud Firestore (a NoSQL document database with real-time listeners and offline cache), Authentication, Hosting, App Hosting (SSR), Cloud Functions, Cloud Storage, Security Rules, and the Local Emulator Suite. A Firebase project is a Google Cloud project — same billing, same IAM. The firebase JS SDK on npm has a modular, tree-shakeable API since v9 and is currently at v12.x. The SDK is Apache-2.0 licensed, but the hosted service itself is proprietary (Firebase Terms of Service).

Why we recommend it​

  • No backend team required — the client SDK talks directly to Firestore; Security Rules act as the API boundary.
  • Real-time and offline built in — Firestore's onSnapshot sync and IndexedDB offline cache come for free.
  • Integrated suite — auth, data, files, hosting, and functions behind one CLI and one console.
  • Mature local development — the Local Emulator Suite enables fully offline development and Security Rules testing.
  • GCP alignment — fits Aliz's Google Cloud footprint; no new vendor relationship needed.
  • Free to prototype — the Spark tier costs nothing for MVPs.

Why over alternatives​

  • vs Supabase — Postgres-based, open-source, and self-hostable. It is the best alternative when your data model is relational. Firebase wins on real-time/offline maturity and GCP alignment.
  • vs AWS Amplify — comparable scope, but only sensible if the organization is AWS-based. Aliz is GCP-aligned.
  • vs custom REST backend on Cloud Run — full control and a formal API contract, at the cost of building and operating a backend. See the detailed comparison table in the React SPA with Firebase cookbook.

When to use​

  • Greenfield React SPAs.
  • Internal tools and admin panels.
  • MVPs under time-to-market pressure.
  • Real-time collaborative features — dashboards, presence, chat.
  • Small teams without backend capacity.

When NOT to use​

  • Complex relational data — Firestore has no joins and only limited aggregations. Prefer Supabase or a custom backend.
  • Vendor lock-in concerns — Security Rules are a proprietary DSL, and migrating the Auth user store is non-trivial.
  • Cost predictability at scale — per-operation pricing can spike with real-time listeners on hot collections.
  • Strict enterprise SLA or data-residency requirements.
  • Formal multi-client API contracts — SDK access is not a published API surface; third-party consumers need REST/GraphQL.
caution

For enterprise engagements, review the enterprise considerations (SLAs, Auth data residency, Identity Platform upgrade path) in the React SPA with Firebase cookbook before committing.

Pricing​

The Spark plan is free (no credit card) with generous quotas — good for prototypes. Blaze is pay-as-you-go at GCP rates (free quotas still included) and is required for Cloud Functions and outbound network calls.

note

Blaze supports budget alerts but has no hard spending cap — set up alerts before launch.

Resources​