Declare incidents from errors
Connect
SPIRITT
incident.ioincident.io
Run incidents end to end
SPIRITT works your incident.io setup from first alert to last follow-up. It declares and updates incidents, pages the right people, keeps the catalog current and closes the loop afterward.
What you can do with incident.io.
Faster declaration
Create incidents with severity, roles and custom fields, and page responders through escalation paths.
Follow-through that finishes
Track updates, actions and follow-ups so every postmortem commitment gets closed.
A catalog kept in sync
Keep services, teams and owners in the catalog synced from the systems that define them.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Start a SPIRITT workspace for the incident response work you want handled.
02
Connect incident.io
Connect incident.io so SPIRITT can work with your incidents, catalog, schedules and escalation paths.
03
Delegate an outcome
Describe the process you want to run better. SPIRITT sets it up, runs it and reports the results.
Hand over a mission.
Choose a mission. Make it yours.
Put incident.io to work.
Run every incident to the finish
Questions
incident.io, with SPIRITT.
01What can SPIRITT do with incident.io?+
SPIRITT creates and edits incidents, pages escalation paths, manages the catalog, custom fields, severities, statuses and roles, updates schedules, escalation paths and workflows, and configures alert sources and routes.
02Can it declare incidents automatically?+
Yes. SPIRITT watches your monitoring on a schedule and creates incidents with severity, roles and custom fields, then pages the right escalation path.
03Can it keep the catalog current?+
Yes. It creates catalog types and bulk-syncs entries from your source of truth, such as repository ownership files, so routing uses current owners.
04Can it help with postmortems?+
Yes. SPIRITT assembles timelines from updates, timestamps, alerts and roles, and tracks follow-ups and actions until they are complete.
05Can it manage on-call?+
Yes. It reads schedule entries, rebalances rotations, updates escalation paths and sends test escalations to confirm paging works.
06How do I get started with incident.io?+
Open a SPIRITT workspace, connect incident.io and hand over one outcome, such as follow-up tracking or catalog sync. SPIRITT runs it and reports progress.