Firebase review

Firebase is Google’s managed platform for building and operating web, mobile, and game apps without running the backend infrastructure yourself. It bundles app services rather than asking a team to assemble each piece separately.

Its databases, Cloud Firestore and Realtime Database, store NoSQL data and support real-time synchronization and offline persistence. Authentication handles sign-in with passwords, phone verification, and providers such as Google, Apple, and GitHub. Cloud Functions runs backend code in response to events or requests.

The rest of the platform covers hosting and object storage, crash and performance monitoring, mobile testing through Test Lab, messaging, and Remote Config. That breadth is the pitch: one platform for backend services and app operations, with usage-based billing once a project outgrows its free quotas. Firebase is not a fixed-price app-hosting plan; Blaze has a $0 base fee, then charges for usage beyond included amounts.

Firebase’s appeal is breadth with less infrastructure to configure. Authentication, databases, functions, hosting, crash reports, testing, and messaging sit in one product family. That can matter for a small team that needs to ship an app without first building and maintaining each backend service. In one Reddit thread, users described Firebase as useful for prototypes and small teams, and one long-time user said it helped their company get from an early product to Series A.

The free Spark plan gives projects within its quotas a way to start without a monthly platform charge. The pricing page lists 50,000 monthly active users for Authentication, 50,000 Firestore reads and 20,000 writes per day, and 10 GB of Hosting storage. Blaze keeps those no-cost quotas and adds, among other allowances, 2 million monthly Cloud Functions invocations and 120 Cloud Build minutes per day.

That makes Firebase worth considering when the stack fits its managed services and usage stays predictable. One Reddit commenter also praised its out-of-the-box authentication; that is an individual opinion, not a guarantee of fit.

The main pricing drawback is that Blaze is usage-based, not a predictable monthly bundle. The pricing page lists a $0 base fee but bills beyond free quotas; it does not publish an annual price. For example, Firestore overages are listed at $0.03 per 100,000 reads and $0.09 per 100,000 writes. Hosting transfer beyond the free tier is $0.15 per GB. Reddit commenters report concern about the lack of a hard billing cap and the risk of an unexpectedly large bill. Spark avoids overage charges by stopping services when quotas are exceeded, which can also interrupt an app.

There are product trade-offs, too. A commenter on r/webdev said Firebase’s query APIs lacked features they needed and became a headache as complexity grew. Another Reddit discussion raised lock-in concerns. Those are user reports, not universal limits, but they point to a real evaluation question: whether Firebase’s NoSQL model and query patterns suit the data your app needs. Teams wanting fixed monthly costs or more control over the backend should compare alternatives before committing.

Firebase starts at $0. Spark is free for projects within its quotas: Firestore includes 50,000 reads and 20,000 writes daily, 1 GiB of storage and 10 GiB monthly egress; Hosting includes 10 GB stored and 360 MB daily transfer; Authentication includes 50,000 monthly active users. Exceeding Spark quotas stops services until they reset.

Blaze also has a $0 base fee, but adds usage billing beyond included quotas; there is no published annual price. Its free allowances include 2 million Cloud Functions invocations monthly and 120 Cloud Build minutes daily. That is not a fixed-price upgrade: usage can grow beyond those amounts, and Google Cloud quotas apply.

Overages can add up across services: Firestore reads cost $0.03 per 100,000, Hosting transfer $0.15 per GB, and Functions invocations $0.40 per million. Phone authentication varies by country; US verification is listed at $0.01 each. Extensions are free to install, but their underlying services may cost extra. Eligible new users may get $300 in Google Cloud credit; SQL Connect has a three-month no-cost trial. Prices checked November 6, 2026.

Switching effort depends on how much of Firebase your app uses. A project built around Firestore or Realtime Database, Firebase Authentication, Cloud Functions, Hosting and Remote Config has more pieces to replace than one using Firebase for a single service. Before moving, inventory the data model, sign-in providers, function triggers, hosting setup and app integrations; each needs a destination and a migration plan.

The main lock-in risk is architectural: Firebase combines backend services, and Firestore is a NoSQL database. Teams moving to a relational-first system should plan for data-model changes, not just a database copy. The published pricing and product information does not specify Firebase data-export or migration tooling, so confirm export formats and limits in the current docs before setting a timeline.

We don’t have Reddit posts or comments in the published sources, so we can’t attribute specific reasons for leaving to Reddit users. For a switch decision, compare your actual usage, required database model and tolerance for usage-based billing against the replacement’s costs and capabilities.