Release channels: beta and stable
Choose which RevoAgent releases each device gets, for the workspace, a customer or a single device.
Updated
On this page
Every RevoAgent release is on one of two release channels. Each device follows one channel, and Revo only offers it releases from that channel.
The channels
| Channel | What it gets | Use it for |
|---|---|---|
| Stable (default) | Releases Revo has promoted after they ran well on beta | Almost every customer |
| Beta | New releases as soon as they're published, plus stable ones | A few of your own devices, a test customer, a friendly client, and platforms that only have a beta release |
A stable device is offered the newest stable release for its platform. A beta device is offered the newest of beta and stable. A device is never moved to an older version: one that's ahead of its channel (for example a device moved from beta back to stable) keeps its version until the channel catches up.
Which channel a device follows
The first setting that applies wins:
- The device's own setting: device → Settings → Agent release channel: Follow the customer, Beta or Stable.
- The customer's channel: Settings → Agent updates, or the customer's Customer settings → Install agent page.
- The workspace default: Settings → Agent updates. Stable unless you change it.
Installer links use the customer's channel too, so new devices start on the release their customer follows.
Who can change it
| Change | Who |
|---|---|
| Workspace default, a customer's channel | Owners and admins |
| One device's channel | Technicians, admins and owners |
| See channels | Everyone in your MSP team; customer-portal users see none of this |
Every change is recorded in the audit log.
A typical setup
- Keep the workspace default on stable.
- Put a test customer (or a few of your own machines) on beta, so new releases reach them first.
- Put customers with Macs, Windows on Arm or Linux ARM64 devices on beta, or set just those devices to beta.
- Watch Settings → Agent updates: it shows how many of your devices run which version on which channel. The Devices list marks beta devices with a small beta pill and can be filtered by channel.
How updates are installed
With automatic agent updates on (Settings → Agents or Settings → Endpoint policy; on by default), devices install new releases from their channel by themselves. Update agent on a device offers the newest release on its channel right away, even when automatic updates are off. Either way the agent:
- downloads the release and checks Revo's signature, version, platform, size and SHA-256;
- replaces itself and restarts its own service (the computer doesn't restart);
- goes back to the previous version if the new one can't check in.
Releases that are withdrawn, or whose signature doesn't verify, are never offered.
Related
- Device actions: update the agent
- Allowlist RevoAgent: allowlisting tools may need the new release's hash before a self-update can run.