Percentage rollout
Also called: percentage-based rollout, gradual rollout
Last updated:
A percentage rollout exposes a feature to a configured share of users — say 10% — instead of everyone at once. Membership is decided by a deterministic hash of the user identifier and the flag key, so the assignment is stable: the same user always lands in the same bucket for the same flag.
How the bucketing works
Percentage rollout vs progressive rollout
Want the full picture? Read the concept guide: Rollout strategies →
Related terms
Feature flag
A feature flag is a conditional in your code whose value is controlled from a remote dashboard, letting you turn functionality on or off without deploying new code.
Dark launch
A dark launch ships a feature to production turned off or invisible to users, so the code runs in the live environment before anyone sees it — you reveal it later on your own schedule.
Kill switch
A kill switch is a feature flag used to disable functionality instantly in production — flip it off and every SDK stops running the risky code path within seconds, no redeploy required.
Try it in your own app
Free Solo plan covers 10 flags and 2 environments. No credit card, no demo call — sign up and ship.