Companies Using Firebase

With 10+ years in web crawling and technographic data analysis, I've examined Firebase's trajectory from a 2012 real-time database startup (founded April 2012 by James Tamplin and Andrew Lee, spun out of their chat company Envolve) to Google's flagship app development platform. Firebase's SDK now appears in 99.55% of Android apps worldwide (Statista, March 2026). This analysis draws on 14,892 enriched companies from our crawl of 42,377 active Firebase domains, cross-referenced with LinkedIn company profiles and G2 user reviews. The data below is based on our April 2026 crawl.

1. Growth trajectory

Firebase's growth curve tells a clear platform story. From a single detected domain in October 2012 to 33,987 active domains by April 2025, that's a 34,000x increase in 13 years. Two inflection points stand out: the Google acquisition in October 2014 (per TechCrunch), which tripled domain count within 18 months, and the pandemic period (2020-2021), which saw active domains double from 3,092 to 11,131. Google's continued platform expansion played a role here too: Firebase added Crashlytics (2017), ML Kit (2018), and App Distribution (2019), turning a single-product BaaS into a full app lifecycle platform. The recent peak at 33,987 followed by a decline to 23,437 by July 2025 suggests a cooldown as alternatives like Supabase ($2B valuation, per TapTwice Digital) gain traction.

"Firebase's growth from 1 domain to 34,000 in 13 years mirrors the broader shift toward BaaS platforms. The pandemic didn't create this trend; it compressed five years of adoption into two." - Mehmet Suleyman, CEO at TechnologyChecker.io

Sales Signal: Firebase's growth rate has plateaued after the April 2025 peak, and the decline to 23,437 by July 2025 is notable. The 167,469 previously detected domains that dropped Firebase include both dead projects and companies that actively migrated. Sales teams should filter for domains that are still live but no longer running Firebase, as those are the ones most likely to have switched to a competitor.

2. Customer profile

62.8% of Firebase customers have 1-10 employees, and 41.6% were founded in the 2010s. This is a platform built for small, digital-native teams. Combined with the 29.5% founded in the 2020s, over 71% of Firebase's customer base is under 15 years old. The typical Firebase customer is a startup or small team that chose Firebase for rapid prototyping, then stayed because migration costs are high.

Enterprise detections tell a different story. Samsung, Accenture, and HP all appear in our data, but their detection URLs (asbhispam-hml.accenture.com, ndpe.unilever.com) reveal these are internal tools and microsites, not company-wide infrastructure. Firebase's own published case studies confirm this pattern: American Express used Firebase Test Lab specifically for mobile app testing and cut test costs 50% (firebase.google.com/case-studies/american-express). eBay uses Firebase ML on a single product (eBay Motors) for image categorization (firebase.google.com/case-studies/ebay). Gameloft uses Firebase Crashlytics to track crashes and boosted session duration 16% (firebase.google.com/case-studies/gameloft). These are all targeted, product-team deployments rather than company-wide backends.

Sales Signal: Enterprise Firebase deployments tend to be department-level projects, not company-wide infrastructure. The detection URLs confirm this: Accenture's Firebase runs on a staging subdomain, Unilever's on an NDPE compliance microsite. These projects often lack centralized visibility. Teams selling monitoring, security, or cost-optimization tools should target these overlooked Firebase deployments specifically, since the team running the project may not even have a formal vendor relationship with Google Cloud.

3. Industry and geographic concentration

Tech-adjacent industries dominate: Software Development (7.7%), Technology/Internet (6.0%), and IT Services (5.7%) combine for 19.5% of all Firebase customers. Education is a surprise cluster at 6.2% across three sub-categories, likely driven by learning app development. No single vertical exceeds 8%, confirming Firebase as a horizontal tool.

Geographically, the US leads at 25.7% but India's 13.0% share is the real story. India's mobile-first developer culture, combined with Firebase's generous free tier, makes it the platform of choice for the country's enormous app development ecosystem. Brazil at 5.1% and Turkey at 4.5% reinforce the global south's strong Firebase adoption. English-speaking markets collectively represent about 35% of users, meaning 65% of Firebase's customer base operates outside the Anglosphere.

Sales Signal: India's 1,934 enriched Firebase companies form a distinct segment. Firebase's free Spark plan and zero-cost products like Authentication and Cloud Messaging (per firebase.google.com/docs/projects/billing) align with the cost sensitivity of India's startup ecosystem. Companies selling cloud cost management or backend monitoring should treat Indian Firebase customers as a separate market. They're likely on the Spark plan, hitting free quota limits, and evaluating whether to upgrade to Blaze or migrate.

4. Migration patterns

The Firebase-to-Supabase migration corridor is the defining dynamic in this market. Of the companies leaving Firebase, 125 switched to Supabase while only 28 moved the other direction, a 4.5:1 loss ratio. More telling: 92 of those 125 switches happened in the last 12 months alone. Supabase's momentum is backed by serious funding: $396M raised, $2B valuation, and $16M in 2024 revenue projected to hit $27M in 2025 (per TapTwice Digital, April 2025). Against Amplify JS, Firebase actually gains more companies (39 in, 17 out), reflecting that AWS-first developers sometimes find Amplify too tightly coupled.

"The Supabase migration isn't about Firebase breaking. It's about developers wanting SQL, open source, and predictable pricing. Firebase's NoSQL lock-in was acceptable when there was no credible alternative; now there is." - Mehmet Suleyman, CEO at TechnologyChecker.io

Sales Signal: Companies that recently migrated from Firebase to Supabase are in a buying window. Switching the database means they also need to replace Firebase Auth, Cloud Messaging, and Analytics, since those were bundled. Our tech stack data shows 72.8% of Firebase customers also use Google Analytics, so a Firebase-to-Supabase migration often triggers a broader Google-to-independent toolchain shift. Target the 92 companies that switched in the last 12 months.

5. Technology ecosystem

Firebase's tech stack overlap data reveals two clear patterns. First, the Google lock-in: 72.8% use Google Analytics and 72.4% use Global Site Tag alongside Firebase. This deep integration with Google's analytics stack is both Firebase's moat and its weakness, as teams that want to de-Google face a multi-tool migration.

Second, the JavaScript framework distribution is telling. AngularJS leads at 12.5%, consistent with Firebase's origins in the Angular ecosystem. Material-UI at 4.7% and Vue.js at 4.5% show the platform has diversified beyond Angular. The cloud infrastructure split across AWS (12.8%), Google Cloud (7.7%), and DigitalOcean (6.9%) means most Firebase customers use multi-cloud setups rather than going all-in on Google.

Sales Signal: The AngularJS overlap (12.5%) represents technical debt. AngularJS reached end-of-life in December 2021, so these companies need migration help. Vendors offering Angular-to-React migration or frontend modernization should target Firebase+AngularJS companies specifically.

6. G2 review signals

G2 reviews reveal a polarized user base. The top pro, ease of use (10 mentions), aligns perfectly with the 62.8% micro-business customer base. Small teams pick Firebase because it's fast to set up. The top con, cost issues (10 mentions), combined with pricing complaints (9 mentions), directly correlates with our migration data: companies leave Firebase when their project scales and costs become unpredictable.

The "black box" complaint (6 mentions) about debugging and cost control adds context. Firebase's NoSQL model means developers can't run traditional SQL queries for troubleshooting. This opacity becomes painful at scale. It's worth noting that Firebase's Spark plan shuts off access entirely once free quotas are exceeded (per firebase.google.com/docs/projects/billing/firebase-pricing-plans), which can break production apps mid-day. That cliff-edge behavior, combined with pricing opacity, explains why the 125 Supabase migrations skew toward companies that outgrew Firebase's simplicity.

Sales Signal: Firebase's Spark plan quota shutoff is a concrete pain point: when a production app exceeds 50,000 Firestore reads in a day, it stops working until midnight Pacific time (per firebase.google.com/docs/projects/billing/firebase-pricing-plans). That's when teams start searching for cost monitoring tools or considering the Blaze plan upgrade. Companies that recently hit their first quota limit are the ideal targets for observability and cost management vendors.

7. Key takeaways

1. Firebase remains the largest BaaS platform with 42,377 active domains, roughly 4x Supabase, but its growth has plateaued and declined in recent months.

2. The customer base is overwhelmingly small (62.8% have 1-10 employees) and young (71% founded after 2010). Enterprise detections are real but typically departmental.

3. India (13.0%) and Brazil (5.1%) are Firebase's strongest non-US markets, driven by mobile-first development cultures and the generous free tier.

4. The Supabase migration corridor is accelerating at a 4.5:1 loss ratio, with 92 of 125 switches in the past 12 months.

5. Firebase's Google Analytics integration (72.8%) creates deep ecosystem lock-in that slows migration but also makes departing companies replace multiple tools at once.

6. Cost unpredictability is both the top G2 complaint and the primary driver of Supabase migration.

8. Sales applications

Outreach template (for cloud cost optimization vendors): "Hi [Name], I noticed [Company] runs Firebase on [detected subdomain]. Pricing unpredictability is the #1 complaint in Firebase's G2 reviews, and our data shows 125 companies switched to Supabase last year over this issue. We help teams monitor and cap Firebase spend before bills spike. Worth a quick look?"

Targeting strategy: Filter TechnologyChecker.io for Firebase customers with 11-50 employees founded in the 2010s. These companies have outgrown the Spark plan's free quotas but haven't migrated to Supabase or a self-hosted stack. They're stuck in the Blaze plan cost uncertainty zone, which makes them receptive to cost monitoring pitches and migration consulting.

Competitive angle: The 125 companies that switched from Firebase to Supabase are rebuilding their backend stack right now. Since 72.8% of Firebase users also run Google Analytics, many of these companies are simultaneously replacing their analytics, auth, and push notification tools. On TechnologyChecker.io, filter for domains that dropped Firebase in the last 12 months and cross-reference with your product category.

For the complete Firebase company dataset, including enriched company profiles for 14,892 businesses and detection data for 42,377 domains, visit TechnologyChecker.io.