Set up docs MCPClickHouse Cloud offers different release channels to cater to different user needs regarding stability, access to new features, and upgrade predictability. Each channel has a distinct upgrade schedule and is meant to address the different usecases - for users that want instant access to new releases and those that want to defer upgrades to ensure they receive the most stable version of the release.
Release channel details
Learn more about release channels
| Channel Name | Description | Key Considerations | Tiers Supported |
|---|---|---|---|
| Fast (Early Release) | Recommended for non production environments. This is the first release channel for every database version upgrade | New feature access over stability. Ability to test releases in non production environments ahead of production upgrade |
Basic (default) Scale, Enterprise tiers |
| Regular | Default release channel for all multi replica services. Rollout on this channel typically begins two weeks after the Fast release channel starts. |
Default/ fleetwide upgrades. Services are upgraded gradually over multiple weeks |
Scale and Enterprise |
| Slow (Deferred) | Recommended for those more risk averse users that want their services to be upgraded towards the end of the release schedule. Rollout on this channel typically begins two weeks after the Regular release channel starts. |
Maximum stability and predictability. Meant for those that need more testing of new releases on either the Fast/Regular channel |
Enterprise |
Scheduled upgrade windows are available for all release channels for services in the Enterprise tier. This feature allows you to configure a time window on a given day of the week for upgrades.
Release schedule
| Version | Fast Channel | Regular Channel | Slow Channel | |||
|---|---|---|---|---|---|---|
| Start | End | Start | End | Start | End | |
| 26.6 | 2026-09-07 | TBD | TBD | TBD | TBD | TBD |
| 26.4 | 2026-06-22 | 2026-07-16 | 2026-08-03 | 2026-09-07 | TBD | TBD |
| 26.2 | Completed | |||||
| 25.12 | Completed | |||||