Service Catalog

The Service Catalog is the workspace’s inventory of what actually runs: services, their owners, their lifecycle and how they connect.

What a catalog entry holds

• Identity - name, kind (service, library, …), lifecycle (experimental → production) and tier.
• Ownership - a product user or a Git developer; an entry with no owner is itself a finding.
• Source binding - the repository/project the service is built from.
• Dependencies - service-to-service links, drawn as an interactive dependency map.
• Deployments - deployment events (for example from Argo CD), which also feed the DORA metrics in Engineering Analytics.
• API specs - an OpenAPI document can be attached and is parsed for display.

Where it pays off

• New joiners get one page per service instead of tribal knowledge.
• The dependency map answers “what breaks if this goes down” before an incident asks it.
• The Administration area lists every catalogued service across all workspaces - the only place that view exists.