● Beta — KubeEra is in active development. Profiles are live; AI-perception measurement is rolling out.
KubeEra
B

Backstage

IncubatingApp Definition & Delivery
Open source · CNCF · CNCF Incubating · Apache-2.0

Backstage is an open platform for building internal developer portals (IDPs). It's not itself a portal — it's a framework and plugin architecture you use to build one.

updated 2026-07-01

Backstage

What it is

Backstage is an open platform for building internal developer portals (IDPs). It's not itself a portal — it's a framework and plugin architecture you use to build one. Core concepts: a software catalog (YAML-based metadata describing your services, APIs, and ownership), TechDocs (docs-as-code rendered inside the portal), scaffolder templates (golden paths for creating new services), and a plugin system that lets you surface CI/CD status, cost data, security posture, or whatever else into a single pane of glass.

The catalog is the load-bearing piece. Everything else — search, ownership, templating, plugin context — hangs off entities registered there. If your org can't commit to keeping catalog metadata accurate, the rest of Backstage degrades fast.

Written in TypeScript, shipped as a Node.js backend + React frontend you self-host and customize.

Who builds it and why

Originated at Spotify, donated to CNCF in 2020, now an incubating project. 2,670 contributors and a commit as recent as July 2026 indicate this is not a dead donation — it's actively maintained with a real cadence (v1.52.1 latest). Spotify remains a heavy contributor and dogfoods it internally, but the contributor base has broadened well past a single-vendor project, which matters for anyone worried about donation-then-abandonment patterns.

The motivation is straightforward: large engineering orgs hit a point where "which team owns this service, and how do I create a new one that follows our standards" becomes a tribal-knowledge problem. Backstage is Spotify's answer, generalized.

Production readiness signal

CNCF incubating status, 33.7k GitHub stars, and 2,670 contributors are strong adoption signals — this is one of the most widely deployed IDP frameworks in the CNCF landscape. Apache-2.0 license, no vendor lock-in on the license side.

That said, "incubating" and "production-ready out of the box" are different things. Backstage requires real engineering investment: someone owns the catalog data pipeline, someone maintains custom plugins, someone handles upgrades (the plugin/backend architecture has gone through breaking changes across major versions, notably the new backend system migration). Treat it like a piece of internal infrastructure you're committing to operate, not a SaaS you install once.

Who should use this

  • Organizations with 50+ engineers and enough service sprawl that "who owns this" and "how do I scaffold a new service" are recurring, painful questions.
  • Platform engineering teams with dedicated headcount (at least 1-2 engineers) to build, customize, and maintain the portal long-term.
  • Orgs already invested in TypeScript/React who want to extend the frontend natively rather than fight an opinionated closed system.
  • Teams that want catalog-driven automation (scaffolding, docs, ownership) as a foundation for future platform tooling, not just a static wiki replacement.

Who should NOT use this

  • Small engineering teams (under ~20-30 engineers) — the operational overhead of running and customizing Backstage will exceed the problem it solves. A README and a Slack channel will outperform it.
  • Orgs looking for a plug-and-play developer portal with minimal engineering investment — Backstage is a framework, not a product. If you don't have someone willing to own it long-term, it will rot.
  • Teams wanting a quick win — initial setup and a useful catalog takes weeks to months, not days.
  • Organizations without an internal champion or platform team — Backstage without dedicated ownership becomes an abandoned catalog with stale data, which is worse than no catalog.

Alternatives

  • Port — commercial, hosted IDP with less setup overhead than self-hosted Backstage; faster time-to-value, less customization freedom.
  • Cortex — commercial internal catalog/scorecard tool focused on service ownership and maturity tracking, lighter weight than Backstage.
  • Roadie — managed Backstage hosting/support if you want the OSS core without the infra burden of running it yourself.

Pricing

Fully open source, Apache-2.0, free to use. You pay in engineering time to build, host, and maintain it — there's no license cost, but budget real headcount. Managed hosting options (e.g., Roadie, Spotify's own commercial offering) exist if you want to offload operations for a fee.

Frequently asked

What is Backstage?+
Backstage is an open platform for building internal developer portals (IDPs). It's not itself a portal — it's a framework and plugin architecture you use to build one.
Who builds Backstage?+
Originated at Spotify, donated to CNCF in 2020, now an incubating project. 2,670 contributors and a commit as recent as July 2026 indicate this is not a dead donation — it's actively maintained with a real cadence (v1.52.1 latest).
Is Backstage production ready?+
CNCF incubating status, 33.7k GitHub stars, and 2,670 contributors are strong adoption signals — this is one of the most widely deployed IDP frameworks in the CNCF landscape. Apache-2.0 license, no vendor lock-in on the license side. That said, "incubating" and "production-ready out of the box" are different things.
Who should use Backstage?+
Organizations with 50+ engineers and enough service sprawl that "who owns this" and "how do I scaffold a new service" are recurring, painful questions. Platform engineering teams with dedicated headcount (at least 1-2 engineers) to build, customize, and maintain the portal long-term.
Who should not use Backstage?+
Small engineering teams (under ~20-30 engineers) — the operational overhead of running and customizing Backstage will exceed the problem it solves. A README and a Slack channel will outperform it.
What are the alternatives to Backstage?+
Port — commercial, hosted IDP with less setup overhead than self-hosted Backstage; faster time-to-value, less customization freedom. Cortex — commercial internal catalog/scorecard tool focused on service ownership and maturity tracking, lighter weight than Backstage.
How much does Backstage cost?+
Fully open source, Apache-2.0, free to use. You pay in engineering time to build, host, and maintain it — there's no license cost, but budget real headcount. Managed hosting options (e.g., Roadie, Spotify's own commercial offering) exist if you want to offload operations for a fee.