DEV CommunityMonday · June 8, 2026FREE

Backstage vs Port vs Cortex: When to Stop Self-Hosting

backstagedeveloper-portalself-hostingplatform-engineeringadoption

The DEV Community article "Backstage vs Port vs Cortex: When to Stop Self-Hosting" examines the paradox of Backstage's market position. Backstage, an open-source framework originating from Spotify and now a CNCF project, has achieved significant market dominance in the Internal Developer Portal (IDP) space, reportedly holding about 89% of the market share. It is deployed across more than 3,400 organizations and serves over two million developers globally, excluding Spotify's internal usage. This widespread adoption by organizations indicates its success as a foundational framework for building developer portals. However, the article points out a critical challenge: the average internal adoption rate for self-hosted Backstage instances is approximately 10%. This low figure suggests that while many organizations choose to implement Backstage, the resulting developer portals often fail to become a daily tool for engineers. The discrepancy between high framework adoption and low end-user engagement leads to the emerging sentiment in platform engineering circles that "DIY is dead," particularly concerning developer portals. The article posits that this situation is not a contradiction but a reflection of how platform teams allocate their resources, indicating that the effort required for self-hosting may not translate into effective developer utility.

// why it matters

Developers are often presented with internal tools that, despite organizational investment, fail to integrate into their daily workflows.

Sources

Primary · DEV Community
▸ Read original at dev.to

Like this? Get the next digest.

Backstage vs Port vs Cortex: When to Stop Self-Hosting — aigest.dev