5 Lessons learned from implementing developer portals at enterprises

Invited to BackstageCon in Chicago, Chris shares five hard-won lessons from implementing Backstage and developer portals inside large enterprises — what worked, what didn’t, and what he’d do differently.

Start from the catalogue

Every service earns its place in the portal by registering a small descriptor, so ownership and docs travel with the code:

apiVersion: backstage.io/v1alpha1
kind: Component
metadata:
name: payments-api
spec:
type: service
owner: payments-team