How Spotify Ships to 675 Million Users Every Week Without Breaking Things

Spotify ships weekly app updates to 675 million users across Android, iOS, and Desktop with a 95%+ success rate. Their release architecture relies on trunk-based development, a two-week release cycle with a branch cut on the second Friday, and five concentric rings of exposure (employees, alpha, beta, 1% rollout, 100% rollout) to catch bugs progressively. Feature flags decouple code deployment from feature activation, allowing risky features to bake invisibly in production before being enabled. A centralized Release Manager Dashboard aggregates data from 10 backend systems into a single color-coded view. An automated state machine called 'the Robot' handles predictable transitions (like initiating a 1% rollout after 3 AM app store approval), saving ~8 hours per cycle, while human Release Managers handle ambiguous judgment calls. The core insight is that a weekly cadence with fewer changes per release makes speed and safety mutually reinforcing rather than opposing forces.