Skip to main content
Nexus is incident.io’s living model of your organization: how your systems are built, how your team operates, and how things break. It combines everything it can see with an understanding of how that fits together. It’s unique to your organization, included with the platform, and powers the products you use across it.

​
Explore your incidents

You don’t need Investigations to get value from Nexus. From your catalog and your past incidents alone, it builds a clustered map of your incident history: related incidents grouped into themes, so you can see your data in a way a list never shows you.
Exploring your incidents in Nexus is available on Pro and Enterprise plans.
The Nexus homepage showing incidents clustered into themes like cache eviction stampedes and auth token expiry failures, with a panel ranking themes by time spent

Nexus clusters your recent incidents into themes you can explore.

Use it to spot the failures that keep recurring, the themes eating the most time, and the responders who show up across related incidents.

​
What Nexus knows

Each source you connect gives Nexus another angle on your organization. Catalog and past incidents come from incident.io itself. Connecting the other sources, like telemetry and code, currently requires Investigations. Once a source is connected, everything draws on it: Investigations use it when an incident is live, and so does the agent whenever you ask it a question. With telemetry connected, you can ask the agent what your systems were doing and it’ll go and query them for you. Connect whatever you have; you don’t need everything to get value.

Catalog

Your services, teams, and who owns what.

Past incidents

Everything that’s happened before, and how it was fixed.

Change events

Deploys, feature flags, and config changes, correlated with incidents.

Documentation

Runbooks and reference docs from Confluence, Notion, GitHub, and GitLab.

Code repositories

Your pull requests and the code behind them, safely sandboxed.

Telemetry

Logs, metrics, traces, and dashboards from your observability tools.

Slack channels

Real-time context: deploys, config changes, and team discussion.
Sources are configured from the Nexus homepage in your dashboard.

​
FAQs

No. Nexus is the intelligence underneath the platform, not a separate purchase. Every product you use adds to what it knows, and it’s unique to your organization: your data never trains shared models. Connecting sources like code and telemetry does require Investigations, but your catalog and your past incidents feed Nexus without it.
Yes. Extensions let you connect your own MCP servers, and write skills that tell Investigations how to use them. To reach a private or self-hosted system, run a proxy in your network and attach the data source to it.