CtrlK
Firebase is a backend-as-a-service (BaaS) platform developed by [[google|Google]]. It began in 2012 as a real-time database product launched by Andrew Lee and James Tamplin and was acquired by Google on October 21, 2014. Since the acquisition, Firebase has grown into a suite of services for mobile and web application development, covering authentication, NoSQL databases, file storage, hosting, serverless functions, analytics, push messaging, crash reporting, A/B testing, machine learning APIs, and generative AI integration tools. Google states that Firebase is used by millions of applications, citing figures around three million active apps [1][2].
The platform is tightly integrated with [[google_cloud|Google Cloud]] and acts as a developer experience layer over Google Cloud primitives such as [[app_engine|App Engine]], [[google_cloud_storage|Google Cloud Storage]], [[cloud_run|Cloud Run]], and [[cloud_spanner|Cloud Spanner]]. Firebase is popular among indie developers, startups, and mobile teams who need to ship a working backend without operating servers. In 2024 and 2025 the platform was repositioned around AI-assisted application development with the launches of Genkit, Firebase AI Logic, and Firebase Studio [3][4].
| Field | Value |
|---|---|
| Type | Backend-as-a-service (BaaS) |
| Industry | Cloud computing, application development |
| Founded | 2011 (as Envolve), 2012 (as Firebase) |
| Founders | [[andrew_lee |
| Acquired | October 21, 2014 by [[google |
| Parent | Google LLC |
| Headquarters | Mountain View, California, United States |
| Website | firebase.google.com |
Firebase traces its lineage to Envolve, a chat-as-a-service startup founded in 2011 by [[andrew_lee|Andrew Lee]] and [[james_tamplin|James Tamplin]]. Envolve provided a hosted chat widget that developers could drop into sites with a few lines of JavaScript, and the underlying infrastructure had to keep browser clients in sync over WebSocket-style connections [5]. Tamplin and Lee discovered that customers were using Envolve in unusual ways, sending non-chat data such as game state, presence, and notifications through the chat channel because it was the only piece of real-time infrastructure they had access to [6]. Rather than continue to bolt new features onto Envolve, the founders decided to expose the data sync engine itself as a standalone product.
That product launched as Firebase in April 2012, with a JavaScript SDK and a JSON tree data model that synchronized changes between connected clients in milliseconds [5]. The [[firebase_realtime_database|Realtime Database]] was the only feature at launch, and the company positioned itself against alternatives such as Parse and Pusher. Firebase emphasised an event-driven API where clients listened for changes rather than polling, automatic conflict resolution for offline writes, and security rules expressed as JSON-like declarative expressions on the server.
The company raised early-stage capital quickly. A $1.1 million seed round closed in June 2012 with Flybridge Capital Partners, Founder Collective, and angel investors [7]. A $5.6 million Series A led by Union Square Ventures followed in June 2013, with USV partner Albert Wenger joining the board [8]. By the end of 2013, Firebase had grown to roughly 110,000 registered developers [6].
On October 21, 2014, Google announced that it had acquired Firebase. Greg DeMichillie, then a Google Cloud Platform product director, wrote on the Google Cloud blog that Firebase would join Google to help mobile and web developers build apps more quickly [1]. Tamplin and Lee continued to lead Firebase as a brand within Google Cloud rather than being absorbed into a different team [2].
Firebase Hosting, a CDN-backed content host, had launched in 2014 just before the acquisition and was tightened into the developer console after the deal [9]. FirebaseUI, drop-in components for sign-in, was released in 2015. Firebase Storage arrived a year later, backed by [[google_cloud_storage|Google Cloud Storage]] [10].
The most consequential moment came at Google I/O 2016 in May. Google rebuilt Firebase into a unified application development platform, layering in Firebase Authentication, Firebase Cloud Messaging (replacing Google Cloud Messaging), Firebase Analytics, Firebase Remote Config, Firebase Crash Reporting, Firebase Test Lab, Firebase Performance Monitoring, and Firebase Dynamic Links, alongside the original Realtime Database and Hosting [11]. The I/O 2016 reset also unified billing across all services into the Spark and Blaze plans.
Firebase is composed of more than fifteen services. The table below lists the principal products with their public launch year.
| Product | Category | Launched | Notes |
|---|---|---|---|
| [[firebase_realtime_database | Realtime Database]] | Database | April 2012 |
| [[firebase_hosting | Firebase Hosting]] | Web hosting | 2014 |
| [[firebase_authentication | Firebase Authentication]] | Identity | May 2016 |
| Firebase Cloud Messaging (FCM) | Messaging | May 2016 | Push for [[android |
| Firebase Remote Config | Feature flags | May 2016 | Server-controlled parameters and rollouts. |
| Firebase Test Lab | QA | May 2016 | Cloud device farm for Android and iOS. |
| Firebase Performance Monitoring | Observability | May 2016 | Network and rendering traces from real devices. |
| Firebase Dynamic Links | Linking | May 2016 | Deferred deep links; shut down August 25, 2025 [12]. |
| Cloud Storage for Firebase | Storage | May 2016 | Backed by [[google_cloud_storage |
| Google Analytics for Firebase | Analytics | May 2016 | Folded into [[google_analytics |
| Firebase A/B Testing | Experimentation | March 2017 | Built on Remote Config and Analytics. |
| Cloud Functions for Firebase | Serverless | March 2017 (beta) | Node.js, Python, Go; v2 on [[cloud_run |
| [[crashlytics | Crashlytics]] | Crash reporting | Joined Firebase 2017 |
| [[cloud_firestore | Cloud Firestore]] | Database | October 2017 (beta), January 2019 (GA) |
| Identity Platform | Identity (enterprise) | April 2019 | GCP Authentication with SAML, OIDC, MFA. |
| Firebase In-App Messaging | Messaging | 2018 | Contextual messages inside the app. |
| Firebase App Distribution | Beta delivery | March 2019 | Pre-release builds to testers. |
| [[ml_kit | ML Kit]] | On-device ML | May 2018 |
| Vertex AI for Firebase / Firebase AI Logic | Generative AI | April 2024, renamed 2025 | Client SDKs for [[gemini_api |
| [[genkit | Genkit]] | AI framework | May 2024 |
| [[firebase_studio | Firebase Studio]] | Cloud IDE | April 2025 |
The [[firebase_realtime_database|Realtime Database]] stores data as one large JSON tree and pushes updates to listening clients over a persistent connection. It pairs well with collaborative apps and game lobbies but has well-documented scaling characteristics, including a recommended ceiling of around 200,000 simultaneously connected clients per database instance [13].
[[cloud_firestore|Cloud Firestore]], announced in beta on October 3, 2017 and reaching general availability on January 31, 2019, is the modern successor [14]. Firestore stores data as collections of documents, supports stronger queries with composite indexes, automatic multi-region replication, and uses [[cloud_spanner|Cloud Spanner]] for parts of its consistency layer. Firestore enforces limits including one sustained write per second per document and ten thousand writes per second per database in its older multi-region modes, though Google has launched higher-throughput Enterprise Edition tiers.
[[firebase_authentication|Firebase Authentication]] launched at I/O 2016 and supports email and password, phone number with SMS one-time codes, anonymous sessions, custom token signing, and federated identity with Google, Facebook, Apple, Microsoft, GitHub, Yahoo, X (formerly Twitter), and any [[oidc|OIDC]] or [[saml|SAML]] provider. Token verification uses standard JSON Web Token signatures, letting backend services validate Firebase identities without contacting Google [15].
Identity Platform, announced in April 2019, is a GCP-branded superset that adds multi-factor authentication, SAML federation, OpenID Connect, tenant isolation, blocking functions, and an SLA. The two products share an underlying service, and customers can upgrade a Firebase project to Identity Platform without rewriting client code [16].
Cloud Functions for Firebase entered public beta in March 2017 and reached general availability in 2018. Functions can trigger on Firestore writes, Realtime Database changes, Cloud Storage uploads, Authentication events, FCM topics, HTTP requests, and scheduled crons. The platform initially supported only Node.js, then added Python and Go. Cloud Functions v2, generally available in 2022, runs on top of [[cloud_run|Cloud Run]] and inherits its concurrency and scaling characteristics [17].
[[crashlytics|Crashlytics]] was founded in 2011 by [[wayne_chang|Wayne Chang]] and [[jeff_seibert|Jeff Seibert]] in Boston as a stand-alone iOS crash reporting service. It was acquired by Twitter in January 2013 and made the centerpiece of Twitter's mobile developer suite [[fabric_io|Fabric]]. On January 18, 2017, Google announced that it had acquired Crashlytics and the rest of Fabric from Twitter [18]. Over the following two years, Google migrated Crashlytics into Firebase, deprecating Firebase Crash Reporting in 2018 and shutting down the Fabric brand in early 2020 [19].
[[ml_kit|ML Kit]] launched at Google I/O 2018 as a set of mobile-first machine learning APIs covering text recognition, face detection, barcode scanning, image labeling, landmark recognition, smart reply, language identification, on-device translation, and the ability to run custom [[tensorflow_lite|TensorFlow Lite]] models. In 2020, Google split ML Kit into a fully on-device variant that no longer required a Firebase project [20].
In April 2024, Google announced Vertex AI for Firebase, a set of client SDKs that let mobile and web apps call the [[gemini_api|Gemini API]] directly while still benefiting from Firebase App Check, quotas, and Authentication. The service was renamed Firebase AI Logic in 2025 to reflect its expansion beyond a single model provider [3].
At Google I/O on May 14, 2024, Google announced [[genkit|Genkit]], an open-source AI application framework for Node.js and Go that integrates cleanly with Firebase, Cloud Functions, and the Gemini API [4]. Genkit ships flow definitions, prompt management, evaluation utilities, and a local developer UI for inspecting traces; it reached general availability in late 2024 for Node.js and in 2025 for Go.
[[firebase_studio|Firebase Studio]] was unveiled at Google Cloud Next on April 9, 2025 in Las Vegas, replacing the earlier Project IDX experiment. Firebase Studio is a browser-based IDE that combines a coding workspace, Gemini-powered chat, an App Prototyping agent that can scaffold an app from a natural-language prompt, and direct deployment to Firebase Hosting [21].
Firebase uses two billing plans that have been stable since 2016.
The Spark Plan is a free tier that covers many small applications without payment information on file. Quotas include 1 GB of Firestore storage with 50,000 document reads per day, 10 GB of Hosting storage with 360 MB of daily transfer, 5 GB of Cloud Storage, 10,000 monthly phone-based Authentication verifications, and Realtime Database capped at 100 simultaneous connections and 1 GB of stored JSON [22].
The Blaze Plan is pay-as-you-go and is required to call most Google Cloud APIs from Cloud Functions, including outbound HTTPS requests to non-Google services. Blaze includes the Spark quotas as a free allowance and bills only for usage above them. Cloud Functions and Cloud Run-backed services are charged per invocation, per gigabyte-second of memory, and per gigabyte of egress, while Firestore is charged per document read, write, and delete plus storage and egress [22].
The Blaze model has drawn criticism because pay-as-you-go scales linearly with traffic, so a viral moment can produce a surprise bill, and Google does not currently offer hard spending caps on Firebase projects, only budget alerts.
Firebase is not a stand-alone cloud. Each Firebase project maps to a [[google_cloud|Google Cloud]] project, and most Firebase services are thin developer-experience layers over a Google Cloud primitive: Firestore runs in part on [[cloud_spanner|Cloud Spanner]] and Google's Megastore lineage, Cloud Storage for Firebase exposes Cloud Storage buckets, Cloud Functions v2 runs on [[cloud_run|Cloud Run]], Hosting uses Google's edge CDN, and Authentication shares its backend with Identity Platform [23].
Clients talk to Firebase through SDKs available for the web (JavaScript and TypeScript), Android (Java and Kotlin), iOS (Swift and Objective-C), [[flutter|Flutter]] (Dart, via FlutterFire), Unity (C#), C++ for game engines, and a REST and gRPC surface for any other runtime. The same SDK conventions are reused across services, so the same onSnapshot listener pattern works for Firestore documents whether a developer writes in Swift or in TypeScript.
Most services support data residency choices. Firestore offers multi-region locations such as nam5 in North America and eur3 in Europe alongside dozens of single-region locations, and once a Firestore database location is set it cannot be changed [24]. Realtime Database instances can be provisioned in the United States, Europe, or Singapore. Cloud Storage for Firebase inherits Google Cloud Storage's full set of regions.
Security is enforced through Security Rules, a domain-specific language for Firestore, Realtime Database, and Cloud Storage. Rules are evaluated server-side on every request and can read the authenticated user's token, fetch other documents, and call out to Cloud Functions. App Check verifies that a request is coming from a legitimate copy of the app rather than a scraper, using attestation services such as Apple DeviceCheck, Google Play Integrity, and reCAPTCHA Enterprise.
Firebase competes with a growing set of alternatives.
| Platform | Database | Open source | Self-host | Notes |
|---|---|---|---|---|
| Firebase | Firestore, Realtime DB ([[nosql | NoSQL]]) | Partial (SDKs only) | No |
| [[aws_amplify | AWS Amplify]] | DynamoDB, Aurora | Partial | No |
| [[supabase | Supabase]] | PostgreSQL | Yes | Yes |
| [[appwrite | Appwrite]] | MariaDB | Yes | Yes |
| [[pocketbase | PocketBase]] | SQLite | Yes | Yes |
| [[convex | Convex]] | Custom reactive store | No | No |
| [[backendless | Backendless]] | Java backend | No | Yes (paid) |
Developers most often choose Firebase for its mobile SDK quality and out-of-the-box Authentication, while teams needing SQL, on-premises hosting, or vendor independence frequently pick [[supabase|Supabase]] or [[appwrite|Appwrite]]. Heavy AWS shops typically default to AWS Amplify.
Public Firebase customer pages and conference talks have featured NPR One, Lyft, Halfbrick (the studio behind Fruit Ninja), Lima Sky (Doodle Jump), Trivago, Alibaba Group, Duolingo, eBay Motors, Chess.com, Venmo, Shazam, and The New York Times crossword team [25][26]. Firebase Authentication is also widely deployed by indie iOS and Android apps as the only identity layer they ship.
The platform's strongest community has historically been the indie startup crowd. The combination of a free tier, real-time data sync, and zero-ops Hosting made Firebase a default starting point for hackathon projects in the mid-2010s and for many of the React Native and [[flutter|Flutter]] tutorials of the early 2020s. Google reports that Firebase is used by more than three million active applications across the App Store, Google Play, and the web [2].
Firebase services are subject to the [[gdpr|General Data Protection Regulation]] in the European Union and the [[ccpa|California Consumer Privacy Act]] in California, and Google publishes a Data Processing and Security Terms addendum that customers sign as part of using Firebase commercially [27]. Firestore supports multi-region and single-region locations across North America, Europe, Asia Pacific, and South America.
In 2020, the launch of Apple's App Tracking Transparency framework in iOS 14 changed how mobile SDKs identified users across apps. Crashlytics and Google Analytics for Firebase published App Store privacy labels and updated their iOS SDKs so developers could disable IDFA collection in regions that required opt-in tracking. Independent privacy researchers raised concerns about the volume of identifiers Firebase Analytics sent to Google by default, prompting Google to add more granular consent controls in later SDK releases [28].
For enterprises with stricter compliance requirements, Identity Platform and Firestore Enterprise Edition offer extra controls including access transparency, customer-managed encryption keys (CMEK), and contractual SLAs.
Firebase is widely praised for developer experience but has attracted persistent criticism on several fronts.
Vendor lock-in is the most common complaint. Firestore's query language, Security Rules, and SDK conventions are proprietary, and there is no straightforward path to migrate a running app off Firestore onto a relational database without rewriting most of the data layer. The Realtime Database has the same problem. Several blog posts in 2023 and 2024 described Firebase as "a great way to start and a hard place to leave," prompting teams to start projects on [[supabase|Supabase]] or [[convex|Convex]] to keep options open [29].
Pricing surprises are a recurring theme. Because the Blaze plan does not support hard spending caps as of 2025, a viral or buggy app can produce an unexpectedly large bill. Google publishes guidance on configuring budget alerts and using Cloud Functions to disable services when usage spikes, but the burden of building those guardrails falls on the developer.
Cloud Firestore limits can bite at scale. The one-write-per-second-per-document soft limit causes contention in counters or leaderboards, where Google recommends a sharded counter pattern. The ten-thousand-write-per-second-per-database hard ceiling on the legacy multi-region mode pushed some high-traffic customers to redesign data partitioning or migrate to [[cloud_spanner|Cloud Spanner]] directly.
Dynamic Links deprecation, announced in 2024 with a final shutdown date of August 25, 2025, drew significant criticism from mobile teams who had used the product since 2016 [12]. Google directed customers to third-party tools such as Branch and Adjust, but no first-party replacement was offered.
Since 2024, Firebase's roadmap has been visibly focused on AI-assisted application development.
[[genkit|Genkit]], announced at Google I/O on May 14, 2024, is an open-source AI framework for Node.js and Go that lets developers compose calls to large language models, retrievers, and tools into flows deployable to Cloud Functions or Cloud Run. Genkit ships a local developer UI for inspecting traces and a plugin system supporting the [[gemini_api|Gemini API]], OpenAI-compatible endpoints, Anthropic, and local models served through Ollama [4].
Firebase AI Logic, the rebranded successor to Vertex AI for Firebase, gives mobile and web client SDKs first-party access to [[gemini|Gemini]] models with the proper App Check, Authentication, and quota integration that a thin REST call from a phone would not have on its own [3].
[[firebase_studio|Firebase Studio]], unveiled at Google Cloud Next on April 9, 2025, is a browser-based IDE built on Code OSS that bundles Gemini chat, terminal access, a preview server, and an App Prototyping agent. The agent can scaffold a working full-stack application from a natural-language prompt and deploy directly to Firebase Hosting [21]. Firebase Studio replaced the earlier Project IDX experiment that Google had been running publicly since 2023.
Taken together, the 2024 and 2025 announcements signal a strategic shift. Firebase is no longer simply a backend-as-a-service for hand-written apps but is increasingly positioned as the default place to build AI-native software inside the Google developer ecosystem.