Solutions
Solutions
The same catalog serves three kinds of user. Here is what each gets from it.
For platform and ops teams
Keep one accurate record of what runs, who owns it and where.
- Teams, services, agents and cloud accounts in one catalog with relational links
- Catalog auditor findings for missing or inconsistent metadata
- Access rules per row instead of one all-or-nothing admin role
For service owners
Edit your own entries without asking an admin.
- Rows you own are editable by you; your owner group can view or edit as you set
- Dependencies, accounts and labels on the Service page
- Connector data from Coastguard and DNS beside the catalog entry
For automation and other systems
Read and write the catalog from scripts, CI and fleet systems.
- Read or write-scope API keys
- Signed webhooks for created, updated and deleted rows
- Idempotent agent registration and an OpenAPI document to generate clients from