Case Study / 2024
Internal Developer Portal
Service catalog and runbook portal used daily by 200+ engineers to reduce ownership ambiguity and incident response time.
200+
Daily users
Engineering organization
10 min to 20 sec
Ownership lookup
Median incident lookup
140+
Services cataloged
Production services
81%
Runbook coverage
Tier 1 and 2 services
problem
Ownership Was Hidden in Chat History
Engineers often discovered service ownership by asking in chat during incidents. The portal turned ownership, dependencies, and runbooks into searchable operational metadata.
database-design
Document Model
Each service document owns nested owners, alert routes, dependencies, and runbooks. MongoDB matched the shape of the operational object and avoided migration churn for optional metadata.
observability
Operational Readiness
The portal highlighted services missing owners, SLOs, alert routes, or runbooks so platform quality could be improved incrementally.
