Feature flags per environment with percentage rollouts, evaluated inside your app so a flag check is never a network call.
Running. Flags runs on this site and in a Flutter app today. Targeting by attribute or cohort is not built, so a rollout is a percentage rather than a rule. There is no billing on this platform yet, so nothing can be bought and nothing here has a customer.
On in development, off in production, or a percentage in between, without a deploy and without a config file somebody forgets. Each environment has its own key, so switching something on in staging cannot switch it on anywhere else.
Evaluated in your app, not ours
The client fetches the rules once and decides locally, so a check costs nothing in a hot path and our outage is not your outage. A flag nobody has defined is off, so a typo fails closed.
An audit that answers the real question
Every change records what the flag was as well as what it became. After an incident nobody asks what a flag is set to now; they ask what it was at the time.
Not built yet
Named rather than left out.
Targeting rules
Percentage rollouts and on or off. No targeting by attribute, country or cohort.
Release health
Monitor knows the crash free rate per release and Flags does not ask it yet, which is the reason to have built this here.
Billing
There is no way to pay for anything on this platform.
Built on one control plane
Flags shares an account, a project and a bill with Monitor, Analytics and the rest. Two tools that already agree on what a release is beat two tools you reconcile by hand.