Optimizely Graph releases and channels
Optimizely Graph follows a routine release schedule that delivers predictable improvements and reliability. Daily latest deployment releases give early access to upcoming features. Monthly standard deployment releases start from September 15, 2025, and alternate between the GraphQL Application Programming Interface (API) and the back-end Search Services each month.
Channels in Optimizely Graph
Optimizely Graph offers two release channels so each environment can balance stability with early access to new features. Choose the channel that matches the environment and the level of verification the workload requires.
Standard deployment channel
The standard deployment channel is the default, fully verified channel. Use it for production environments that require reliability and predictability.
- Endpoint – Target the (https://cg.optimizely.com) endpoint to reach the standard release.
- Stability – Optimizely tests, QA-verifies, and production-hardens features in this channel.
- Recommended use – Use the standard channel for production environments that require reliability.
Latest deployment channel
The latest deployment channel is an optional early access channel for customers who want to test upcoming GraphQL API features before general release. Use it in non-production environments to evaluate features and report issues before the change reaches the standard channel.
- Endpoint – Target the (https://latest.cg.optimizely.com) endpoint to reach early features.
- Stability – Features in this channel pass initial testing but lack full QA verification.
- Recommended use – Use the latest channel in non-production environments. Provide feedback to help improve features before Optimizely promotes them to the standard channel. Contact the assigned Customer Success Manager (CSM) to provide feedback.
Release communication
Each release ships with a detailed summary of changes so customers can plan around enhancements and fixes. Review the release notes whenever an environment picks up a new build.
Review the release notes for information about enhancements, fixes, and functionality.
What this means for you
The release schedule keeps both channels predictable and signals when new functionality reaches each environment. The following points summarize how the cadence benefits customers.
- Predictable updates – Expect meaningful improvements for the back-end Search Services and the GraphQL API on a reliable timeline.
- Customer-focused cadence – Stay informed and empowered without the disruption of unplanned or frequent changes.
- Continuous improvement – Each release ships enhancements, bug fixes, and other updates that improve the customer experience.
Routine releases do not cause downtime and do not require any customer action.