operate
Staged / Canary Rollout
1% → 10% → 50% → 100% with an automatic error gate.
What you get
Automatic error gate
At each traffic stage, ZipLoom monitors the error rate for the new version. If it exceeds the baseline, the rollout pauses and traffic shifts back to the previous version automatically — no manual intervention required.
Configurable stages
Default stages: 1% → 10% → 50% → 100%. You can configure the percentages, the duration at each stage, and the error rate threshold that triggers a pause. Some deployments warrant a longer soak at 10%; some can go straight to 50%.
Ship slowly when it matters
Not every deploy is equal. A dependency update with no user-facing changes can go 100% immediately. A payment flow change should go slowly. Staged rollout gives you the tools to make that distinction without building it yourself.
How staged rollout works
- 1
Enable staged rollout on a project in Settings → Rollout.
- 2
Configure your stages, durations, and error threshold.
- 3
When you deploy, ZipLoom routes a percentage of traffic to the new version using weighted routing on the target platform.
- 4
The synthetic monitor watches the error rate for both versions.
- 5
If the error rate exceeds the threshold, the rollout pauses and traffic reverts to the stable version.
- 6
You receive a notification with the error details. You can manually resume or abort.
Related features