# incident.io vs PagerDuty: who uses which

On usedby, 52 companies use incident.io and 18 use PagerDuty. 1 company uses both, including Honeycomb. Counts include every proof level, job-post signals included; each company keeps its proof level on each side. Latest check 2026-11-22: 70 of 70 public lines checked.

## Side by side

|  | [incident.io](https://www.usedby.ai/tools/incident-io.md) | [PagerDuty](https://www.usedby.ai/tools/pagerduty.md) |
|---|---|---|
| Public customers | 52 | 18 |
| Confirmed | 34 | 8 |
| Observed | 14 | 2 |
| Signals (job posts) | 0 | 2 |
| Top industries of customers (every proof level) | DevTools & Infrastructure (9), Fintech & Payments (7), Artificial Intelligence (4) | DevTools & Infrastructure (4), Telecommunications (3), Artificial Intelligence (2) |
| Category | DevOps, SRE & incidents | DevOps, SRE & incidents |
| Security | SOC 2 Type II ([trust.incident.io](https://trust.incident.io/), checked 2026-11-13) | — |
| Data processing terms | A data processing agreement is available. ([trust.incident.io](https://trust.incident.io/), checked 2026-11-13) | — |
| Free trial | Free trial or free plan available. ([incident.io](https://incident.io/pricing), checked 2026-11-13) | — |
| Integrations | Slack, Microsoft Teams, Jira, GitHub, GitLab, Linear, Datadog, PagerDuty, Opsgenie, Sentry, Zoom, Okta ([incident.io](https://incident.io/integrations), checked 2026-11-13) | — |
| Pricing | Basic: Free Forever; Team: $19 Per user / month; Pro: $25 Per user / month; Enterprise: contact sales ([incident.io](https://incident.io/pricing), checked 2026-11-13) | Starter: $2,800 / year; Essential: $12,000 / year; Plus: $48,000 / year ([pagerduty.com](https://www.pagerduty.com/pricing/), checked 2026-11-16) |

## Companies that use both

Every proof level counts; the proof level of each side is shown, strongest proofs first. The first public proof is not an adoption date.

| Company | Proof, incident.io | Proof, PagerDuty | First public proof, incident.io | First public proof, PagerDuty |
|---|---|---|---|---|
| [Honeycomb](https://www.usedby.ai/companies/honeycomb.md) | Declared by the company | Declared by the company | On or before October 2024 | On or before November 2026 |

## Published results

Reviewed stories only; usedby did not measure the figures.

- incident.io: [Trainline](https://www.usedby.ai/case-studies/trainline-incident-io.md): **3.5 hours**: “3.5 hours saved per P1/P2 post-mortem” (published 2024-06-25)
- incident.io: [Giant Swarm](https://www.usedby.ai/case-studies/giant-swarm-incident-io.md): **3 hours**: “I’d estimate that we save at least 3 hours onboarding each new oncaller” (published 2021-02-01)
- PagerDuty: [SAP](https://www.usedby.ai/case-studies/sap-pagerduty.md): **30%**: “reducing initial response and communications times to critical incidents by 30%” (published 2023-09-16)
- PagerDuty: [DraftKings](https://www.usedby.ai/case-studies/draftkings-pagerduty.md): **under 30 minutes**: “MTTR is now under 30 minutes” (published 2023-06-15)

## Evidence for your decision: incident.io

Source observations. Check the required plan and conditions before choosing.

### Documented tasks

No reviewed task examples are available yet.


### Choice criteria

- Free trial or free plan: Yes — Sourced observation
  Plan: Unknown · Checked: 2026-11-13T13:05:17.479Z
  > Basic Free Forever Everything you need to get started with incident management
  [Source](<https://incident.io/pricing>) · Vendor page
- Integration: Jira — Sourced observation
  Plan: Unknown · Checked: 2026-11-13T13:05:17.479Z
  > Export and automatically sync your incident actions with tickets in Jira.
  [Source](<https://incident.io/integrations>) · Vendor page
- Pricing: Free — Sourced observation
  Plan: Basic · Checked: 2026-11-13T13:05:17.479Z
  > Basic Free Forever Everything you need to get started with incident management
  [Source](<https://incident.io/pricing>) · Vendor page
  Scope: Forever
- Integration: Slack — Sourced observation
  Plan: Basic · Checked: 2026-10-23T23:41:58.968383+00:00
  > Slack or Microsoft Teams native incident response
  [Source](<https://incident.io/pricing>) · Documented · Not tested
  Product: incident.io
  Setup and limits: Named plan, contract entitlement, connector scopes, permissions, volume limits and regional eligibility remain unknown.; Documented only; not\_tested. No authenticated vendor operation executed.
  Conditions: Basic plan only; native incident response scope.


## Capabilities for agents: incident.io

Documentation and operational tests are separate. A test covers only the stated task and operation.

No reviewed capability profile yet.

---
Source: https://www.usedby.ai/compare/incident-io-vs-pagerduty · How we check: https://www.usedby.ai/methodology
