Most Internal Developer Portals Fail. Here Is Why.

Backstage runs inside 3,400+ organizations and reaches 2 million developers. It's a CNCF incubating project with near-monopoly market share for internal developer portals. And yet, enterprise after enterprise reports the same outcome: 12-18 months of implementation, single-digit adoption, and developers who still open Slack instead of the portal. The problem isn't Backstage. The problem is confusing a portal for a platform.

80% Market Share, 9% Adoption

Backstage, Spotify's open-source developer portal, holds an estimated 80-90% of the IDP market. The adoption curve looks like a success story — until you measure what happens after deployment.

Organizations that spent 12-18 months implementing Backstage repeatedly report adoption rates stalling around 9%. The portal exists, but developers aren't using it. Thoughtworks and other consultancies see this pattern across enterprises: a polished catalog that nobody opens.

Many teams mistake the portal for the entire platform, but Backstage is not your platform. Portals are the front end of the platform, a UI that allows developers to discover and access the platform's underlying capabilities.

7.4 Tools, $1M in Lost Productivity

Development teams use 7.4 tools on average, forcing constant context switching. 75% of developers lose 6-15 hours weekly to tool sprawl. For a team of 50 engineers, that's nearly $1 million in lost productivity annually.

A portal addresses discoverability — knowing what tools exist. It doesn't solve the underlying fragmentation. If developers still switch between 7 tools, a central catalog listing them all doesn't reduce cognitive load.

What Successful Platforms Provide

Commercial IDPs Are Winning on Time-to-Value

Gartner's 2025 Market Guide signals a clear shift: the market now favors IDPs that deliver immediate value. Cortex, Port, and Humanitec are gaining ground by shipping opinionated solutions rather than frameworks to customize.

Backstage's strength — extreme flexibility — is also its weakness. Organizations must build plugins, define entity schemas, and create service catalogs from scratch. That's months of investment before any developer sees value. Commercial alternatives ship a working portal in weeks.

Five Principles That Separate Shipping Teams from Stalled Ones

Platform Engineering Success Factors

• The platform exists to make developers faster, not to look cool
• Every feature must reduce cognitive load or it gets deleted
• If a human approves it in Slack, automate it
• Paved roads are mandatory; off-roading is opt-in only
• Success is measured by how little developers think about infrastructure

The industry is converging on a "vending machine" model for infrastructure. Developers select from curated options that are standardized and optimized for the enterprise. The platform team maintains these options; developers consume them without understanding the implementation details.

85% Portal Adoption by 2028 — But "Initiative" Doesn't Mean Success

Gartner predicts that by 2028, 85% of organizations with platform engineering teams will have internal developer portals — up from 60% in 2025. The same forecast warns that 80% of enterprises will have some platform engineering initiative by 2026.

"Initiative" doesn't mean success. The organizations that will thrive are those treating the platform as a product — with dedicated teams, user research, and continuous improvement — not as an infrastructure project with a launch date and no iteration budget.

Start With Three Pain Points, Not a Portal

Working with government agencies where developer experience is often an afterthought, platform engineering is genuinely transformative — when done right. The failure mode is treating it as an infrastructure project rather than a product initiative.

Don't begin with Backstage. Begin by identifying the three things that most slow your developers down. Solve those problems — even if the solution is a script and a Confluence page. Once you understand what developers actually need, then evaluate whether a portal adds value.