Feature Flags
Feature Flags let you change what your application does without shipping a new build. Define a flag once, decide who sees which value with targeting rules, and read the result from your code through OpenFeature, the vendor-neutral flag standard.
Because evaluation speaks OpenFeature's remote protocol (OFREP), there's no Flagon-specific client to adopt: any OpenFeature SDK with an OFREP provider works, in any language, pointed at Flagon by URL.
Create a flag, mint an SDK key, and evaluate it in about five minutes.
The recommended path: the standard SDK plus the OFREP provider.
How it fits together
- Flags and variants are what you toggle. A boolean
flag serves
true/false; a multivariate flag serves one of several named values (string, number, or JSON). - Environments keep Production, Preview, and Development separate. The same flag can be on in one and off in another.
- Targeting and segments decide which variant a given user or request receives, from the context your app supplies.
- SDK keys authenticate evaluation, scoped to one environment.
Evaluate
Server and browser, with per-language examples.
Plain HTTP: the exact request, response, and error shapes.
Manage and operate
Create and configure flags, rules, segments, and keys programmatically.
Fix the common issues: auth errors, missing flags, values that won't change.
Read What is Flagon first for the platform concepts (organizations, environments, teams) that Feature Flags builds on.