DevOps Dictionary

Service Catalog is a centralized, searchable list of the services a team or organization offers, describing what each service does, who owns it, what it depends on, and how to request, change, or get support for it. It solves the “tribal knowledge” problem by making service details explicit and consistent, so people can discover the right capability and engage the right team without guesswork. At a high level, it works by standardizing service metadata (for example, environments supported, reliability expectations, and escalation paths) and connecting that data to workflows such as provisioning, access approval, incident response, and lifecycle management.

With a Service Catalog, teams onboard faster, avoid duplicating systems, and route incidents and changes to the correct owners; without it, discovery becomes ad hoc, ownership is unclear, and operational risk increases as services sprawl. This gap exists because service delivery spans many teams and tools, and the catalog provides a shared source of truth that keeps those moving parts aligned.