Statsig, a company founded by former Facebook engineers, has developed a unique approach to software releases, balancing the need for rapid iteration with the necessity of maintaining a stable platform. Initially, their release process involved a lively in-office ritual, but as the user base grew, it became clear that this method was unsustainable due to human error risks. To address this, Statsig adopted a GitOps practice using ArgoCD and Argo Rollouts to automate and streamline releases, significantly reducing incidents and improving the lives of their oncall engineers. Central to their strategy is the use of canary rollouts, which allow gradual exposure of new software versions to detect issues early. This approach is supported by a robust system of metrics and feature gates that guide engineers in monitoring and adjusting rollouts based on system performance. While a rollback strategy is an integral part of their release plan, Statsig champions a distributed decision-making model for canary rollouts, empowering individual teams to manage their features efficiently. This practice, combined with continuous learning and adaptation, has enhanced the reliability of their product and fostered a strong experimentation culture within the team.