PatchBee docs
Automating updates
PatchBee can roll updates out gradually and without manual approval. Rings catch problems while they are small; auto-approve removes the busywork.
Update rings (staged rollout)
Rings release a new version to groups in waves, so you catch problems before everyone gets them.
- Go to Settings → Rollout profiles.
- Create a profile with rings, for example Pilot → Broad → All.
- For each ring set the target group, a delay before it starts, and the intent (Required or Available).
New versions then advance through the rings automatically. You can pause, resume, advance, or cancel a rollout at any time.
new version → Pilot (day 0) → Broad (day 3) → All (day 7)
Example: a three-ring profile that works for most fleets
| Ring | Group | Starts | Intent |
|---|---|---|---|
| Pilot | IT team (a handful of technical users) | Day 0, immediately | Required |
| Broad | Early adopters (one department, roughly 10% of devices) | Day 3 | Required |
| All | All Company | Day 7 | Required |
A bad build surfaces in the Pilot ring within a day or two, while it is on ten machines instead of a thousand. Pause the rollout, roll the app back from Deployed Apps, and nobody outside IT ever saw the problem.
Auto-approve (hands-off)
Turn on auto-approve for an app so PatchBee approves and publishes new versions for you, after a safety delay you choose. Combine it with rings for a fully automated, staged pipeline:
detected update → auto-approved after the delay → published → rolled out ring by ring.