Spotify's Backstage: an internal developer portal that became the industry standard

By the mid-2010s Spotify ran hundreds of microservices across an engineering culture built on autonomous squads. Every piece of that infrastructure had its own tool — Terraform, cloud CLIs, GitLab CI, Prometheus, Kubernetes, Docker and more — each with different interfaces, credentials and rules. Engineers were expected to know all of them, and the cost showed up as context switching, fragmentation and cognitive load.

Around 2016 Spotify's engineers started solving that with Backstage, an internal developer portal: a software catalog recording what services existed and who owned them, clickable templates that scaffolded a new microservice with best practices already in place, views that followed a pull request from review to production, and documentation written as Markdown in code and rendered in one place. By 2020 the internal installation had more than 100 plugins — one consistent front door for the whole stack.

In March 2020 Spotify open-sourced Backstage on purpose, releasing it early so other companies facing the same fragmentation could shape it — and so it could become the standard rather than a proprietary island Spotify would one day be forced to migrate away from. The Cloud Native Computing Foundation accepted it into its Sandbox that September; by 2025 more than 3,000 organizations had adopted it, all 700 of Spotify's R&D squads still depended on it, and Spotify was selling Spotify Portal for Backstage as an enterprise product.