Backstage — Trivia & Interesting Facts¶
Surprising, historical, and little-known facts about Backstage.
Backstage was built at Spotify to manage 2,000+ microservices¶
Spotify developed Backstage internally starting in 2016 to help its engineering teams navigate over 2,000 microservices. Before Backstage, new engineers had no centralized way to discover who owned a service, where its documentation lived, or how to deploy it.
It was open-sourced during a pandemic¶
Spotify open-sourced Backstage on March 16, 2020 — the same week much of the world entered COVID-19 lockdowns. Despite the timing, the project quickly gained traction as remote engineering teams needed better developer portals. It was donated to the CNCF just months later in September 2020.
The Software Catalog is powered by YAML files in Git repos¶
Backstage's Software Catalog works by reading catalog-info.yaml files that live alongside the code they describe. This "docs as code" approach means the catalog stays in sync with the codebase — but it also means someone has to write and maintain those YAML files, which is the number-one adoption friction point.
Backstage plugins number over 200¶
The Backstage plugin ecosystem grew to over 200 community-contributed plugins by 2024, covering everything from Kubernetes dashboards to cost monitoring. Spotify built the plugin architecture specifically because they knew a developer portal needed to integrate with every team's preferred tools.
The TechDocs feature generates documentation sites from Markdown¶
Backstage's TechDocs plugin takes Markdown files from repositories and generates a searchable documentation site using MkDocs under the hood. Spotify chose this approach because their engineers would write Markdown in their repos but wouldn't maintain a separate wiki. TechDocs made documentation a side effect of normal development.
Backstage was the fastest CNCF project to reach "Incubating"¶
Backstage moved from CNCF Sandbox to Incubating status in March 2022, approximately 18 months after donation. This was one of the fastest progressions in CNCF history, driven by adoption at dozens of major companies including American Airlines, HP, and Expedia.
The "Golden Path" concept originated at Spotify¶
Backstage popularized the concept of "Golden Paths" — opinionated, pre-built templates that guide developers through the right way to create a new service, deploy to production, or set up monitoring. The term and concept were invented by Spotify's Platform team and have since become standard platform engineering vocabulary.
Software Templates (Scaffolder) can provision entire environments¶
Backstage's Software Templates can do more than create Git repos — they can trigger Terraform runs, create cloud resources, set up CI/CD pipelines, and register the new service in the catalog. Some organizations have reduced new service setup time from two weeks of manual steps to 10 minutes through a single template.
Roadie raised $26M to offer Backstage-as-a-Service¶
Roadie, a startup founded in 2020, raised $26 million to offer a managed Backstage experience. The company bet that while Backstage is powerful, self-hosting and maintaining it requires significant engineering effort — typically 1-2 full-time engineers. This spawned a small ecosystem of managed Backstage providers.
The Backstage System Model has four entity kinds¶
Backstage models software with four core entity kinds: Components (individual software pieces), APIs (interfaces), Resources (infrastructure), and Systems (collections of the above). This taxonomy was designed by Spotify after years of trying to categorize their sprawling microservice estate and finding that simpler models always broke down.