The use case: how Giant Swarm deploys incident.io
Giant Swarm uses incident.io to standardise its incident response through automations and workflows, so on-call engineers, including new joiners, follow a consistent process. It also uses the tool for post-mortem generation, custom-field insights and follow-up capture, and to keep Customer Success informed during incidents.
More reported results
Figures published in incident.io’s case study. They are not independently measured by usedby.
before we probably captured 40% vs 90% now that we’re using incident.io
incident.io users in DevTools & Infrastructure
Companies in the same sector, with public evidence.
ContentfulConfirmed
TurbopufferConfirmed
WorkOSConfirmed
HashiCorpObserved
HoneycombObserved
LinearObservedGo straight to the source
Based on incident.io’s published case study. We check the public evidence; the results are reported by the vendor.
incident.io- Source published
- Feb 1, 2021
- Last checked
- Nov 22, 2026
Open source capture What the story claims, and what we checked
What we compared with the page.
- The figure: 3 hoursChecked
Printed word for word on the page, near the name of Giant Swarm.
- The passage quoted aboveChecked
Copied word for word from the page, near the name of Giant Swarm.
- The publication dateChecked
Read from the page’s own metadata, never guessed.
- Giant Swarm uses incident.ioChecked
Confirmed line.
- The result itselfNot checked
We quote it; we did not measure it.
We’re now able to encode the process itself which really helps new on-callers. We are approaching it in terms of making our on-callers' lives easier, and reducing that stress, allowing us to make changes to our process without having to retrain everyone.
