Skip to main content
usedby
incident.io
DevTools & Infrastructure · 51–200 employees

What AI does incident.io use?

incident.io uses 11 AI tools, from Slack and Sentry to Fivetran and ElevenLabs. 3 are confirmed by a published story, quote or press release. 8 are declared by incident.io itself. Every tool links to the public page that names incident.io.

Checked Nov 22, 202617 public sources7 of 11 tool families
AI stack

The AI stack at incident.io

11 tools in 7 families. Open a tool to see its proof level and its source.

All tools

Every tool, with its source

Strongest proof first. Each line links to the page behind it and its capture date.

AI tools used at incident.io, with category, proof level, first public proof and source
ToolCategoryProofFirst public proofSource
CircleCIDevOps, SRE & incidentsDevOps, SRE & incidentsConfirmed≤ Apr 2025circleci.com
Common RoomProspecting data & signalsProspecting data & signalsConfirmed≤ Mar 2025commonroom.io
Recall.aiSpeech & voice APIsSpeech & voice APIsConfirmed≤ Sep 2024recall.ai
ElevenLabsVoice & audio generationVoice & audio generationDeclared≤ Nov 2026incident.io
FivetranData platforms & analyticsData platforms & analyticsDeclared≤ Nov 2026incident.io
HexData platforms & analyticsData platforms & analyticsDeclared≤ Nov 2026incident.io
MergeWorkflow automation & AI agentsWorkflow automation & AI agentsDeclared≤ Nov 2026incident.io
PylonHelp desksHelp desksDeclared≤ Feb 2025incident.io
SentryDevOps, SRE & incidentsDevOps, SRE & incidentsDeclared≤ Nov 2026incident.io
SlackWorkspaces & project managementWorkspaces & project managementDeclared≤ Nov 2026incident.io
TemporalAgent frameworks & AI gatewaysAgent frameworks & AI gatewaysDeclared≤ Nov 2026incident.io
Showing 11 of 11Showing 10 of 11

“First public proof” is the earliest public page we have dated: a mention (“on or before”), a job post or a start the source states. Our capture dates are not adoption dates.

Results

What incident.io’s teams say about their tools

Quotes and figures as the vendors and incident.io published them, each tied to its saved source page. usedby does not measure the result.

On Common Room
~0.8%
Account duplicate rate, down from ~3% across
When we started the exercise, about 3% of our accounts were duplicates. Today it’s about 0.8. That is material.
Khaled AlSalehRevOps Leader, incident.io
Case study, Published May 20, 2026 · Read how incident.io uses Common Room
On CircleCI
20 to 30
merges per day
CircleCI is so far out in front of other CI/CD platforms. We know we won’t have to plan for re-platforming. When you start out with CircleCI, you can skip talking about CI/CD platforms for years to come.
Isaac SeymourProduct Engineer at incident.io
Case study, Published Nov 12, 2026 · Read how incident.io uses CircleCI
On Common Room
10%
more meetings booked as of August 2025 than in the entirety of 2024
Common Room was a breakthrough. Now I have a tool that feels like it was built for prospecting—something I can put in the hands of every BDR and every AE.
Tom WentworthCMO, incident.io
Case study, Published Sep 2, 2025 · Read how incident.io uses Common Room
Timeline

How the stack grew

Each tool sits on the quarter of the first public page we found. It means “on or before”, never an adoption date.

Peers

How incident.io compares to its industry

396 DevTools & Infrastructure companies on usedby, public proof only. A company can use tools that no public page names.

AI tools per company

396 DevTools & Infrastructure companies on usedby, by number of AI tools
  1. 223 companies with 1 tool
  2. 44 companies with 2 tools
  3. 24 companies with 3 tools
  4. 20 companies with 4 tools
  5. 13 companies with 5 tools
  6. 10 companies with 6 tools
  7. 10 companies with 7 tools
  8. 52 companies with 8 tools or more

Median: 1 tool. 363 of its 395 peers use fewer.

These counts cover public proof only. A company can use tools that no public page names.

What DevTools & Infrastructure companies with up to 200 employees use
Most used tools among the other DevTools & Infrastructure companies with up to 200 employees on usedby
ToolCompanies
PostHog11
Pylon (incident.io too)11
Common Room (incident.io too)10
CodeRabbit9
Sentry (incident.io too)9
Datadog9

121 other DevTools & Infrastructure companies with up to 200 employees on usedby. Every proof level counts, job posts included. Companies with no stored size are left out.

FAQ

Questions about AI at incident.io

What AI tools does incident.io use?

incident.io uses 11 AI tools (3 confirmed, 8 declared): CircleCI, Common Room, Recall.ai, ElevenLabs, Fivetran, Hex, Merge, Pylon, Sentry, Slack, and Temporal.

Does incident.io use Slack or Sentry?

Yes, both. Slack: declared, incident.io lists it as a sub-processor on its own legal page. Sentry: declared, incident.io lists it as a sub-processor on its own legal page.

Which AI tools are confirmed at incident.io?

3: CircleCI, Common Room, and Recall.ai. Each one has a published case study, a named quote or a press release.

Which AI tool do DevTools & Infrastructure companies use most?

Resend is the most used AI tool among the 396 DevTools & Infrastructure companies on usedby: 34 of them use it. See who uses Resend.

How does incident.io compare to other DevTools & Infrastructure companies?

incident.io uses 11 AI tools. The median among the 396 DevTools & Infrastructure companies on usedby is 1, and 363 of its 395 peers use fewer tools. These counts cover public proof only. Its closest stacks are Linear (7 shared tools), Figma (5 shared tools), and ClickUp (5 shared tools).

What do confirmed, declared, observed and signal mean?

Confirmed: a case study, a named quote or a press release. Observed: the vendor shows incident.io on its own pages, for example a logo wall. Signal: a job post shows incident.io’s employees use the tool, the weakest proof. Every level counts, and each line shows its level. Declared: incident.io told usedby itself that it uses the tool, from an address on its own domain, and no public page backs the line; or incident.io lists the tool as a sub-processor on its own legal page, a data-processing relationship rather than a described use.

How current is this page?

The most recent check was on November 22, 2026. 11 of the 11 lines have been checked so far, from 17 public sources.

How does usedby know which AI tools incident.io uses?

Each tool is linked to a public page that names incident.io: a vendor's customer page, a published case study, a press release or a job post. We save most pages with a dated capture and check them again on each run. A tool leaves the list only after three checks in a row that no longer find incident.io, and at least 14 days after it was last seen. A tool with a published case study or quote is never removed automatically. A tool incident.io declared itself has no page to open: its line is marked Declared, and a vendor dropping its logo never removes it.

Sources

Where this data comes from

Two proof levels

Confirmed · 3Case study, named quote or press release.
Declared · 8incident.io told usedby itself that it uses the tool, or lists it as a sub-processor on its own legal page.

Source types

  • incident.io sub-processor lists8 lines
  • Customer stories2 lines
  • Vendor pages1 line
How we check →

Cite this page

UsedBy.ai (2026). What AI does incident.io use? 11 tools. Retrieved from https://www.usedby.ai/companies/incident-io, latest check November 22, 2026.