Service catalog
single source of truth for "what services run where"
// official site: backstage.io ↗
Backstage is the open developer portal platform originally built at Spotify, now CNCF incubating. Service catalog, tech docs (TechDocs), software templates (Backstage Templates), plugin ecosystem with 100+ plugins. Centralizes "what services exist, who owns them, how to deploy" for engineering orgs.
Backstage is the open developer portal platform originally built at Spotify, now CNCF incubating. Service catalog, tech docs (TechDocs), software templates (Backstage Templates), plugin ecosystem with 100+ plugins. Centralizes "what services exist, who owns them, how to deploy" for engineering orgs.
The "internal developer platform" reference implementation — adopted by Spotify, Netflix, Expedia, Wealthsimple.
Concrete scenarios where teams pick Backstage over the SaaS alternative.
single source of truth for "what services run where"
Markdown-in-Git → rendered docs portal
golden-path "new service" generators
visualize service mesh + API consumers
add views for CI, K8s, AWS, costs, etc.
If your team profile matches one of these, Backstage is a strong fit out of the box.
with 10+ services + multiple teams
building internal developer platforms
standardizing developer workflows
needing service ownership clarity
When evaluating self-hosted options for this category, here are the dimensions on which Backstage consistently lands above the alternatives.
The stack you'll plug Backstage into — services, protocols, and adjacent apps in the BluixApps catalog.
roadiehq/community-backstage-image:latest (community quickstart)Operational guidance from running this in production — what to lock down, what surprises people.