Safer Release Cycles with Canary Deployments

This is an informational update about our release cycles.

We have improved our CI/CD pipeline to reduce the risk of deploying new versions. Deployments now use canary instances that receive a small portion of live traffic. Once the new version is validated under real usage, traffic is gradually moved to the updated production instances until 100% is on the new version.

Any error found in the canary instances will trigger an immediate rollback to the latest stable version.

• We deliver safe, small updates daily or several times per week. Larger feature releases are typically deployed on weekends during low-traffic periods.

• Hotfixes for critical issues are deployed the same day, usually immediately or within a few hours.

• We also use AI assistance to automatically investigate issues detected in production and propose fixes, speeding up resolution before engineers may even become aware of the problem.

Some larger features or refactorings may be released less frequently, typically around once per month. In rare cases, if a change carries increased risk, we may notify customers in advance.