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 Rootly Inc. · rootly.com

Compare with incident.io → Report an error on this page Is this your product? →

Link to this page

Rootly: AI-assisted analysis on whats-best.ai Rootly: 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.

Rootly at a glance

Vendor
Rootly Inc.
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
Not stated on the vendor’s pages as of 6 Nov 2026
Panel verdict
The AI panel rates Rootly 3/5, the mean of 6 judges. Rootly is an AI-native platform for on-call scheduling, incident response, status pages and retrospectives. how scores are made
As of
Vendor pages captured 6 Nov 2026; evaluated by the panel 6 Nov 2026. all sources

Rootly alternatives, European ones first →

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

The IT Operations Manager

Weighted verdict

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.

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

Scored by The IT Operations Manager

Panel median The IT Operations 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 IT Operations Manager
On-call schedules, rotations & escalation 4 of 5 0 of 5
Alert delivery, routing & noise reduction 3.5 of 5 0 of 5
Incident response, status pages & post-incident review 4 of 5 0 of 5
Integrations, API & administration 4.5 of 5 0 of 5
Platform reliability, security & compliance 3.5 of 5 0 of 5
European sovereignty 2 of 5 0 of 5
Pricing transparency 2.5 of 5 0 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 IT Operations Manager

Rotations run daily through monthly plus custom 8- or 12-hour shifts, with layered primary and secondary cover, time zones, shadow shifts for new engineers, holiday overlays from an iCal feed, and overrides raised from Slack, the web or the mobile app — everything my five-admin weekly standby needs. Escalation policies carry per-step delays with acknowledgement timeouts and automatic second and third steps, so the deputy is paged after the delay I set, and round robin plus automated gap detection with a fallback assignee stops a night going uncovered. Schedules, rotations and escalation policies can be managed as code in Terraform, and the on-call pay calculator exports active versus standby hours to Excel or CSV for payroll. 2 16 17 6

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 IT Operations Manager

Voice, SMS, push, Slack and email with automatic retries, fallbacks and a do-not-disturb override for critical alerts, plus live call routing with IVR trees and voicemail-to-page, covers my requirement that a Checkmk alert becomes a phone call. Routing rules evaluate alert source, normalized fields and raw payload values, alert grouping and deduplication are documented in detail — the first matching alert pages and later matches join silently under a leader within a rolling window from five minutes to seven days — and heartbeats, deferral paths and route disabling handle silent failures and planned maintenance. We found no public information on the countries and channels where SMS and voice are delivered, or on per-notification delivery receipts. 2 7 18 19

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 IT Operations Manager

Incidents are declared and run in Slack, Teams or Google Chat with severities up to SEV0, custom roles, and a timeline, while playbooks auto-attach by severity, service, functionality, team or incident type with their tasks added as action items. Public and private status pages with components, groups, subscribers and custom domains are included with Incident Response, and workflows can page on-call, file a Jira ticket and post updates automatically. Retrospectives come with templates and AI blocks, follow-up actions track into Jira or Linear, and the AI data handling is described: providers neither store the data nor use it for training, and customer data is never used to improve results for others. 9 15 20 21 25

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 IT Operations Manager

Ninety-four integrations are listed including Prometheus Alertmanager, Datadog, Grafana, Splunk and a generic webhook alert source for any tool that can send a webhook — the documented route for my Checkmk and PRTG stack, as we found no public information on named integrations for either. The REST API is documented with an OpenAPI specification, Go and Python SDKs, a CLI and a Terraform provider that manages schedules, rotations and escalation policies as code, and SAML single sign-on with SCIM 2.0 provisioning is described down to attribute and group mappings. Granular roles per team, an audit log with unlimited tenant-lifetime retention exportable through the API, isolated tenants for full separation, and migration from PagerDuty and Opsgenie on every plan complete the picture. 6 8 9 17 23 24

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 IT Operations Manager

A multi-region redundant architecture with a 99.99% uptime SLA and multi-channel fallbacks — a critical alert landing even when one channel or provider is degraded — plus the vendor's own public status page gives me the independent paging path I need when the plant's own network is the thing that is down. SOC 2 Type II is maintained with the report available under NDA, a pentest report and trust centre exist, and audit logs are retained for the tenant lifetime with sensitive fields automatically redacted. We found no public information on SLA credits, redundant notification carriers by name, or a DORA addendum beyond a mention that documented incident processes help teams comply with such frameworks. 2 9 11 12 24

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 IT Operations Manager

The contracting entity is Rootly, Inc. of San Francisco and the services are hosted and operated in the United States through Rootly and its service providers, with AI running through providers like OpenAI and Anthropic unless pointed at your own Azure environment. A subprocessor list is published, a data processing addendum is available through the account team, SOC 2 Type II is maintained, and EU-U.S. Data Privacy Framework certification is claimed with FTC enforcement. We found no public information on EU hosting or a European contracting entity, so for my three plants the alerting, timeline and contact data chain runs through the United States. 6 15 24

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 IT Operations Manager

On-Call and Incident Response are each published at $20 per user / month, with per-plan inclusions shown such as one external and one internal status page, single sign-on on every plan and SCIM on the enterprise tier, and migration included on every plan. On-call paging requires a separate seat type, a bundle discount for buying the products together is offered without figures, and a PagerDuty contract buyout of up to 12 months is published. We found no public information on AI SRE pricing, included SMS and voice volumes or overage prices, minimum terms, billing options or VAT treatment, so I cannot compute the real annual cost for my five responders from public pages alone. 2 9 24

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 On request unverified
Why unverified?

The agreement is not published for direct download; it is obtained by contacting the vendor's account team, and the trust center likewise gates its 'Data Processing Agreement' document behind an access request.

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

Questions about Rootly

Is Rootly European?

No. whats-best.ai classifies Rootly as Rest of world.

Where does Rootly store data?

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

Does Rootly have a free plan?

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

What are the best alternatives to Rootly?

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: Rootly 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 (25)

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

  1. 1 Vendor homepage rootly.com Checked 6 Nov 2026 Details →
  2. 2 Features page (on-call) rootly.com Checked 6 Nov 2026 Details →
  3. 3 Features page (incident response) rootly.com Checked 6 Nov 2026 Details →
  4. 4 Features page (retrospectives) rootly.com Checked 6 Nov 2026 Details →
  5. 5 Features page (status pages) rootly.com Checked 6 Nov 2026 Details →
  6. 6 Integrations page rootly.com Checked 6 Nov 2026 Details →
  7. 7 Documentation docs.rootly.com Checked 6 Nov 2026 Details →
  8. 8 API documentation docs.rootly.com Checked 6 Nov 2026 Details →
  9. 9 Pricing page rootly.com Checked 6 Nov 2026 Details →
  10. 10 Security / trust page rootly.com Checked 6 Nov 2026 Details →
  11. 11 Trust centre security.rootly.com Checked 6 Nov 2026 Details →
  12. 12 Public status page status.rootly.com Checked 6 Nov 2026 Details →
  13. 13 About page rootly.com Checked 6 Nov 2026 Details →
  14. 14 Terms of service (names the operating company) rootly.com Checked 6 Nov 2026 Details →
  15. 15 Privacy policy rootly.com Checked 6 Nov 2026 Details →
  16. 16 On-call schedules, rotations & escalation — found from sitemap rootly.com Checked 6 Nov 2026 Details →
  17. 17 On-call schedules, rotations & escalation — found from sitemap rootly.com Checked 6 Nov 2026 Details →
  18. 18 Alert delivery, routing & noise reduction — found from sitemap docs.rootly.com Checked 6 Nov 2026 Details →
  19. 19 Alert delivery, routing & noise reduction — found from sitemap docs.rootly.com Checked 6 Nov 2026 Details →
  20. 20 Incident response, status pages & post-incident review — found from sitemap rootly.com Checked 6 Nov 2026 Details →
  21. 21 Incident response, status pages & post-incident review — found from sitemap docs.rootly.com Checked 6 Nov 2026 Details →
  22. 22 Integrations, API & administration — found from sitemap docs.rootly.com Checked 6 Nov 2026 Details →
  23. 23 Integrations, API & administration — found from sitemap docs.rootly.com Checked 6 Nov 2026 Details →
  24. 24 Platform reliability, security & compliance — found from sitemap docs.rootly.com Checked 6 Nov 2026 Details →
  25. 25 Platform reliability, security & compliance — found from sitemap rootly.com Checked 6 Nov 2026 Details →