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 Engineering Manager

Weighted verdict

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.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The Engineering Manager

Panel median The Engineering Manager This judge’s scores over the panel median. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median The Engineering Manager
On-call schedules, rotations & escalation 4 of 5 4 of 5
Alert delivery, routing & noise reduction 3.5 of 5 3.5 of 5
Incident response, status pages & post-incident review 4 of 5 4 of 5
Integrations, API & administration 4.5 of 5 4.5 of 5
Platform reliability, security & compliance 3 of 5 3 of 5
European sovereignty 0.5 of 5 0.5 of 5
Pricing transparency 2.5 of 5 2.5 of 5

On-call schedules, rotations & escalation

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 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

Alert delivery, routing & noise reduction

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 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

Incident response, status pages & post-incident review

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 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

Integrations, API & administration

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 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

Platform reliability, security & compliance

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 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

European sovereignty

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 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

Pricing transparency

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 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

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 →