The practical guide to internal developer portals

Why is the internal developer portal a foundational technology and what promise does it hold?

How internal developer portals drive developer self-sufficiency and reduce cognitive load.

Now that we’ve established what an internal developer portal is, the more practical question is: what do you use it for?

Far from being just a “flat” repository for static metadata (e.g., ownership, logs), the software catalog is at the center of the developer portal.

Self-service actions make developers more productive (and happy), through autonomy with guardrails and golden paths.

Scorecards provide clear standards of quality and maturity to drive alignment across engineering teams – and the toolkit to drive a variety of initiatives.

A robust portal can – and should – be able to trigger workflows around alerting, resource management, remediation, provisioning, and more.

You’re leaving value on the table if you overlook a portal’s reporting capabilities. Done right, reporting can do quite a lot.

The more data in your developer portal the better. Learn more about how to think about extensibility and integrations.

Blueprints are the foundational building blocks of the internal developer portal. Learn why they matter.

The portal needs to integrate into developers’ existing workflows, start with the right features and then develop organically.