▸ saaro:~/blog ▊ Notizen & Artikel DE
← back

📷 "Technology Abstract" by Lenharth Systems is marked with CC0 1.0. To view the terms, visit https://creativecommons.org/publicdomain/zero/1.0/.

Backstage 2026: Latest Developments in the Open-Source Standard for Developer Portals

19 July 2026 · 5 min · Martin Jochum #Backstage#Developer Portal#Internal Developer Platform#Platform Engineering#CNCF#Red Hat Developer Hub

Backstage, the open-source framework for Internal Developer Portals (IDPs) developed by Spotify and handed over to the CNCF in 2020, has evolved rapidly in recent months. With version 1.53.0, released just a few days ago, the new Spotify Portal, the growing Red Hat Developer Hub distribution, and a mature New Frontend System, Backstage is more alive than ever. This article provides an overview of the most important developments in 2025/2026.

New Releases: Backstage v1.53.0 and the Release Cadence

The Backstage project is releasing at a high tempo: Version 1.53.0 was released just a few days ago — the latest stable version. The release brings, among other things, breaking changes such as the removal of the deprecated SSE transport for MCP actions (now exclusively Streamable HTTP), stricter validation of OAuth redirect URIs, and the migration of the catalog entity page to Backstage UI (BUI). TypeScript configuration schemas now resolve and validate imported types — a step towards more type safety across the framework.

With over 33,900 GitHub stars and 7,500 forks, Backstage is one of the most active projects in the cloud-native ecosystem. The release cadence of roughly one major release every four to six weeks demonstrates the project’s maturity.

CNCF Status and Project Velocity

Backstage remains in Incubating status with the CNCF (accepted September 2020, incubation since March 2022). In March 2025, the CNCF published the document “Backstage: From Spreadsheet to Standard,” which traces the evolution from an internal Spotify tool to the global open-source standard for platform engineering. According to CNCF CTO Chris Aniszczyk, Backstage “set the global open-source standard for platform engineering in just over five years.”

Particularly noteworthy: In the CNCF’s annual Project Velocity Reports, Backstage improved from 8th place (2020, among 100 projects) to 6th place (2025, among over 230 projects) — a clear sign of growing community activity and adoption.

Spotify Portal for Backstage: GA Since October 2025

In October 2025, Spotify announced the General Availability of Spotify Portal — a commercial, managed Internal Developer Platform based on Backstage. Spotify Portal is designed as “Backstage in a Box”: teams get a fully functional IDP without having to worry about the underlying infrastructure or React development. The platform offers commercial plugins for service maturity scoring, incident management integration, and advanced analytics.

Spotify itself achieves 99% internal adoption with Backstage — external organizations average around 10% according to Spotify’s VP of Engineering, which underscores the potential for improvement through managed services like Spotify Portal.

Red Hat Developer Hub: Enterprise Backstage with Dynamic Plugins

Red Hat is taking its own path with the Red Hat Developer Hub (RHDH) : an enterprise-ready, opinionated Backstage distribution that runs on Red Hat OpenShift and other Kubernetes platforms (AKS, EKS, GKE). RHDH was the first Backstage distributor to support dynamic plugins — plugins can be added to a running instance without needing to recompile the entire Backstage project. This addresses one of the biggest pain points in day-to-day Backstage usage and is a decisive advantage for enterprise teams.

Red Hat has also donated five additional plugins to the Backstage project, including integrations for Azure Container Registry, JFrog Artifactory, Kiali, Nexus, and 3scale. Seamless integration with GitHub organizations for users, groups, and catalog discovery is also possible.

New Frontend System: Ready for Adoption

Backstage’s New Frontend System, which promises a departure from the previous React-heavy plugin development, has been “adoption-ready” since the end of 2025. It significantly simplifies plugin development and reduces the dependency on deep React knowledge — one of the most frequently cited hurdles for Backstage newcomers. The Backstage CLI has also been switched to Rspack as the bundler, noticeably reducing build times.

Adoption and Trends for Internal Developer Platforms

The “2025 State of Internal Developer Portals” report by Port.io shows: 53% of respondents use Backstage or a commercial IDP based on Backstage. Developer teams use an average of 7.4 different tools — 75% of developers lose between 6 and 15 hours of productivity per week as a result. Gartner predicts that 80% of large engineering organizations will have platform teams by the end of 2026.

The trend toward platform engineering and Internal Developer Platforms continues unabated. Backstage remains the central open-source framework, even as competition from managed services like Port, Cortex, and OpsLevel grows. Backstage’s strength lies in its flexibility and the active community ecosystem with over 230 plugins.

Conclusion

Backstage has evolved from an internal Spotify tool to the leading open-source standard for Internal Developer Platforms. The latest developments — the new Spotify Portal, Red Hat’s Developer Hub with dynamic plugins, the mature New Frontend System, and the consistent release cadence — show that the project continues to gain maturity and user-friendliness. For teams serious about platform engineering, Backstage remains the top choice in 2026, complemented by increasingly mature commercial ecosystems that lower the remaining hurdles in operations and adoption.

Sources

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