Feature flags · Connected to the change
Know what
changed.
Ship with clarity.
Test a change, review the difference, and follow the version your app actually sees.
From test to observed evidence.
Explore flags, saved scenarios and a reviewable change.
One change · A clearer picture
From the first test to what runs.
- 01
Test the scenario
Save inputs and compare expected outcomes.
- 02
Review the difference
Connect the code, configuration and evidence.
- 03
Follow the version
Separate published state from reported observations.
Works where your application runs.
Evaluate flags locally in supported Browser and Node.js SDKs, with explicit fallback behavior.
React · TypeScript · Node.js · OpenFeature JS/TS
Start with the quickstartconst enabled = flags.boolean("checkout-v2", false, context);
// Reads the locally available configuration.
// Defaults and stale behavior remain explicit.Built around the decisions your team makes.
Control
Targeting, gradual rollout and environment differences.
Confidence
Saved scenarios and reviewable evidence.
Clarity
Version visibility with honest coverage limits.
- What happens during a connection outage?
- A ready SDK follows its local configuration and fallback policy. Network revocation and updates have propagation limits.
- Does no telemetry mean a failed release?
- No. Unobserved services remain unknown.
See a change end to end.
Explore an example workspace and the developer documentation.