# incident.io — On-Call & Incident Management

incident.io by Pineapple Technology Ltd. holds a panel rating of 3/5 from 6 AI judges (category median 3/5), as of 2026-11-06. Provenance: UK / wider Europe; sovereignty: 1 of 6 dimensions proven.

- Vendor: Pineapple Technology Ltd. (https://incident.io)
- Category: [On-Call & Incident Management](https://whats-best.ai/software/incident-management.md)
- Provenance (editorial classification): UK / wider Europe
- Canonical page: https://whats-best.ai/software/incident-management/incident-io
- Alternatives: https://whats-best.ai/software/incident-management/incident-io/alternatives ([markdown](https://whats-best.ai/software/incident-management/incident-io/alternatives.md))
- Data as of: 2026-11-21 · evaluated 2026-11-06 · oldest source captured 2026-11-06

**AI-generated.** Every score, rationale and verdict here is written by a panel of AI judges from public evidence — an analysis, not a hands-on test. Every fact quotes the vendor page it was read from. No score can be bought. How scores are made: https://whats-best.ai/methodology

## At a glance

- Vendor: Pineapple Technology Ltd.
- Headquarters: Not stated on the vendor’s pages as of 6 Nov 2026
- Data hosting: Not stated on the vendor’s pages as of 6 Nov 2026
- Free plan: Yes, per the vendor’s own page [S8]

## The panel's verdict

incident.io, an on-call and incident management product from Pineapple Technology Ltd., earns top marks for integration and admin and for on-call scheduling, where scores cluster at 8-9: a REST API with an OpenAPI 3.0 spec, client libraries in seven languages, a CLI and Terraform, plus rotations from single-team through shadow to follow-the-sun, cover requests, overrides and an on-call pay report. Incident response scores 7-8 on Slack and Teams declaration, status pages and AI-drafted post-mortems. The weak points are sovereignty at 0-1 and pricing transparency at a flat 5 from scored judges: the captured pages name Pineapple Technology Ltd. under the laws of England and Wales, seat not stated, and we found no public information on data residency, subprocessors or a published data processing agreement, while Enterprise and three add-ons carry no public prices. Reliability and compliance splits 6-7 — one judge calls the compliance claims a solid audit file, others flag unstated hosting regions, SLA credits and data retention. A sixth judge's scores are 0 throughout; the ranges cover the five judges with nonzero scores, whose persona-weighted totals run 6.5-7.4.

**Speaks for it:**
- Integration and admin scores cluster at 8-9, on a REST API with an OpenAPI 3.0 spec, client libraries in seven languages, a CLI and Terraform support.
- On-call scheduling scores cluster at 8-9, covering single-team rotations, shadow schedules, follow-the-sun, cover requests, overrides and holiday feeds.
- An on-call pay report, pay calculator and pay configuration API support payroll, with fairness tracking and time-off imports from HR systems.
- Incident response scores 7-8, with declaration from Slack or Microsoft Teams, severity levels SEV-1 to SEV-4, status pages and AI-drafted post-mortems documented.
- Mid-tier prices are public: Basic is Free Forever, on-call standalone is $20 per user / month and Pro is $25 per user / month.

**Held against it:**
- Sovereignty scores sit at 0-1, with no public information on data residency, subprocessors or a published data processing agreement, and the entity's seat not stated.
- Pricing transparency scores 5, with Enterprise as a custom proposal, three add-ons carrying no public prices and different status-page figures across captured pages.
- Reliability and compliance scores 6-7, with hosting regions, multi-region failover, SLA credits and data retention not publicly stated.
- Alerting and routing scores 6-7, with no public information on delivery receipts, a per-alert notification log or the countries where SMS and voice are delivered.
- We found no public information on the model provider or data handling behind the AI features, or on named MTTA and MTTR analytics.

**Best for:**
- You run incident response from Slack or Microsoft Teams and want follow-ups synced into Jira, Linear or Azure DevOps.
- You operate follow-the-sun or multi-team on-call across countries and need a pay report, fairness tracking and HR time-off imports for payroll.
- You manage on-call configuration as code and want Terraform plus an API with published rate limits and a no-breaking-changes policy.
- You are migrating from PagerDuty, Opsgenie or Atlassian Statuspage and want documented migration tools.

**Avoid if:**
- Your procurement requires a published data processing agreement and a stated hosting location before sign-off; the captured pages name Pineapple Technology Ltd. under the laws of England and Wales and we found no public information on either.
- You need per-alert delivery evidence — delivery receipts or a notification log — or to know which countries SMS and voice reach.
- You must compute a full annual cost before committing — Enterprise is a custom proposal, and we found no public information on SMS and voice volumes, VAT treatment or add-on prices.
- You need multi-region failover detail or DORA and NIS2 documentation for a regulated audit file.

## Scores by judge and criterion

Scores out of 5, each judge scoring independently against the published rubric (v1). "n/r" = not rated: the vendor publishes no price, or the judge found no public information on that criterion.

| Criterion | The SRE Lead | The IT Operations Manager | The MSP NOC Lead | The ICT Risk Officer | The Engineering Manager | The Skeptic |
| --- | --- | --- | --- | --- | --- | --- |
| On-call schedules, rotations & escalation | 0/5 | 4.5/5 | 4/5 | 4/5 | 4/5 | 4/5 |
| Alert delivery, routing & noise reduction | 0/5 | 3.5/5 | 3.5/5 | 3/5 | 3.5/5 | 3.5/5 |
| Incident response, status pages & post-incident review | 0/5 | 4/5 | 3.5/5 | 4/5 | 4/5 | 4/5 |
| Integrations, API & administration | 0/5 | 4.5/5 | 4/5 | 4.5/5 | 4.5/5 | 4.5/5 |
| Platform reliability, security & compliance | 0/5 | 3/5 | 3.5/5 | 3/5 | 3/5 | 3/5 |
| European sovereignty | 0/5 | n/r | n/r | n/r | 0.5/5 | n/r |
| Pricing transparency | 0/5 | 2.5/5 | 2.5/5 | 2.5/5 | 2.5/5 | 2.5/5 |
| **Weighted verdict** | **0/5** | **3.5/5** | **3.5/5** | **3.5/5** | **3.5/5** | **3.5/5** |

### The judges

- **The SRE Lead** (v1.0): Leads site reliability at a Berlin SaaS company with sixty engineers in eight product teams, Prometheus and Grafana for metrics, Sentry for errors and everything discussed in Slack. Wants an incident declared with one command, a channel with roles and a timeline, the status page updated from the same place, alerts grouped so one database outage does not page five teams, schedules kept in Terraform, and a postmortem that writes its first draft.
- **The IT Operations Manager** (v1.0): Runs IT operations for a packaging manufacturer with 900 staff and three plants running around the clock, with Checkmk and PRTG watching servers, networks and the production line. Five administrators share a weekly standby. Wants a Checkmk alert to become a phone call that the right person acknowledges by keypad, the deputy called after ten minutes, no pages during planned maintenance, and an alerting service that still works when the plant's own network is the thing that is down.
- **The MSP NOC Lead** (v1.0): Leads the network operations centre of a managed service provider in Nuremberg that looks after sixty mid-sized customers, with Zabbix, Microsoft Sentinel and Autotask in the stack. Wants alerts routed by customer and contract hours, tickets opened and closed in the PSA without anyone copying text, a separate on-call rota for the night shift and for each key account, one customer never seeing another's data, and a monthly report per customer on response times.
- **The ICT Risk Officer** (v1.0): ICT risk officer at a Frankfurt payments company supervised by BaFin, where DORA requires major ICT incidents to be classified and reported within hours. The incident tool is itself an ICT third-party service in the register. Reads the subprocessor list, asks where incident timelines and the AI summaries of the response channel are processed, wants an SLA, audit logs and a DORA addendum in the contract, and needs the timeline to hold up as evidence for the regulator.
- **The Engineering Manager** (v1.0): Engineering manager at a logistics software company in Hamburg with developers in Germany, Portugal and Poland, where the works council has agreed an on-call policy with paid standby hours and rest periods after a night call. Wants a follow-the-sun rota across three time zones, swaps from the phone, on-call hours exported to payroll each month, a warning when the same person is paged three nights running, and a price per responder that does not charge for the managers who only read along.
- **The Skeptic** (v1.0): Has seen "never miss an alert" from a pager that was down in the same cloud region as the outage it should have reported, "unlimited notifications" that meant twenty SMS a month outside the US, and an "AI incident assistant" that sent the whole response channel to a model nobody named. Asks which carriers deliver the calls, what the SLA pays, whether schedules and history can be exported when leaving — and what the plan costs once the stakeholders need seats.

## European sovereignty — proven facts

Built only from facts on the vendor's own pages; a dimension we could not prove is left open, never scored as zero. Headline: 1 of 6 dimensions proven.

| Dimension | Finding | Points | Source |
|---|---|---|---|
| Legal entity | Not determined | — | — |
| Hosting location | Not determined | — | — |
| Hosting options | Not determined | — | — |
| Open source | Not determined | — | — |
| Data processing agreement | Published, self-serve | 1/1 | [S11] |
| Transfer impact assessment | Not determined | — | — |

## Key facts

Each fact is the vendor's own statement, cited to the source page it was read from ([S*n*] → Sources).

**Compliance**
- Authentication: SSO+SAML · SSO · SSO+SAML+SCIM [S8]
- Bug bounty: yes [S9]
- Encryption: AES-256 · SHA-256 [S9]
- Penetration testing: annual · yes [S9]
- Security page: yes [S1]
- SOC 2: yes [S8]
- SOC 2 GDPR: yes [S9]
- Vulnerability scanning: OWASP vulnerabilities · weekly [S9]

**Integrations**
- Alerts paging count: 38 [S5]
- Announcement copy: Tools connected into one system spanning first alert to final follow-up [S5]
- API base URL: https://api.incident.io/ [S7]
- API key auth: Authorization: Bearer <YOUR_API_KEY> · Bearer · Settings → API keys [S7]
- API key permissions: account-level · team-scoped · both [S7]
- API key survives deactivation: yes [S7]
- API terraform: yes [S2]
- API webhooks: yes [S8]
- Aws: AWS · Incidents from Cloudwatch Alarms; export audit logs to S3 [S5]
- Azure devops: Azure DevOps · Export incidents as issues, kept up to date [S5]
- Basic limit: 2 · unlimited [S8]
- Calendar: Google Calendar · Outlook Calendar · Link calendar events such as incident debriefs to incidents [S5]
- Catalog sync: Cortex · OpsLevel · Backstage · ServiceNow [S3]
- Cli: inc · yes [S7]
- Communication: Slack · Microsoft Teams · Zoom · Google Meet [S3]
- Compatibility policy: new path (e.g. /v1 → /v2) run in parallel · yes · 3 [S7]
- Custom: REST API · webhooks · HTTP endpoints · Terraform [S3]
- Datadog: Datadog · Create incidents from monitors; stream audit logs to Datadog SIEM [S5]
- Endpoint surface: Actions · Alerts · Escalations · Incidents · On-call Schedules · Catalog · Custom Fields · Status Pages · Workflows · Webhooks · Audit logs · Users · Teams [S7]
- Error format: JSON with type, status, request_id, errors [S7]
- Everything else count: 13 [S5]
- Github: GitHub · Connect pull requests, export follow-ups as GitHub Issues with sync [S5]
- Gitlab: GitLab · Connect pull requests, export follow-ups as GitLab Issues with sync [S5]
- Google meet: Google Meet · Automatically start a Google Meet for each incident [S5]
- HR: BambooHR · HiBob · PeopleHR · Personio · Rippling · CharlieHR [S3]
- HR systems count: 8 [S5]
- HR time off: BambooHR · CharlieHR · HiBob · PeopleHR · Personio · Workday · Import time-off calendars to keep on-call schedules up-to-date [S5]
- Hris: HRIS integrations available (unlimited) [S8]
- Incident creation limits: 10 · 300 [S7]
- Issue tracking count: 8 [S5]
- Jira: Jira · Export and sync incident actions with tickets [S5]
- Linear: Linear · Export and sync incident actions with tickets [S5]
- Mcp: yes [S8]
- Microsoft teams: Microsoft Teams · Automatically start a Teams meeting for each incident [S5]
- Monitoring: Datadog · New Relic · Grafana · AWS CloudWatch · Prometheus · Sentry · Splunk · AppDynamics · Sumo Logic · uptime.com [S3]
- Okta: Okta · SAML SSO and SCIM provisioning [S5]
- Openapi spec: OpenAPI 3.0 · yes [S7]
- Opsgenie: Opsgenie · Alerting and escalation [S5]
- Pagerduty: PagerDuty · Alerting and escalation [S5]
- Pagination: cursor · 25 [S7]
- Post mortem export: Confluence · Google Docs · Notion · SharePoint · Export post-mortems for archival or collaboration [S5]
- Rate limit default: 1200 requests/minute per API key [S7]
- Rate limit endpoint specific: 25 · 300/min · 60 · 60/min · 10 · 60/min · yes [S7]
- Rate limit exceeded response: 429 · yes [S7]
- Rate limit headers: X-RateLimit-Limit · X-RateLimit-Remaining · X-RateLimit-Used · X-RateLimit-Reset [S7]
- Rippling: Rippling · SCIM and/or SAML user and team management [S5]
- Salesforce: Salesforce · Bring in customer information [S5]
- Sdks: Go · TypeScript · Python · Rust · Ruby · PHP · .NET [S7]
- Service catalog count: 4 [S5]
- Service catalog sync: Backstage · Cortex · OpsLevel · Sync service catalogs into Workflows, Insights and Triggers [S5]
- Servicenow: ServiceNow · Two-way incident sync [S5]
- Slack: Slack · Manage incidents at scale, without leaving Slack [S5]
- Splunk: Splunk · Splunk On-call alerting; stream audit logs to Splunk SIEM [S5]
- SSO: Okta · Azure AD · Google Workspace [S3]
- Statuspage: Statuspage · Automatic customer status updates [S5]
- Support contact: support@incident.io [S7]
- Ticketing: Jira · Linear · Asana · GitHub Issues · Azure DevOps · Shortcut · Zendesk [S3]
- Vanta: Vanta · Sync incident follow-ups for SOC2/ISO27001 compliance [S5]
- Video documents count: 8 [S5]
- Zapier: Zapier · Create incidents from thousands of Zapier triggers [S5]
- Zendesk: Zendesk · Link support tickets to incidents [S5]
- Zoom: Zoom · Automatically set up video conferencing for incidents [S5]

**Legal**
- Company name: Pineapple Technology Ltd. [S2]
- Copyright entity: Pineapple Technology Ltd. · 2026 [S1]
- Entity: 2026 · Pineapple Technology Ltd [S4]
- Entity: 2026 · Pineapple Technology Ltd [S3]
- Entity: Pineapple Technology Ltd. [S9]
- Entity: 2026 · Pineapple Technology Ltd [S5]
- Entity: Pineapple Technology Ltd. [S8]
- Entity: 2026 · Pineapple Technology Ltd [S11]

**Pricing**
- Basic price: Basic · 0 [S8]
- Enterprise price: yes [S8]
- Included features: 24/7 · no · 50 [S2]
- Inclusion: no · yes [S4]
- Integrations included: no [S3]
- Jsm comparison: 18 · 48 [S2]
- Oncall price: 20 [S2]
- Oncall price: yes · 20 [S8]
- Pagerduty comparison: 21 · 41 [S2]
- Pro oncall addon: 20 [S8]
- Pro price: 25 [S8]
- Purchasing options: Pro · Enterprise · yes [S2]
- Team oncall addon: 10 [S8]
- Teams plan availability: yes [S3]

**Product**
- Action tracking: yes [S3]
- Addon capabilities: Root cause analysis, autonomous agent, Nexus data sources available as add-ons (mid-tier plans) [S8]
- Agent learning: yes [S1]
- Agent reasoning: yes [S1]
- AI alert intelligence: yes [S2]
- AI drafted post mortems: yes [S3]
- AI incident summaries: yes [S3]
- AI investigations: Investigations: AI SRE that drafts PRs, suggests next steps, surfaces similar incidents, drafts comms, pulls dashboards [S3]
- AI noise reduction: 80 [S2]
- AI suggestions: yes [S8]
- Alert deduplication: Automatic deduplication, incident grouping, false-positive suppression [S2]
- Alert routing: Alert routing by team, service, or other criteria [S2]
- Alert sources: Alerting includes alert sources, live call routing, BYO Twilio number, heartbeat monitoring, and alert deduplication [S6]
- Alert sources count: 40 · yes [S2]
- API: yes [S3]
- Atlassian migration: Atlassian Statuspage · component structure · subscriber lists · custom domains [S4]
- Automated alert naming: yes [S2]
- Basic features: Slack/Teams native incident response, single team on-call, status page, essential automation [S8]
- Catalog: yes [S3]
- Component subscriptions: yes [S4]
- Cover requests: yes [S2]
- Current status: no · fully operational [S10]
- Custom domains: yes [S4]
- Custom fields: yes [S3]
- Custom fields components: multi-select custom fields [S4]
- Custom rbac: Custom RBAC [S8]
- Demo available: yes [S1]
- Documentation available: yes [S1]
- Easy overrides: yes [S2]
- Endpoint security: within a month · as soon as they're available [S9]
- Enterprise features: Dedicated CSM, advanced access control, multiple environments, enterprise security & compliance [S8]
- Escalation policies: yes [S3]
- Fairness tracking: yes [S2]
- Free tier: yes [S4]
- Free tier available: yes [S1]
- History calendar: monthly calendar of incident history · yes [S10]
- Holiday feeds: yes [S2]
- Holidays in schedules: yes [S2]
- Incident response features: Incident response includes creating, managing, and private incidents [S6]
- Integrations count: 100 [S3]
- Integrations group: Integrations · 100% · 25 [S10]
- Intercom integration: Intercom [S4]
- Investigations: Investigations provide agentic root cause analysis for every incident [S6]
- Investigations capability: Agentic root cause analysis delivering structured hypothesis in seconds [S1]
- Investigations group: Investigations · 100% [S10]
- Migration time: Most migrations complete in under a week [S2]
- Migration tools: Import schedules/escalation paths from existing paging tools, dual-run supported [S2]
- Migration tools: PagerDuty · Opsgenie [S3]
- Mobile app: yes [S2]
- Mttr reduction claim: 30 · 50 [S2]
- Multiple pages: yes [S4]
- Nexus: Nexus includes past incidents, Slack channels, change events, documentation, catalog, code, telemetry, and extensions [S6]
- On call features: On-call includes schedules, escalation paths, readiness insights, on-call pay report, and pay configuration API [S6]
- Oncall capability: On-call: automatic alert routing, AI noise filtering, escalation [S1]
- Oncall features: Mobile app · Alerting · Scheduling · Trends [S1]
- Oncall group: On-call · 100% · 6 [S10]
- Oncall standalone: yes [S8]
- Opsgenie sunset: 2027-04 [S2]
- Page types: public · private · internal [S4]
- Pay calculator: yes [S2]
- Platform description: Software reliability platform for investigating, responding and preventing incidents, powered by AI [S1]
- Platforms: Platform products: On-call (alerting, flexible schedules, reliable paging) and Response (automation, context, tools in one place) [S6]
- Post incident features: Post-incident features include post-mortems, follow-ups, task due dates & reminders, timeline generation, debriefs, and shoutouts [S6]
- Postmortem AI: AI Native [S8]
- Private incidents: yes [S3]

**Support**
- Channels: Help center, community, email support, dedicated Slack channel (designated CSM), live phone support [S8]
- Enterprise migration: Enterprise customers get dedicated migration assistance [S2]
- Onboarding engineering: yes [S3]

33 more facts on the canonical page: https://whats-best.ai/software/incident-management/incident-io

## Questions

### Is incident.io European?

Yes, though not from the EU. whats-best.ai classifies incident.io as UK / wider Europe.

### Where does incident.io store data?

Not stated on the vendor’s pages as of 6 Nov 2026.

### Does incident.io have a free plan?

Yes. incident.io has a free plan, per [the vendor’s page captured 6 Nov 2026](https://whats-best.ai/evidence/19765).

### What are the best alternatives to incident.io?

As of 18 Nov 2026, the panel rates [ilert (4/5)](https://whats-best.ai/software/incident-management/ilert), [All Quiet (3.5/5)](https://whats-best.ai/software/incident-management/all-quiet) and [OneUptime (3.5/5)](https://whats-best.ai/software/incident-management/oneuptime) highest among the other 16 On-Call & Incident Management products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is [ilert](https://whats-best.ai/software/incident-management/ilert) (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: [how scores are made](https://whats-best.ai/methodology#ordering). The full list, with European products first: [incident.io alternatives](https://whats-best.ai/software/incident-management/incident-io/alternatives).

## Head-to-head

- [incident.io vs Rootly](https://whats-best.ai/compare/incident-io-vs-rootly.md)

## What this page leaves out

- 13 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material.
- 1 compliance fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material.
- 1 integrations fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material.
- 1 pricing fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material.
- We read 11 of the 25 pages we planned to read for this product; the others could not be captured yet. Everything on this page rests on the pages we read.
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement.

## Sources

- [S1] Vendor homepage: https://incident.io/ (checked 2026-11-06)
- [S2] Features page (on-call): https://incident.io/on-call (checked 2026-11-06)
- [S3] Features page (incident response): https://incident.io/incident-response-slack (checked 2026-11-06)
- [S4] Features page (status pages): https://incident.io/status-pages (checked 2026-11-06)
- [S5] Integrations page: https://incident.io/integrations (checked 2026-11-06)
- [S6] Documentation: https://docs.incident.io/ (checked 2026-11-06)
- [S7] API documentation: https://docs.incident.io/api-reference/introduction (checked 2026-11-06)
- [S8] Pricing page: https://incident.io/pricing (checked 2026-11-06)
- [S9] Security / trust page: https://incident.io/security (checked 2026-11-06)
- [S10] Public status page: https://status.incident.io/ (checked 2026-11-06)
- [S11] Service level agreement: https://incident.io/legal/sla (checked 2026-11-06)

---

Cite as: whats-best.ai, "incident.io — On-Call & Incident Management", AI panel analysis, as of 2026-11-21. https://whats-best.ai/software/incident-management/incident-io

Corrections: https://whats-best.ai/correct/1622?target=page
