Release Channels
Release channels control which software version your Atrium instance receives. Each instance is assigned to exactly one channel.
Available channels
| Channel | Audience | Description |
|---|---|---|
| stable | All production deployments | Fully tested, production-ready releases. This is the default for every customer. |
| beta | Opt-in customers | Pre-release versions with new features. Tested internally but may have rough edges. |
| staging | Internal only | Every merge to main. Used for our internal testing. Not available to customers. |
How channels work
When your instance checks in with the Control Plane, the response includes the latest version available on your assigned channel. If a new version is available, it appears in the admin dashboard (in notify mode) or is applied automatically (in auto mode).
Versions flow through channels in order:
staging → beta → stable
A version is promoted from staging to beta after internal validation, and from beta to stable after a validation period. This ensures that stable releases have been tested at multiple stages before reaching production.
Changing your channel
Channel assignment is managed in the Control Plane. To switch to the beta channel (for early access to new features), contact support. Switching back to stable is always possible — your instance will stay on its current version until the next stable release catches up.
Version numbering
Atrium uses semantic versioning:
- Major (X.0.0): Breaking changes requiring manual steps (rare). Always communicated in advance.
- Minor (1.X.0): New features, new entitlements. The normal release cadence. Safe for automatic updates.
- Patch (1.5.X): Bug fixes and security patches. No new features.