Gartner's Market Guide for Internal Developer Portals, in its March 2025 edition, projects that 85 percent of organizations with platform engineering teams will provide internal developer portals by 2028, up from 60 percent in 2025. The portal, once a niche platform-engineering tool, is becoming the standard front door of software delivery, and the guide's most valuable content is its warning about the market's most famous free option.
The catalog that became the portal
The internal developer portal began as a catalog: a living inventory of every service, its owner, its dependencies, its health, in an estate too large for any human to hold in memory.
The portal grew from the catalog in every direction: self-service access to tools and environments, scaffolding templates for new components, scorecards that benchmark quality and security, and integrations into the delivery pipeline. Gartner's definition makes the promise explicit: tools that enable self-service discovery, automation, and access to reusable components, tools, platform services, and knowledge assets.
The software catalog is the portal's spine, and everything else hangs from it.
The March 2025 Market Guide for Internal Developer Portals, and its 85 percent forecast
The current edition published March 31, 2025, authored by Manjunath Bhat and Cary Pillers, following the September 2023 edition.
The adoption data explains the forecast's confidence. Internal developer portals were the most frequently piloted technology in Gartner's Technology Adoption Roadmaps across 2022 through 2024, with 22 percent of respondents piloting and 36 percent already deployed.
The confirmed representative vendors across the editions include Port, Mia-Platform with its Console, Cortex, and OpsVerse, with the Peer Insights market adding the wider field: Roadie, the managed Backstage option, Atlassian Compass, OpsLevel, Configure8, Humanitec, and Red Hat Developer Hub.
The portal is a long-term investment wearing a quick-win demo, and the guide's advice follows: dedicate a platform team, appoint a platform owner, and build the roadmap around the team's most pressing problems, continuously.
The Backstage disillusionment
The guide's sharpest content is its caution about Backstage, the open-source portal the market adopted as its default answer: Gartner calls it the Kubernetes of IDPs, a major market driver that organizations misconstrue as a ready-to-use portal requiring no additional work.
The misconception is expensive. Supporting Backstage in production requires real software engineering depth, TypeScript, Node.js, React, and the infrastructure stack around them, and the organizations that adopted the free option expecting a finished product discovered they had adopted a development project instead. The guide notes the disillusionment and abandoned projects that follow.
The commercial providers' pitch follows directly: simpler deployment, easier maintenance, sensible and secure defaults. Backstage is the Kubernetes of IDPs: powerful, free, and not the product.
The fourth pillar
The 2025 guide adds a capability the category did not have before: platform orchestration, the catalog acting as a central hub of knowledge that participates in CI pipelines through APIs.
The fourth pillar is the market's direction. A catalog that only describes the estate is a wiki. A catalog that drives the pipeline, that provisions, that triggers, that enforces, is infrastructure. The orchestration pillar turns the portal from a map into an instrument, and the guide treats it as a core capability rather than an add-on.
The fourth pillar turns the catalog into an API, and the vendors that shipped it are the ones the 2028 forecast will reward.
The AppSec case nobody pitches first
The guide names a use case the vendors under-sell: application security. The portal that knows every service's owner, tracks its component metadata, and integrates with the security tools is the fastest mechanism for consistent patching.
The mechanism is the portal's quietest return on investment. When a vulnerability lands, the organization with the portal knows who owns the affected service, what depends on it, and how to push the mitigation, in hours instead of weeks. The security team's adoption of the portal is often the purchase's second buyer, arriving after the platform team signed.
Security patch speed is the portal's quietest return on investment, and the buyer should price it as part of the case.
What the guide cannot install for you
A Market Guide names representative vendors and does not rank them, and its honest limit is the adoption work itself: the portal's value depends on the catalog's data quality, the integrations' depth, and the organization's willingness to maintain both, none of which any vendor can supply.
The other limit is the AI layer's dependency, which the guide states: only portals with logic persisting throughout the system can fully benefit from AI capabilities, the chatbots, the retrieval-augmented knowledge discovery. The AI that navigates the portal inherits the portal's data model, and a shallow portal produces a shallow assistant.
Four questions for the platform team
Build Backstage or buy the commercial option? The guide's own caution is the decision's starting point. Price the engineering team's years against the license, honestly.
What is the catalog's data quality plan? The portal's spine is the inventory. Ask how the catalog stays current, which sources feed it, and what happens when it drifts, because the drift is where portals quietly fail.
Is the orchestration pillar real? The fourth pillar is the market's direction. Ask which pipeline actions the portal actually drives, in production, not which it displays.
Who owns the portal after launch? The guide's advice is a named platform owner. Ask for the operating model, the roadmap owner, and the funding, because an unowned portal is a catalog that rots.
Analyst Source
Gartner Market Guide
Category definition, representative vendor list, and market guidance in this article draw on Gartner's Market Guide for Internal Developer Portals, current edition published March 31, 2025, authored by Manjunath Bhat and Cary Pillers, following the September 2023 edition. The guide defines portals around self-service discovery, automation, and access to reusable components, projects that 85 percent of organizations with platform engineering teams will provide portals by 2028, names platform orchestration as a core capability, and cautions that Backstage is misconceived as a ready-to-use portal. Port, Mia-Platform, Cortex, and OpsVerse are among the representative vendors. Market Guides do not rank vendors or name Leaders.
Source research
Gartner does not endorse any vendor, product or service depicted in its research publications, and does not advise technology users to select only those vendors with the highest ratings or other designation. Gartner research publications consist of the opinions of Gartner's research organization and should not be construed as statements of fact. Gartner disclaims all warranties, expressed or implied, with respect to this research, including any warranties of merchantability or fitness for a particular purpose.
A closely related read is Robotic Process Automation. UiPath and Automation Anywhere have both led Gartner's RPA quadrant for seven straight years, even as the vendors' own marketing quietly renames the category agentic process automation, robots included as one tool among many.