IT AI Index

Index › Vendors › Firebase Remote Config · September 2026 Edition

Firebase · 1 category · Named, not ranked

Firebase Remote Config

2Judge labels

0First choices

2Negative labels

2 of 12Models named it

1Category

September 2026 Edition. Every number here is derived from the raw labels under vendor table vv2026-09.2, every buyer segment counted.

Standing

1 label, too few to rank

A product needs 10 labels in a category before a share or quadrant is stated. Firebase Remote Config was named 1 time in Feature flags, where LaunchDarkly led with 30%. The labels and the evidence are below, counted exactly.

By buyer segmentRead the same way at every buyer size.

Small businessnot named

No model named it for this buyer.

Mid-market28 of 31

under the label threshold

Enterprise30 of 33

under the label threshold

In feature flags · each standing computed within its segment · bars are 0 to 100 · the accent bar is the product's own best reading

Standing by category

Every category where a model named Firebase Remote Config for a mid-market B2B company. Share is first choices across the direct, paraphrase, budget and scale prompts; rank is within every product named in that category.

Category	Function	Share	Rank	Negative rate	Labels	Quadrant
Feature flags	Developer platform	0%	28 of 31	100%	1	under 10 labels · led by LaunchDarkly at 30%

Movement

This is the first edition on this tier, so no move can be computed for Firebase Remote Config yet. From the next edition this section shows, per buyer segment, whether its share moved by more than the measured noise floor.

By model

How each model treated Firebase Remote Config across every prompt where it was named for a mid-market B2B company. Twelve models, six prompts per category.

Model	Negative	Labels
Claude Haiku 4.5	0	0
GPT-5.4 mini	1	1
Gemini 3.5 Flash	0	0
Perplexity Sonar	0	0
Grok 4.1 Fast	0	0
Mistral Small	0	0
DeepSeek V4 Flash	0	0
Llama 4 Maverick	0	0
Qwen 3.7 Flash	0	0
Kimi K2	0	0
GLM 4.7 FlashX	0	0
MiniMax M2.5	0	0

By framing

Which of the six questions produced the naming. By model says how often; this says asked what. The first-choice count on the right carries the marks of the models that produced it.

FramingLabels by classFirst choices

Direct0 labelsNone

Paraphrase0 labelsNone

Comparative0 labelsNone

Budget-constrained1 labelNone

Scale-constrained0 labelsNone

Negative1 labelNone

First choiceAlternativeMentionNegative2 labels in all, every segment counted; 0 of the 0 first choices count toward share, since the comparative and negative framings do not. The bar is one segment per label class, to scale within the framing.

What the models said for it

Verbatim evidence the judge attached to positive labels.

No positive label carried a quote.

And against it

Verbatim evidence attached to negative labels. A warning on a product with few labels is a warning; on a product with many, it is one voice among them.

“can work, though they’re not a full feature-flag platform in the same way” GPT-5.4 mini · Feature flags · budget prompt · soft negative

Named alongside

The products named in the same answers as Firebase Remote Config, over the 2 answers that named it. Took the first choice instead counts the answers where the other product was the first choice and Firebase Remote Config was named but was not.

ProductSame answerTook the first choice insteadHead to head

Flagsmith1 of 21Not in the top three

Unleash1 of 21Not in the top three

LaunchDarkly1 of 20Not in the top three

A head-to-head page exists where both products are in a category's top three. The other rows are the same fact without a page behind them, so they link to the product instead.

What carried it into the answer

The sites and pages cited by the answers that named Firebase Remote Config. A fact about retrieval, not a lever on the model.

Citations exist only for the models that return a source list, four of the twelve in this edition, so these counts come from 1 of the 2 answers that named Firebase Remote Config and are not a share of its labels.

Domains cited

betterconfig.dev1

docs.getunleash.io1

enterprise-software-review.contentwave.net1

featbit.co1

featureflip.io1

firebase.google.com1

getunleash.io1

growthbook.io1

harness.io1

launchdarkly.com1

Ten of the ten domain citations in answers naming Firebase Remote Config came from somebody else's page.

Pages cited

betterconfig.dev/blog/firebase-remote-config-limitations1

docs.getunleash.io/guides/feature-flag-best-practices1

enterprise-software-review.contentwave.net/article/scalable-enterprise-feature-flag-platfo1

featbit.co/self-hosted-feature-flags1

featureflip.io/blog/feature-flag-pricing-explained1

featureflip.io/feature-flag-tools1

firebase.google.com/docs/remote-config1

firebase.google.com/docs/remote-config/quotas-limits1

Pages are listed as the models cited them.

Is this your product?

Claim this page

Claiming is free and changes nothing in the data. A claimed page shows a verified contact who is told when each edition publishes and when Firebase Remote Config's standing changes by more than the noise floor; the right to propose corrections to the vendor table, meaning names the judge wrote that should or should not read as Firebase Remote Config, applied by version and listed in the change log; and a one-line description supplied by the vendor and marked as such.

It does not get any change to labels, shares or verdicts, any preview, or any say over which quotes appear. A verification link goes to your work email; an address at firebase.com is approved on the spot, any other address is reviewed by hand.

Your name and company appear on the claimed page, or the company alone if you ask below. A title and a LinkedIn address appear there too if you give them, and are left off if you do not. Your email address is never published.