3.0 Rollout
Roll out to exactly who you mean.
Ordered rules, stable percentage buckets, and environment-specific defaults let you widen a release without changing code.
Practice
Release in slices that match how your product is used.
Context attributes
Pass stable user, account, plan, region, or request facts that describe the unit you are releasing to.
Ordered rule groups
Use match-all and match-any groups to make intent visible without writing custom release logic.
Stable percentages
Hash on a stable rollout key so the same user stays in the same bucket as the rollout widens.
Product proof
Rules explain the rollout order.
FeatureGate evaluates rule groups in order. The first match wins, missing attributes miss quietly, and anything unmatched falls through to the environment default.
- First matching rule wins
- Missing attributes miss quietly
- Stable rollout key keeps buckets fixed
- Fallback default handles the rest
What changes
The habit behind the feature.
Rules should read like release notes
A teammate should understand why a customer receives a behavior by reading the ordered rule list, not by asking who edited the flag last.
Percentages are a blast-radius tool
Start with a tiny slice, watch the product, then widen the percentage. If the signal turns bad, drop back to the safe default.
Environment state stays separate
A staging rollout can be wide open while production stays dark, because each environment owns its own default and rules.
Go deeper