Definition of the internal developer portal
Which software services already exist, who is answerable for them, how do you create a new one? The internal developer portal (portail développeur interne in French) is the web interface that brings these answers together for an organisation’s development teams. It gathers a catalogue of software components, project templates, technical documentation and access to the capabilities of the internal platform.
The expression belongs to the vocabulary of projects and tool vendors. The “Platforms” white paper from the CNCF TAG App Delivery (tag-app-delivery.cncf.io) does not use it. It speaks of “Web portals” and makes them one of the families of capabilities of a platform, responsible for publishing documentation, service catalogues and project templates.
Two tool documentations, consulted on 12 November 2026, speak of a developer portal. The Backstage documentation, a CNCF project, describes “an open source framework for building developer portals”. The documentation of Port, a vendor’s product, sees in the internal developer portal “a central interface” where developers find services, consult engineering information and launch self-service actions.
Portal, platform, ITSM catalogue, API portal: not to be confused
The internal developer platform, defined in our entry on platform engineering, is the set of capabilities offered on a self-service basis. The portal is one interface to it: the CNCF white paper also cites APIs, the command line and development environments. The two expressions share the acronym IDP.
In IT service management (ITSM), common usage calls service catalogue the list of what an IT department offers its users. The catalogue of a developer portal lists software components and the teams answerable for them.
The API portal, presented in the entry on API management, is aimed at those who consume APIs, third parties included.
The golden path is a recommended route, which the portal makes it possible to find.
Catalogue, templates, documentation, self-service
The Backstage documentation details three core functions, which plugins complement.
- The software catalogue tracks the ownership and metadata of the organisation’s software: services, websites, libraries, data pipelines. It is fed by YAML files stored with the code. Its stated aim: that every piece of software and its owner can be found. The need grows with the number of components, as in a microservices architecture.
- Templates are used to create new projects that comply with the organisation’s practices.
- Technical documentation is managed like code (“docs like code”).
To these is added self-service, which Port calls “self-service actions”. The CNCF white paper gives an example: requesting a database through a form, then receiving its address and credentials.
At a carrier: finding the owner of a service
Suppose a carrier whose teams maintain services for parcel tracking, delivery round planning and invoicing. A developer needs to call the delivery rounds service. She searches for it in the portal catalogue, reads the name of the owning team there and opens the interface documentation.
Later, this team is split, and nobody corrects the service’s metadata file. The catalogue then displays a team that no longer exists.
What a portal does not solve
The portal is an interface. If no automated capability responds behind a form, the request is handled by hand.
The catalogue is only as good as the metadata kept by the teams.
Nor is a portal a prerequisite. According to the CNCF white paper, a very simple platform can come down to a wiki page pointing to procedures. Finally, a portal is itself software to be run and maintained.
Our page on DevOps and platform engineering specifies at what point in a platform approach a portal finds its place.