Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 1 of 6 dimensions proven

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by Pineapple Technology Ltd. · incident.io

Compare with Rootly → Report an error on this page Is this your product? →

Link to this page

incident.io: AI-assisted analysis on whats-best.ai incident.io: AI-assisted analysis on whats-best.ai (dark)

Add ?theme=dark to the image address for dark backgrounds. The badge shows the category and the month of the latest evaluation, and EU-Made where that is the product’s provenance. It never shows a score.

incident.io 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 source, captured 6 Nov 2026
Panel verdict
The AI panel rates incident.io 3/5, the mean of 6 judges. 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. how scores are made
As of
Vendor pages captured 6 Nov 2026; evaluated by the panel 6 Nov 2026. all sources

incident.io alternatives, European ones first →

Read this page as one judge. Each weighs the same scores by what they care about.

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.

Report an error

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.

Report an error

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.

Report an error

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.

Report an error

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.

Report an error

The scores

Panel median The median of the judges’ scores per criterion. Each label opens its reasoning below.

On-call schedules, rotations & escalation

panel disagrees Show reasoning
How this is scored

Who is on call and what happens when nobody answers: schedules with daily, weekly and custom rotations, layers and follow-the-sun hand-offs across time zones, overrides, swaps and holiday cover, escalation policies with timeouts, repeat and fallback levels, round-robin and team escalation, calendar export and sync, reminders before a shift, on-call reports and hours exported for on-call pay and working-time rules, and a mobile app that shows the shift and lets a responder hand it over.

0 — No schedules or escalation of any kind; alerts go to a fixed list of people.

3 — A simple weekly rotation and one escalation step; overrides, layers, time zones and on-call reports are basic or not described.

5 — Schedules with several rotation types and layers, overrides and swaps from the app, escalation policies with timeouts and several levels, time-zone handling, calendar export, shift reminders, and a report of who was on call when.

8 — Follow-the-sun and multi-team schedules, round-robin and conditional escalation, coverage gaps flagged before they happen, schedules and policies managed as code or by API, and on-call hours exported per person for pay and working-time rules, all documented.

10 — Scheduling a large organisation runs on: every feature above with fairness and fatigue reports, rest-period rules enforced or warned, schedules imported from HR or workforce tools, and every scheduling limit documented per plan.

Report an error

The SRE Lead

Follow-the-sun, shadow rotations, multi-team schedules, cover requests, overrides and holiday calendars are all documented, and schedules are managed as code through Terraform and an API whose documented surface explicitly covers on-call schedules and escalations. The on-call pay report, pay calculator, pay configuration API and built-in fairness tracking give me exactly the per-person hours and load distribution I need for working-time and fatigue conversations, and time-off imports from Personio, Workday, BambooHR and others keep schedules current from HR. We found no public information on rest-period rules being enforced or warned, or per-plan scheduling limits, which is the gap to the top level. 2 5 6 7 8

Report an error

The IT Operations Manager

Schedules run from single-team rotations to shadow schedules and follow-the-sun, with overrides, cover requests and holiday feeds, and multi-team on-call from the Team plan upward; escalations automatically page additional responders when SLAs are breached. Schedules and escalation paths are managed through the API and Terraform, and on-call hours feed a pay report, a pay calculator and a pay configuration API, with fairness tracking and HRIS time-off imports to keep the roster current. We found no public information on round-robin distribution or fatigue and rest-period rules. 2 3 5 6 7 8

Report an error

The MSP NOC Lead

Follow-the-sun, shadow rotations, holiday calendars, overrides and cover requests are documented, escalation automatically pages more responders when SLAs are breached, and the on-call pay report, fairness tracking and pay-configuration API are exactly what I need for night-shift hours across sixty customers. Schedules and escalations are manageable by API and Terraform, and time-off imports from HR systems like Personio or Workday keep the rota honest. We found no public information on round-robin escalation, coverage-gap warnings or rest-period rules, so it stops a step short of the top. 2 3 5 6 7 8

Report an error

The ICT Risk Officer

Follow-the-sun, shadow schedules, holiday calendars, cover requests and overrides are documented, multi-team on-call appears on the higher plans, and the on-call pay report, pay calculator and pay configuration API plus HR time-off imports cover on-call pay and fairness tracking shows load distribution. We found no public information on round-robin escalation, warnings for coverage gaps before they happen, or fatigue and rest-period reporting, which keeps this a level below the top. 2 5 6 8

Report an error

The Engineering Manager

The on-call product documents the shape my three-country rota needs: rotations from simple single-team through shadow schedules to follow-the-sun, cover requests, easy overrides, holiday feeds and multi-team on-call on the higher plans, with schedules and escalation policies managed by API and Terraform. Best for our works council arrangement, there is an on-call pay report with a pay configuration API for payroll, plus built-in fairness tracking of load distribution and time-off calendars imported from Personio, Workday and other HR systems. What we found no public information on is a rest-period or fatigue warning when the same person is paged night after night, or shift reminders and calendar export of the rota itself. 2 6 7 5 8 3

Report an error

The Skeptic

Follow-the-sun, shadow rotations, multi-team on-call, holiday feeds, cover requests and overrides are documented, schedules and escalation paths are managed by API and Terraform, and an on-call pay report with a pay configuration API and pay calculator exports hours for payroll, with fairness tracking on top. I found no public information on round-robin or conditional escalation, rest-period rules, or per-plan scheduling limits. 2 5 6 7 8

Report an error

Alert delivery, routing & noise reduction

panel disagrees Show reasoning
How this is scored

Whether the alert reaches a human and only the right one: notification by push, SMS, voice call, email and chat, critical alerts that override do-not-disturb on iOS and Android, personal notification rules with retries and fallbacks, acknowledgement by app, SMS reply or keypad, delivery receipts, live call routing for a hotline, routing rules by service, severity, payload and time, deduplication, grouping and correlation of related alerts, suppression and maintenance windows, heartbeats for silent failures, and inbound email and webhook endpoints.

0 — Sends no alerts to people; a dashboard or log viewer only.

3 — Push and email notifications with acknowledgement; SMS, voice, routing rules and noise reduction are basic or not described.

5 — Push, SMS, voice and email with personal notification rules and retries, critical alerts on mobile, acknowledgement from the app or by phone, routing by service and severity, deduplication, and maintenance windows.

8 — Alert grouping or correlation with its logic documented, routing on payload fields and time conditions, delivery receipts and a notification log per alert, live call routing, heartbeat monitoring, suppression rules, and the countries and channels where SMS and voice are delivered stated.

10 — Delivery that is evidenced, not promised: redundant SMS and voice carriers named with automatic failover, delivery statistics published, AI or rule-based noise reduction with measurable results, and every notification limit per plan documented.

Report an error

The SRE Lead

Routing by team and service, automatic deduplication, grouping of related incidents and false-positive suppression with a stated noise cut of up to 80 percent cover my main fear — one database outage paging five teams — and live call routing, WhatsApp escalations, voicemail, IVR phone trees, heartbeat monitoring and a bring-your-own Twilio number are documented alongside more than forty alert sources plus custom HTTP intake. However, we found no public information on delivery receipts, a per-alert notification log, critical alerts overriding do-not-disturb, personal notification rules with retries and fallbacks, routing on payload fields and time conditions, or the countries and channels where SMS and voice are delivered, so the delivery plumbing is thinner than the grouping story. 1 2 6 8

Report an error

The IT Operations Manager

Routing by team and service, automatic deduplication, incident grouping and false-positive suppression are documented, with a claimed AI noise cut of up to 80 percent, heartbeat monitoring, live call routing across one or five numbers with voicemail and IVR phone trees, WhatsApp escalations and a bring-your-own Twilio number. Forty-plus alert sources plus a custom HTTP endpoint and Zapier would carry our Checkmk and PRTG alerts, though neither monitor is among the named sources. We found no public information on delivery receipts or a notification log per alert, the countries where SMS and voice are delivered, personal notification rules and retries, acknowledgement by keypad, or maintenance windows to silence planned work. 2 3 5 6 8

Report an error

The MSP NOC Lead

Routing by team, service and other criteria, automatic deduplication, incident grouping and false-positive suppression are all documented, and a claimed noise cut of up to 80% is a number I can hold them to. Live call routing with phone trees and voicemail, WhatsApp escalation, a bring-your-own Twilio number and heartbeat monitoring cover the delivery side across forty-plus alert sources including a custom HTTP source. We found no public information on delivery receipts, a per-alert notification log, or which countries SMS and voice are delivered in. 2 6 8

Report an error

The ICT Risk Officer

Routing by team and service, automatic deduplication, incident grouping, false-positive suppression, heartbeat monitoring, and live call routing with voicemail, phone trees, WhatsApp escalations and a bring-your-own Twilio number are documented, with a claim that AI cuts alert noise by up to 80 percent. We found no public information on personal notification rules with retries, acknowledgement methods, delivery receipts or a per-alert delivery log, and the countries where SMS and voice are delivered are not stated — for a pager I want that delivery evidence, not just a reliability claim. 2 6 8

Report an error

The Engineering Manager

Routing and noise reduction are well documented: alerts route by team, service or other criteria, related alerts are deduplicated and grouped, false positives are suppressed, AI is claimed to cut alert noise by up to 80 percent, and live call routing with voicemail, IVR phone trees, WhatsApp escalations, a bring-your-own Twilio number and heartbeat monitoring are all named. What we found no public information on is the responder's personal delivery path — personal notification rules with retries and fallbacks, acknowledgement by app or keypad, delivery receipts per alert — and the countries and channels where SMS and voice are delivered. 6 2 8 3

Report an error

The Skeptic

Deduplication, incident grouping, false-positive suppression with a claimed noise cut of up to 80 percent, heartbeat monitoring, live call routing with voicemail and phone trees, WhatsApp escalations and bring-your-own Twilio are documented, plus routing by team and service. What I did not find: delivery receipts or a notification log, routing on payload fields or time conditions, the countries where SMS and voice are delivered, named carriers with failover, or per-plan notification limits; the 99.99 percent alert delivery reliability is a claim, not published delivery statistics. 1 2 6 8

Report an error

Incident response, status pages & post-incident review

panel disagrees Show reasoning
How this is scored

What happens once the alert is a real incident: declaring an incident from Slack, Microsoft Teams or the app, a dedicated channel and video bridge, incident roles and commander, severities and incident types, runbooks, tasks and automated workflows, stakeholder updates, public and internal status pages with subscribers, a timeline, post-incident reviews and postmortem templates with follow-up actions, analytics such as MTTA and MTTR, and AI features that summarise, suggest causes or draft the review.

0 — No incident record of any kind beyond the alert itself.

3 — An incident list with status and notes; channels, roles, status pages and post-incident reviews are basic or not described.

5 — Incidents declared from chat or the app with severities, a Slack or Teams channel created, incident roles, a timeline, a public status page, stakeholder notifications, postmortem templates, and MTTA and MTTR reports.

8 — Workflows and runbooks that automate the response, incident types with their own process, internal and public status pages with components and subscribers, follow-up actions tracked into Jira or Linear, service catalogue and dependencies, and AI summaries with their data handling described.

10 — A response process a regulated enterprise runs on: every feature above with major-incident and regulatory reporting templates, cross-team analytics and learning reviews, AI features documented with model provider, data handling and an opt-out, and every limit per plan stated.

Report an error

The SRE Lead

This is close to what I would run: a /incident command in Slack or Teams declares the incident, roles like Incident Lead, Communications Lead and Technical Lead are pre-defined, timelines are generated automatically, war rooms auto-start on Google Meet or Teams, and the status page is prompted from the same workflow with templates, unlimited subscribers, public, internal and private pages, component subscriptions and custom domains. Follow-ups sync into Jira and Linear with changes tracked, the service catalogue syncs from Backstage, Cortex, OpsLevel or ServiceNow, simulation mode lets me drill teams, and AI drafts the complete post-mortem including timeline, contributing factors and follow-ups. We found no public information on runbooks as a distinct artefact, on the data handling behind the AI summaries, or on MTTA and MTTR analytics being named as such, which is what separates this from the top level. 1 3 4 5 6

Report an error

The IT Operations Manager

Incidents are declared from Slack with /incident or from Microsoft Teams, carry severities SEV-1 through SEV-4 with configurable incident types, predefined roles, workflow automation, timeline generation, private incidents and a simulation mode for training. Public, internal and customer status pages have components and subscribers, follow-ups export and sync to Jira, Linear or Azure DevOps, and AI drafts incident summaries and complete post-mortems. We found no public information on how the AI features handle their data, and MTTA and MTTR appear as reduction claims rather than documented analytics. 1 3 4 5 6 8

Report an error

The MSP NOC Lead

Declaration from Slack with SEV-1 to SEV-4 severities, incident types with their own process, named roles, timelines, workflows and simulation mode are documented, follow-ups sync into Jira and Linear, and public, private and internal status pages support per-component subscriptions, custom domains and automated updates. AI-drafted post-mortems and incident summaries exist, and the import tools from PagerDuty or Opsgenie matter to a shop like mine. We found no public information on explicit MTTA and MTTR reporting per customer or on how the AI features handle data — "advanced insights and custom dashboards" is the only analytics description we found. 3 4 5 6 8

Report an error

The ICT Risk Officer

Declaration from Slack and Teams, incident types with severities, defined commander roles, workflows, a generated timeline, public, internal and private status pages with component-level subscribers, follow-ups exported and synced to Jira and Linear, plus AI summaries and AI-drafted post-mortems are all documented. For the regulator's file, though, we found no public information on the AI model provider or data handling behind those summaries, and no major-incident or regulatory reporting templates; resolution-time gains appear only as a vendor claim. 1 3 4 6 8

Report an error

The Engineering Manager

Incidents are declared from Slack or Microsoft Teams with severity levels SEV-1 to SEV-4, incident types with their own process, pre-defined roles for lead and communications, automated workflows, AI-transcribed calls and AI-drafted post-mortems with a generated timeline and tracked follow-ups. Status pages come in public, internal and customer flavours with component subscriptions over email, Slack and RSS, follow-up actions export and sync into Jira and Linear, and a service catalogue syncs from Backstage, Cortex or OpsLevel. We found no public information on how the AI features handle data — model provider or opt-out — nor a named MTTA or MTTR report, though advanced insights and custom dashboards are described. 1 3 6 4 5

Report an error

The Skeptic

Declaration from Slack via the /incident command (Teams on Pro and Enterprise), incident roles, severities to SEV-4, workflows, auto-started video bridges, public/internal/customer status pages with components and subscribers, timelines, AI-drafted post-mortems and AI summaries, follow-ups exported and synced to Jira or Linear, a service catalogue and simulation mode are all documented. The AI features come with no model provider, data handling or opt-out statement, and I found no explicit MTTA or MTTR analytics, so the top tier is out of reach. 3 4 5 6 8

Report an error

Integrations, API & administration

panel disagrees Show reasoning
How this is scored

How the tool fits the stack and the organisation: inbound integrations with monitoring and observability tools (Prometheus, Grafana, Datadog, Zabbix, Checkmk, PRTG, Azure Monitor, CloudWatch, Sentry), outbound integrations with chat, ticketing and ITSM tools (Slack, Microsoft Teams, Jira, ServiceNow, ConnectWise, Autotask), bidirectional sync, a documented REST API, webhooks and a Terraform provider, teams and services, roles and permissions, single sign-on (SAML or OIDC) and SCIM, audit logs, multi-tenant or customer separation for service providers, and migration help from other tools.

0 — No integrations and no administration beyond a single shared account.

3 — Email and webhook intake and a few named integrations; the API, roles and single sign-on are basic or not described.

5 — Dozens of named inbound and outbound integrations including Slack or Teams and Jira, a documented REST API and webhooks, teams with roles, two-factor authentication, single sign-on, and an import path from at least one other tool.

8 — Bidirectional ITSM and ticketing sync, a Terraform provider or configuration as code, SCIM provisioning, granular roles per team, audit logs, service-provider or multi-tenant set-ups, and API coverage of schedules, escalations and incidents documented.

10 — Administration that scales across many teams and customers: every setting reachable by API with parity stated, audit logs exportable to a SIEM, SSO enforced with SCIM, white-label or sub-account management for service providers, and documented migration from the major competitors.

Report an error

The SRE Lead

My stack is covered — Prometheus, Grafana and Sentry are named inbound sources among more than a hundred integrations, ServiceNow syncs two ways, Jira, Linear and Azure DevOps keep follow-ups in sync, and audit logs export to AWS S3, Datadog SIEM or Splunk. The REST API is genuinely documented with an OpenAPI 3.0 spec, cursor pagination, published rate limits with response headers, official SDKs in seven languages, a CLI and a sandbox, plus Terraform support for on-call configuration, Okta SAML with SCIM provisioning, custom RBAC on enterprise, and migration tools from PagerDuty, Opsgenie and Atlassian Statuspage. We found no public information on service-provider or multi-tenant administration, white-labelling or sub-accounts, or a stated guarantee of full API parity with the UI. 3 5 7 8

Report an error

The IT Operations Manager

Inbound monitoring spans forty-plus named sources and outbound ticketing includes Jira, Linear and Zendesk, with two-way ServiceNow sync, audit logs exportable to AWS S3, Datadog SIEM or Splunk SIEM, and migration tools from PagerDuty and Opsgenie plus Atlassian Statuspage. The REST API is published with an OpenAPI 3.0 spec, official client libraries for seven languages, a CLI, Terraform support and explicit rate limits, and covers actions, alerts, escalations, incidents, on-call schedules, catalog, status pages, workflows and audit logs; SSO and SAML are on every plan with SCIM and custom role-based access control at enterprise. We found no public information on multi-tenant or service-provider separation, or on API parity with the web interface. 2 3 5 7 8

Report an error

The MSP NOC Lead

The API is genuinely documented — an OpenAPI 3.0 spec, seven official SDKs, rate limits with Retry-After, cursor pagination and a no-breaking-changes policy with a three-month upgrade window — and it reaches schedules, escalations, incidents, status pages and audit logs, with Terraform, webhooks, a sandbox and a CLI alongside. ServiceNow syncs two-way, Jira and Linear keep incident actions in step, audit logs export to S3, Datadog or Splunk for our Sentinel workflow, and SSO with SAML and SCIM plus custom RBAC on Enterprise covers administration. We found no public information on multi-tenant or customer separation for service providers, and among the named connectors I see Datadog, Grafana, Prometheus, CloudWatch and Splunk but we found no public information on Zabbix or Autotask — the custom HTTP source, webhooks and Zapier give me a bridge. 3 5 7 8

Report an error

The ICT Risk Officer

A documented REST API with an OpenAPI spec, client libraries in seven languages, a CLI, webhooks and Terraform, endpoint coverage spanning schedules, escalations and incidents, SAML SSO with SCIM provisioning, two-way ServiceNow sync, audit logs streamable to Datadog, Splunk and S3, and documented migrations from PagerDuty, Opsgenie and Atlassian Statuspage. We found no public information on white-label or sub-account management for service providers or a stated API parity with the dashboard, which is all that keeps this from the top level. 3 4 5 7 8

Report an error

The Engineering Manager

This is the strongest area for a team like mine: a documented REST API with an OpenAPI 3.0 spec, official client libraries in seven languages, a CLI, per-endpoint rate limits and documented API coverage of schedules, escalations, incidents and audit logs, with Terraform for configuration as code. Named integrations run past a hundred — Prometheus, Grafana, Datadog, Sentry and CloudWatch inbound; Jira, Linear and a two-way ServiceNow sync outbound — alongside SCIM provisioning via Okta and Rippling, custom RBAC on the top plan, and audit logs exportable to S3 or streamed to a SIEM. Migration tools import schedules and escalation paths directly from PagerDuty or Opsgenie. 7 5 3 2 8

Report an error

The Skeptic

Over a hundred named integrations including two-way ServiceNow sync, a REST API with a published OpenAPI 3.0 spec, official client libraries in seven languages, a CLI, Terraform support, webhooks with a sandbox, SSO via SAML and SCIM through Okta and Rippling, custom RBAC on Enterprise, and audit logs exportable to S3 or streamed to Datadog or Splunk SIEM — plus documented migrations from PagerDuty, Opsgenie and Atlassian Statuspage. I found no public information on white-label or sub-account management for service providers, nor any statement of full API parity for every setting. 3 5 7 8

Report an error

Platform reliability, security & compliance

panel disagrees Show reasoning
How this is scored

Whether the pager works on the day everything else is down and holds up in an audit: an architecture independent of the customer's own cloud, multi-region or multi-zone hosting with failover, a stated availability or SLA with credits, the vendor's own public status page and incident history, delivery via redundant carriers, encryption in transit and at rest, security certifications (ISO 27001, SOC 2, BSI C5), penetration tests, data retention and deletion, audit trails, and what the vendor documents for DORA, NIS2, HIPAA or other regulated customers.

0 — Nothing on availability, security or how the service is operated.

3 — A claim of high availability or "enterprise security"; the SLA, status page, certifications and architecture are basic or not described.

5 — A public status page, a stated availability or SLA, hosting regions named, encryption in transit and at rest, ISO 27001 or SOC 2 stated, and data retention described.

8 — An SLA with credits published, the incident history public, multi-region failover or redundancy documented, redundant notification carriers named, certifications with their scope, a trust centre with reports on request, and a DORA or NIS2 addendum or mapping offered.

10 — Operation evidenced end to end: failover tested and published, independent audits (ISO 27001, SOC 2 Type II, BSI C5) with reports available, regulatory obligations for financial and critical-infrastructure customers explained in plain language, and the vendor's own post-incident reviews public.

Report an error

The SRE Lead

There is a public status page with per-group component uptime and a monthly calendar of incident history, a 99.99 percent uptime SLA on the enterprise plan, a claimed 99.99 percent alert delivery reliability, SOC 2 Type I and II, HIPAA and GDPR compliance claims, annual third-party penetration tests shared via a trust centre, AES-256 encryption, weekly OWASP scans, a bug bounty and responsible disclosure. But we found no public information on hosting regions or multi-region failover, redundant notification carriers, data retention and deletion, or DORA and NIS2 documentation for regulated customers, and the captured pages do not confirm SLA credits even though an SLA page exists. 2 8 9 10

Report an error

The IT Operations Manager

A public status page shows component groups with uptime and a calendar of incident history, the enterprise plan carries a 99.99 percent uptime SLA, and the vendor states SOC 2 Type I and II, HIPAA and GDPR compliance, annual third-party penetration tests shared via a trust centre, AES-256 encryption at rest, weekly OWASP scans and a bug bounty. We found no public information on hosting regions or multi-region failover, which is what I need to know the pager still works when the plant's own network is down, nor on SLA credits, encryption in transit, data retention or a DORA or NIS2 mapping. 2 5 8 9 10

Report an error

The MSP NOC Lead

A public status page with component-level uptime, incident history and subscription, a 99.99% uptime SLA on Enterprise, SOC 2 Type I and II, HIPAA and GDPR compliance claims, annual third-party penetration tests shared through a trust centre, weekly OWASP scanning and a bug bounty make a solid audit file. AES-256 data encryption and SHA-256 password hashing are stated. We found no public information on multi-region failover, redundant notification carriers, SLA credits, data retention, or a DORA or NIS2 addendum — the first questions my regulated German customers ask. 8 9 10 11

Report an error

The ICT Risk Officer

A 99.99 percent uptime SLA, a public status page with incident history, SOC 2 Type I and II, HIPAA and GDPR statements, AES-256 encryption, weekly vulnerability scans and annual third-party penetration tests shared via a Trust Center are documented. We found no public information on hosting regions or multi-region failover, SLA credits, data retention, certification scope, or a DORA or NIS2 addendum — precisely the pieces I need before this tool goes into our ICT third-party register. 8 9 10

Report an error

The Engineering Manager

There is a public status page with per-component uptime and a visible history window, a stated 99.99 percent uptime SLA on the enterprise plan, and a security page stating SOC 2 Type I and II, GDPR compliance, AES-256 encryption, annual third-party penetration tests shared through a trust centre, weekly OWASP scans and a bug bounty. We found no public information on hosting regions, multi-region failover, SLA credits, data retention and deletion, or anything addressing DORA or NIS2 customers — the questions our auditor asks first. 10 8 9 11

Report an error

The Skeptic

A public status page with per-component uptime and an incident history calendar, a 99.99 percent uptime SLA on the Enterprise plan, SOC 2 Type I and II and HIPAA claims, AES-256 encryption, annual third-party penetration tests shared through a Trust Center and weekly OWASP scans give real substance. But the captured pages never say what the SLA pays in credits, whether hosting is multi-region, which carriers deliver the pages, how long data is retained, or anything for DORA or NIS2 customers. 8 9 10

Report an error

European sovereignty panel opinion

n/r n/r n/r n/r Show reasoning
How this is scored

Who the contracting entity and the parent company are, where alerts, incident timelines, chat transcripts, contact data, phone numbers and account data are stored and processed, and who the subprocessors are (hosting, SMS and voice carriers, push services, email delivery, AI summary and transcription models, analytics, support and payment tools). Independently sourced by the sovereignty pipeline. Telephony and push providers needed to reach a responder in another country are part of what the product does and are not counted against it; where the data is stored and who processes it is. A self-hosted edition the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.

0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.

3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.

5 — EU hosting available and an EU contracting entity or EU representative, but parts of the chain (SMS and voice, AI, support, payment) run through non-EU providers without a stated safeguard.

8 — EU hosting on named infrastructure, EU contracting entity, subprocessors listed with their locations, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated — or a self-hosted edition documented that keeps every record on the customer's own servers.

10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor including the AI models and notification carriers, or a self-hosted edition with no call home, data export and deletion documented, and certifications published with their scope rather than implied.

Report an error

The SRE Lead

The copyright and legal pages name Pineapple Technology Ltd. with terms governed by the laws of England and Wales, so the contracting entity sits outside the EU on what is shown, though the company seat itself is not stated on the captured pages. We found no public information on where alerts, incident timelines, chat transcripts, contact data and phone numbers are stored or processed, on the hosting infrastructure, on any subprocessor list, or on a published data processing agreement — a GDPR compliance claim is the only chain-adjacent statement. As a Berlin operator I cannot see the chain my on-call data runs through, and a UK-law contract with an unstated hosting and subprocessor chain is what this level of evidence supports. 1 2 11

Report an error

The IT Operations Manager not rated — no public information

We found no public information on where alerts, incident timelines, chat transcripts, contact and phone data or account data are stored and processed, who the subprocessors are, or whether a data processing agreement is offered. The pages name Pineapple Technology Ltd. and claim SOC 2 and GDPR compliance, but we found no public information on the entity's jurisdiction, hosting location or subprocessor chain on the vendor homepage, legal and SLA pages, security page or pricing page that we read. 1 2 9 11

Report an error

The MSP NOC Lead not rated — no public information

We found no public information on where alerts, incident timelines, contact data and account data are stored or processed, who the subprocessors are, or a published data processing agreement; even the jurisdiction of Pineapple Technology Ltd., named only in copyright lines, is not stated on the pages we read. For a Nuremberg MSP with sixty customers, this is the first question I would put to the vendor. 1 9 11

Report an error

The ICT Risk Officer not rated — no public information

We found no public information on where alerts, incident timelines, chat transcripts and contact data are stored or processed, on the subprocessors behind hosting, SMS, voice and the AI features, or on a published data processing agreement; the captured pages name the contracting entity as Pineapple Technology Ltd. but do not state its seat. 1 9 11

Report an error

The Engineering Manager

The captured pages identify the contracting entity as Pineapple Technology Ltd. with terms governed by the laws of England and Wales, and nothing more. We found no public information on where alerts, incident data and contact details are hosted, on the subprocessors behind SMS, voice, push and AI features, or on a published data processing agreement — which for a Hamburg company with a works council is not enough to clear procurement. 1 2 11

Report an error

The Skeptic not rated — no public information

We found no public information on the captured pages about where alerts, incident timelines, contact data and account data are stored or processed, who the subprocessors are, whether a data processing agreement is published, or the contracting entity's seat; the copyright line names Pineapple Technology Ltd. under the laws of England and Wales and the security page claims GDPR compliance, but none of the sovereignty dimensions are evidenced. 1 2 9

Report an error

Pricing transparency

panel disagrees Show reasoning
How this is scored

Whether a buyer can compute the real annual cost from public pages alone: price per user or responder and per plan, whether stakeholders and viewers are free, how many SMS and voice notifications are included and what the rest cost per country, which features (incident response, status pages, AI, live call routing, SSO, audit logs) are add-ons or in higher plans, platform fees, minimum seats, annual versus monthly billing, and the currency and VAT treatment.

0 — No public prices at all; every customer is a sales call.

3 — A starting price per user exists, but notification limits, add-ons and the enterprise tier are unclear.

5 — Plans are public with their price per user and main inclusions, but at least one commonly needed piece (SMS and voice volume, status pages, AI, SSO or the top tier) is unpriced or "contact sales".

8 — Every plan priced publicly with its scaling rule, notification limits and overage prices stated, add-ons priced, stakeholder seats explained, minimum term and billing options and VAT treatment stated.

10 — Complete price computability: annual cost derivable for a given number of responders, stakeholders, notifications and status pages, with every add-on, overage and support fee and the cancellation and data-export terms published.

Report an error

The SRE Lead

Per-user prices are public — Basic is Free Forever, on-call is $20 per user / month standalone, Pro is $25 per user / month with the on-call add-on at $10 per user / month on the team plan — and per-plan limits for integrations, public and internal status pages, subscribers and custom domains are stated, with status pages included rather than a separate charge. But the enterprise tier is Let's talk, the root cause analysis, autonomous agent and Nexus data source add-ons carry no public prices, and we found no public information on SMS and voice volumes or per-country overage costs, annual versus monthly billing options, VAT treatment, minimum seats or cancellation and export terms. A buyer can price the mid tiers but cannot compute a full annual cost from these pages. 2 3 4 8

Report an error

The IT Operations Manager

Basic is "Free Forever", on-call is "$20 Per user / month" standalone with an add-on of $10 per user per month on Team and $20 on Pro, Pro itself is "$25 Per user / month", and Enterprise is "Let's talk" with a custom proposal. The captured pages give different figures for status page limits, one saying there are no limits on page views, subscriber counts or number of pages while the pricing page shows one public page on three tiers and internal pages unlimited only above Basic. We found no public information on SMS and voice notification volumes or per-country costs, VAT treatment, billing terms, or prices for the root-cause-analysis, autonomous-agent and Nexus add-ons. 2 4 8

Report an error

The MSP NOC Lead

Basic is free forever, on-call standalone is $20 per user per month, Pro is $25 per user per month, the on-call add-on is $10 per user per month on Team and $20 on Pro, and per-plan limits for integrations, status pages, live call routing numbers and SSO tiers are published, with status pages included without subscriber or page-view limits. Against that, the Enterprise tier is "Let's talk", and the root-cause-analysis, autonomous-agent and Nexus data-source add-ons carry no price. We found no public information on SMS and voice volumes and overage prices, annual versus monthly billing, minimum seats or VAT treatment, so I cannot compute a real annual cost for sixty responders. 2 4 8

Report an error

The ICT Risk Officer

Plan prices are public — Basic free forever, Pro at $25 per user / month, on-call standalone at $20 per user / month, with the on-call add-on at $10 per user / month on one plan and $20 per user / month on another — and per-plan limits for status pages, subscribers and integrations are stated alongside a no-hidden-fees claim. But the Enterprise tier is 'Let's talk', the root cause analysis, autonomous agent and Nexus add-ons carry no prices, and SMS and voice volumes, VAT treatment and billing terms are not stated, so a real annual cost is not computable from the public pages. 2 4 8

Report an error

The Engineering Manager

Prices are public for the named tiers: Basic is Free Forever, Pro is $25 per user / month, on-call standalone is $20 per user / month with the on-call add-on at $10 on the middle plan and $20 on Pro, and status pages are included with no page-view, subscriber or page-count limits. The enterprise tier is a custom proposal, the root-cause-analysis, autonomous-agent and Nexus add-ons carry no price, and we found no public information on SMS and voice volumes and overage costs, VAT treatment or billing terms. Unlimited viewer access for read-only stakeholders is described but not priced — which matters to me, since managers who only read along should not cost a responder seat — and the captured pages give different figures for how many integrations the plans include. 8 4 2 3

Report an error

The Skeptic

Basic is free forever, standalone on-call is $20 per user per month, Pro is $25 per user per month with on-call addable at $20 on Pro and $10 on the Team plan, integration counts and status page counts are shown per plan, and unlimited viewer access is offered. But Enterprise is a custom proposal, the root cause analysis, autonomous agent and Nexus data source add-ons carry no public prices, and I found no SMS or voice volumes or overage prices, no minimum term, billing options or VAT treatment, so the annual cost for a given team is not computable from public pages. The captured pages also give different figures for how many status pages each plan includes. 2 4 8

Report an error

European sovereignty — proven facts

1 of 6 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Hosting location Not determined — uncited Report an error
Hosting options Not determined — uncited Report an error
Open source Not determined — uncited Report an error
Data processing agreement Published, self-serve unverified
Why unverified?

The excerpt shows only the link title in the legal navigation of the SLA page; the Data Processing Addendum document itself is not captured, so self-serve conclusion is inferred from its publication in the site's legal menu.

1/1 pts 11 Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about incident.io

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.

What are the best alternatives to incident.io?

As of 18 Nov 2026, the panel rates ilert (4/5), All Quiet (3.5/5) and OneUptime (3.5/5) 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 (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: incident.io alternatives.

Where this could be wrong

What we left out

A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.

Sources (11)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor homepage incident.io Checked 6 Nov 2026 Details →
  2. 2 Features page (on-call) incident.io Checked 6 Nov 2026 Details →
  3. 3 Features page (incident response) incident.io Checked 6 Nov 2026 Details →
  4. 4 Features page (status pages) incident.io Checked 6 Nov 2026 Details →
  5. 5 Integrations page incident.io Checked 6 Nov 2026 Details →
  6. 6 Documentation docs.incident.io Checked 6 Nov 2026 Details →
  7. 7 API documentation docs.incident.io Checked 6 Nov 2026 Details →
  8. 8 Pricing page incident.io Checked 6 Nov 2026 Details →
  9. 9 Security / trust page incident.io Checked 6 Nov 2026 Details →
  10. 10 Public status page status.incident.io Checked 6 Nov 2026 Details →
  11. 11 Service level agreement incident.io Checked 6 Nov 2026 Details →