The use case: how Contentful deploys incident.io
Contentful moved incident response, on-call paging and service ownership data onto incident.io, replacing homegrown Slack scripts and a legacy PagerDuty setup. Responders also use its Investigations feature, connected to Datadog and the service Catalog, to diagnose incidents in Slack.
More reported results
Figures published in incident.io’s case study. They are not independently measured by usedby.
Now more than 100 engineers have led an incident, and 150 have responded to one.
In the legacy tool every new microservice had needed its own escalation policy, which could add up to half a day of work.
In the customer’s words
Investigations has been an absolute game changer. From catching people up when they join an incident, to finding the PR that triggered an issue, to drafting a status update. It lets you focus on the incident itself rather than the bureaucratic tasks on the side.Other AI tools used by Contentful
Other public relationships recorded on usedby.
Explore Contentful’s AI stackincident.io users in DevTools & Infrastructure
Companies in the same sector, with public evidence.
Giant SwarmConfirmed
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
- Aug 3, 2026
- Last checked
- Nov 5, 2026
Open source capture What the story claims, and what we checked
What we compared with the page.
- The publication dateChecked
Read from the page’s own metadata, never guessed.
- Contentful uses incident.ioChecked
Confirmed line.
- The result itselfNot checked
We quote it; we did not measure it.
Myself and a staff software engineer had been bashing our heads for at least two hours. Investigations ran for about five minutes and figured it out.



