Every service with an owner, which is the whole point.
Compass keeps a catalog of the services an engineering organization runs, with an owner, a health signal, and the dependencies between them recorded against each. Our work is cataloguing services, recording ownership, and connecting that ownership to identity and change control.
Compass catalogs the services in your estate and records who owns each one. Ownership is the same problem we solve at the identity layer, arriving one level up.
What it is
Compass keeps a catalog of the services an engineering organization runs, with an owner, a health signal, and the dependencies between them recorded against each.
It is for organizations large enough that nobody can name every service from memory, which is a lower threshold than most teams expect.
What it does
A catalog with owners
Every component has a named owner, which is the field that turns a list into something actionable.
Dependencies made explicit
What depends on what, recorded rather than reconstructed during an incident.
Where it fits
L2, platform and migration, answering an L1 question. An unowned service and an unowned identity are the same failure at different altitudes. Whoever owns a service is also the person who should be answering for what its credentials can reach.
What we do with it
Ownership as a working model
Naming an owner is easy. Keeping the list true as teams reorganize is the part that needs a process.
Connecting ownership to access
A service owner and the owner of that service's credentials should be the same person, and usually are not.
Wiring it into incident and change
A catalog only earns its place if it is consulted during an incident, which means the service desk has to reference it.
Where it earns its place
An engineering group after reorganization
Team boundaries moved, service ownership did not, and nobody noticed until an incident.
An estate preparing for automation
Automation acting on a service nobody owns is the risk. The catalog is how you find those first.
Proof
World Class Software Development Finalist, 2024-2025
Atlassian Partner Awards, 2024-2025
Questions we get
Is this a CMDB?
How do we stop it going stale?
Licensing
Compass is licensed per user and is often adopted by one team before anyone checks what the estate-wide count would be. That reconciliation sits with the rest of the estate in licensing and renewals.