Incident management and on-call · Rankedincident.io
incident.io is an incident management and on-call platform that describes itself as an AI software reliability platform · incident.io ↗
Leads at mid-market. Ranked 2 of 64 for enterprise buyers.
The standing depends on who is buying. Every model is asked the same questions for each company size.
Ranked first, contested: PagerDuty has 18%.
Ranked first. Next is PagerDuty at 25%. 11 of 14 models made it the first choice when asked directly.
PagerDuty is first at 53%.
Why models recommend it
“incident.io: A Slack-native platform that eliminates the "coordination tax" through automated channel creation, timeline capture, and AI-powered post-mortems.”Llama 4 Maverick · Negative question · first choice
“For a small team with limited budget and Slack as a core communication tool: Incident.io (free tier) or Rootly (free tier).”GLM 4.7 FlashX · Budget-constrained question · first choice
“For SRE & Slack-Native Engineering Teams: Look at modern workflow platforms like incident.io, Rootly, or All Quiet.”Gemini 3.5 Flash · Negative question · first choice
“Modern / ChatOps-First | Incident.io, Rootly, FireHydrant | Best developer experience. Built natively around Slack/Teams.”Gemini 3.5 Flash · Scale-constrained question · first choice
What gives them pause
“G2 reviews for incident.io mention setup complexity and limited status-page flexibility in some cases.”GPT-5.4 mini · Negative question · warning
“Slack-centered coordination can be insufficient when Slack or identity systems are unavailable.”Perplexity Sonar · Negative question · warning
Also on the shortlist
The products named in the same answers as incident.io, over the 180 answers that named it, and how often each was the first choice instead.
| Product | Named together | Picked instead | |
|---|---|---|---|
| 168 | 51 | Compare → | |
| 97 | 3 | Compare → | |
| 94 | 0 | View → | |
| 79 | 0 | View → | |
| 62 | 1 | Compare → | |
| 61 | 3 | View → | |
| 48 | 4 | Compare → | |
| 42 | 1 | View → | |
| 42 | 0 | View → | |
| 34 | 2 | Compare → |
What the models named instead of incident.io →
A side-by-side page exists where both products are among a category's top eight.
At a glance
Stated on incident.io's own site, not checked by Gane.
- For
- teams where downtime isn't an option
- Price stated
- Free; $19 per user / month; $25 per user / month; Let's talk
- Starting price
- Free
- Free plan or trial
- Get started for free
- Integrations
- 2 · 4 (its own pages disagree)
- Certifications
- HIPAA, SOC 2 Type II
- Customers named
- Zendesk, Fin, Linear, Airbnb, Square, Netflix, Etsy, Skyscanner
How this is measured
Fourteen AI models from 12 labs are asked the same buying questions six ways, for three company sizes. Standings refresh every edition.
Gane sells AI visibility software. No company can pay to change a result.
Read the method →Sources returned with these answers
Fourteen of the fourteen models returned a source list in this edition: five return the pages they cited and nine the search results they consulted. These counts come from 170 of the 180 answers that named incident.io and are not a share of its labels.
Domains cited
390 of the 519 domain citations in answers naming incident.io came from a third party's page.
Pages cited
Pages are listed as the models cited them.
By model
| Model | First choice | Alternative | Mention | Warning | Labels |
|---|---|---|---|---|---|
| Claude Haiku 4.5 | 1 | 2 | 0 | 0 | 3 |
| GPT-5.4 mini | 1 | 1 | 0 | 1 | 3 |
| Gemini 3.5 Flash | 3 | 2 | 0 | 0 | 5 |
| Perplexity Sonar | 2 | 2 | 0 | 1 | 5 |
| Grok 4.20 | 3 | 1 | 2 | 0 | 6 |
| Mistral Small | 3 | 0 | 2 | 0 | 5 |
| DeepSeek V4 Flash | 2 | 4 | 0 | 0 | 6 |
| Llama 4 Maverick | 2 | 1 | 2 | 0 | 5 |
| Qwen 3.7 Flash | 4 | 2 | 0 | 0 | 6 |
| Kimi K2 | 3 | 2 | 1 | 0 | 6 |
| GLM 4.7 FlashX | 3 | 1 | 0 | 0 | 4 |
| MiniMax M2.5 | 2 | 2 | 0 | 0 | 4 |
| GPT-6 Luna | 2 | 2 | 0 | 0 | 4 |
| Muse Glimmer 30B | 4 | 0 | 0 | 0 | 4 |
What it publishes
| Kind | Pages | Last 90 days | 2025-10 to 2026-09 | Latest | Categories named |
|---|---|---|---|---|---|
| Blog | 540 | 33 | 2026-09-22 | Incidents, ITSM | |
| Comparison | 69 | 5 | 2026-09-01 | Incidents, ITSM | |
| Case study | 33 | 1 | 2026-08-03 | ||
| Report or ebook | 26 | 1 | 2026-07-09 | ||
| Glossary or explainer | 14 | 3 | 2026-09-21 | ITSM | |
| News or press | 11 | 0 | 2023-06-07 | ||
| Template or tool | 7 | 1 | 2026-07-09 | ||
| Podcast or video | 6 | 0 | 2023-01-12 |
Most recent
- 2026-09-22Almost excited to get paged blog
- 2026-09-21Ai incident triage blog
- 2026-09-21What is ai incident triage glossary or explainer
- 2026-09-15Ai powered incident detection guide blog
- 2026-09-15Best ai incident detection tools for startups blog
- 2026-09-15How to evaluate ai incident detection vendors blog
How it is countedHide how it is counted
Every page incident.io exposes, subdomains included. Kind is read from the address and title. The last 90 days, the latest date and the twelve months count pages by when they were published, from the site's feeds, a date in the address, or the page's own publication date, read from up to a hundred of its most recently changed pages; a page that says only when it last changed is counted in its kind but not in when, so the recent counts are a floor, and a kind none of whose pages gives a publication date reads undated. Read September 29, 2026.