Backstage 2026: From Service Catalog to AI Hub for Developer Portals

📷 "Twinkling Backstage, Diana Eng's Fairytale Fashion Show at Eyebeam NYC / 20100224.7D.03564.P1.L1 / SML" by See-ming Lee (SML) is licensed under CC BY-SA 2.0. To view a copy of this license, visit https://creativecommons.org/licenses/by-sa/2.0/.

In March 2026, the cloud-native community gathered in Amsterdam for KubeCon + CloudNativeCon Europe — and with it, the growing Backstage community for the now fifth BackstageCon. While Spotify published the documentation “Spreadsheet to Standard,” tracing the journey from an internal Excel list to a CNCF incubation project, it became clear: Backstage is far more than a service catalog. It is evolving into the central control plane for developer portals — and is increasingly becoming the interface between humans and AI agents.

What Backstage is today

Backstage was born out of necessity at Spotify in 2016: hundreds of microservices, no overview, no standard. The team built an internal portal — and donated it to the open-source world in 2020. Today, Backstage is a CNCF incubation project, used by over 3,400 organizations and serving more than two million developers outside Spotify. Its market share among developer portal frameworks is estimated at 89 percent.

The core features have proven themselves:

Software Catalog: A central directory of all services, libraries, databases, ML models, and their owners. Each entity is modeled via YAML descriptions.
Software Templates: Pre-built “Golden Paths” for creating new services with built-in best practices — from repository to CI/CD to monitoring.
TechDocs: Documentation as code — Markdown files directly in the repository, automatically indexed and searchable.
Kubernetes Plugin: Service-oriented view of Kubernetes resources, cloud-agnostic and without CLI requirement.

Since September 2024, the New Backend System is stable, which fundamentally modernized the plugin architecture. The old legacy backend was removed in December 2024. Backstage has since followed a monthly release cycle — always on the Tuesday before the third Wednesday of the month.

AI and MCP: Backstage as a foundation for AI agents

The most important trend in 2026 is the integration of AI into developer portals. Backstage has responded with several innovations:

Actions Registry and MCP Server Support: Since the end of 2025, Backstage installations can communicate with AI assistants via the Model Context Protocol (MCP). This means: AI coding agents like Claude Code or Cursor can directly access the Software Catalog, Templates, and TechDocs — and thus act contextually aware.

AiResource Catalog Kind: Since v1.54, the catalog supports a new entity type AiResource with fields for plugins, allowed tools, licenses, and compatibility information. This makes AI models, agents, and AI workflows first-class citizens in the developer portal.

Spotify itself uses these integrations productively: Their in-house AI Knowledge Assistant, connected via an MCP service, reduced developers’ so-called “goalie workload” by 47 percent. This refers to the time developers spend answering requests that could actually be automated. Spotify manager Tyson Singer summed it up at KubeCon: “AI agents amplify what’s going well in your ecosystem — and what’s going poorly.” Those with a structured catalog and clear standards benefit disproportionately.

BackstageCon 2026: Agentic Backstage and the road ahead

BackstageCon 2026 in Amsterdam showed where things are heading. Sessions like “Agentic Backstage: How to Manage an AI Software Catalog” and “Modern AI IDP: The Backstage + Kubeflow Way” made it clear: The portal is becoming a platform for managing AI workflows, models, and agents.

CNCF CTO Chris Aniszczyk emphasized: “IDPs and Backstage are becoming increasingly important in the age of agentic systems because agents rely on structured information. An IDP like Backstage provides exactly that: who owns which services, what standards apply — the information agents need to be truly effective.”

This is complemented by practical advances: The catalog now syncs entity relationships via diff (instead of full deletion), PostgreSQL deadlocks are automatically retried, and new apps receive a default GitHub Actions CI workflow as well as a configurable homepage.

Economics: Platform engineering pays off

Platform engineering is not an end in itself. The market for Internal Developer Platforms is projected to grow from an estimated $5.76 billion (2025) to $47.32 billion by 2035. Companies investing in platform engineering report dramatic improvements: Teams with mature platforms deploy 2.5 times faster and have 50 percent fewer production outages.

Toyota North America saved ten million dollars over two years with its Backstage-based platform “Chofer” — five million dollars annually in infrastructure costs alone. Individual teams reported six weeks of saved development time per project, equivalent to a value of roughly $250,000 per project.

Conclusion

In 2026, Backstage has evolved from a pure service catalog to the central infrastructure for developer portals and AI integration. With MCP support, AI-native catalog extensions, and an active community at the most important cloud-native conferences, the framework is well-positioned to tame the growing complexity of modern software development — especially in an era where AI agents scale productivity. Those who understand their developer portal not just as a dashboard but as a structured knowledge base for humans and machines will ultimately have the edge.

Sources

🌐 Machine-translated from the German original, editorially reviewed. 🤖 Written with AI assistance.