backstage
Backstage is an open framework for building developer portals
Backstage: a catalog that holds a developer portal together
Backstage is an open source framework for building developer portals. The README centers it on a software catalog that keeps track of services, libraries, and the rest of your tooling.
A portal built around a catalog
The pitch is an open source framework for developer portals, where a centralized software catalog restores order to microservices and infrastructure. Product teams get to ship code quickly without giving up autonomy. The project is TypeScript under Apache-2.0 and dates back to the start of 2020.
What it bundles
Three pieces carry the weight. Software Catalog manages software like microservices, libraries, data pipelines, websites, and ML models. Software Templates spin up new projects and standardize tooling against the organization's best practices. TechDocs makes technical documentation easy to create, maintain, find, and use, treating docs as code. Open source plugins sit on top and extend all of it.
Where it came from
Spotify created Backstage, and it now lives at the Cloud Native Computing Foundation as an Incubation level project. The README also opens with a seasonal note that maintainer responses can slow down during the summer holidays, which reads like a small peek into how the project actually runs day to day.
What the docs point to
The README routes people outward: a roadmap with delivered milestones, Discord for support, RFCs that shape technical direction, an FAQ, a code of conduct, a list of adopters, a blog, and a newsletter. Sensitive security issues get reported through Spotify's bug bounty program rather than GitHub, which is a notable choice for a CNCF project.
Editorial conclusion
The catalog idea is what makes Backstage cohere: one place that knows about your software, templates, and docs. Whether a portal needs all of that is a question each team answers for itself.
Community notes