Skip to main content
The catalog is where incident.io holds the structure of your organization: your services, the teams that own them, and how everything depends on everything else. It’s one of the richest things Nexus knows about you, and it works across the whole platform, not just investigations. For Nexus, the catalog is the map. When an investigation traces a problem to a service, the catalog is what tells it who owns that service, what it depends on, and what depends on it, so a finding lands with the right team and its blast radius is clear.

Using the catalog

Set up the catalog and understand how it’s structured.

Importing data

Populate the catalog from Backstage, Cortex, OpsLevel, and other sources.

Teams

Model your teams and connect them to the services they own.

What data to add

Decide what belongs in your catalog and how to shape it.