Firebase Remote Config: What It Is, Pricing & Alternatives

Overview

Firebase Remote Config is a Google cloud service that changes an app’s or server’s behaviour without releasing an update: developers define in-app defaults and override them from the Firebase console or backend APIs^[22]. Conditions target users by app version, language, Google Analytics audience, imported segment or custom signals; rollouts release features gradually using parameters as feature flags and compare results against an automatically provisioned control group using Crashlytics and Analytics data; and real-time Remote Config lets apps receive newly published values without polling^[22].

A project can hold 3,000 parameters per template type, keep up to 300 template versions and run up to 24 A/B experiments and rollouts combined^[22]. On Firebase’s pricing page, Remote Config is listed as up to 100,000 requests per day per project on the no-cost Spark plan and no-cost up to that level on the Blaze plan, with charges for usage above it starting on 1 September 2026; A/B Testing is listed as no-cost^[21]. Remote Config is the default choice for Firebase mobile apps, but its tight coupling to Google Analytics and Firebase, limited governance and per-project limits make it less suitable as an organisation-wide flag system.

What Firebase Remote Config does

Conditions by version, language, audience, custom signals
Rollouts with automatic control groups
Real-time config updates
A/B Testing integration
Personalization with machine learning
Server templates

Firebase Remote Config pricing

Spark (no-cost): up to 100,000 requests per day per project. Blaze: no-cost up to 100,000 per day per project; usage above that charged from 1 September 2026. A/B Testing: no-cost.