Step 3 of 6
Ship with confidence.
The gap between “code merged” and “feature live” is where things break. Percentage rollouts let you close that gap safely. Start with 5% canary. Monitor real metrics. Expand when you're confident. Roll back instantly if something goes wrong — no deploy, no waiting.
Canary releases
Roll out to 5% of users first. Watch error rates. If clean, expand to 25%, 50%, then 100%. Roll back instantly if needed.
Ring deployment model
Internal team → beta users → half production → full rollout. Each ring validates before the next. Progressive delivery built in.
Instant rollback
Set the slider back to 0%. All users immediately return to the default variant. No deploy, no revert PR, no waiting for CI.
Gradual Rollout
Flag: new-checkout-flow
0%
of users receiving this flag
Deployment Rings
1
Canary
Internal team + early adopters
5%
500 users
2
Ring 1
Beta users, 25% of production
25%
2,500 users
3
Ring 2
Half of all users
50%
5,000 users
4
Ring 3
Full rollout — 100% of users
100%
10,000 users
User Distribution10,000 total users
10,000 excluded