Service Catalog Management and Design

Calendar February 22, 2026
Platform-Engineering
Intermediate, Advanced
Catalog-Design, Backstage-Administration, Scorecard-Configuration, Ownership-Modeling
Service-Catalog, Backstage, Catalog-Info, Scorecards, Tech-Debt, Ownership, Software-Catalog, Maturity-Model
Backstage, Github, Gitlab, Kubernetes, Cortex, Opslevel, Datadog

Why a Service Catalog Exists#

A service catalog answers: “What do we have, who owns it, and what state is it in?” Without one, this information lives in tribal knowledge and stale wiki pages. When an incident hits at 3 AM, the on-call engineer needs to know who owns the failing service, what it depends on, and where to find the runbook. The catalog provides this in seconds.

The catalog is also the foundation for other platform capabilities. Golden paths register outputs in it. Scorecards evaluate catalog entities. Self-service workflows provision resources linked to catalog entries.

Platform Engineering Maturity Model

Calendar February 22, 2026
Platform-Engineering
Intermediate, Advanced
Maturity-Assessment, Platform-Strategy, Capability-Mapping, Organizational-Design
Platform-Maturity, Maturity-Model, Platform-Engineering, Developer-Platform, Organizational-Assessment, Platform-Team
Backstage, Crossplane, Terraform, Argocd, Port

Why a Maturity Model#

Platform engineering investments fail when organizations skip levels. A team that cannot maintain shared Terraform modules reliably has no business building a self-service portal. The maturity model provides an honest assessment of where you are and what must be true before advancing.

This is not a five-year roadmap. Some organizations reach Level 2 and stay there — it serves their needs. The model helps you identify what level you need, what level you are at, and what is blocking progress.