Flags, rollouts, and experiment assignment are delivered together in the SDK config payload, so a single fetch controls what each user sees.
Feature Flags
Ship behind feature flags, control rollouts, and run experiments — flags, rollouts, and experiment assignment are all delivered in the SDK config payload.
Read the flags & experiments docs Flags & experiments on the web Talk to the team
What feature flags gives you
Feature flags, staged rollouts, and experiment assignment.
No flash of the default value
Flags resolve before first paint rather than after hydration, so users do not see the control variant blink into the treatment — the failure mode that quietly invalidates an experiment and looks like a visual bug.
Rollouts and experiments on one assignment
Staged percentage rollouts and experiment variants come from the same evaluation, with exposures recorded when a flag is actually read — so analysis counts users who saw the variant, not everyone who loaded the page.
Remote config, and overrides for QA
Ship values, not just booleans, and refresh them without a release. Local overrides let QA pin a variant on a device without touching the rollout everyone else is on.
Built as one lightweight SDK, not five disconnected tools.
One install brings the whole platform online, with the plumbing — queueing, batching, retries, and masking — handled for you.
- One installation
- OTA bundle updates
- One identity layer
- One event schema
- Offline queueing
- Batching & retrying
- Privacy controls
- Masking by default
- iOS · Android · RN
- Server-side APIs
- Webhooks
- Data export
Feature Flags — common questions
See every journey. Fix every issue. Grow every user.
One SDK, one timeline, and one dashboard for marketing, product, and engineering.