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

Weighted verdict

Leads site reliability at a Berlin SaaS company with sixty engineers in eight product teams, Prometheus and Grafana for metrics, Sentry for errors and everything discussed in Slack. Wants an incident declared with one command, a channel with roles and a timeline, the status page updated from the same place, alerts grouped so one database outage does not page five teams, schedules kept in Terraform, and a postmortem that writes its first draft.

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

Scored by The SRE Lead

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

Rotations from daily to custom 8- and 12-hour shifts each with their own timezone, layered primary/secondary cover, shadow shifts, overrides from Slack or the mobile app, and escalation with per-step delays, round robin and acknowledgement timeouts. Gap detection flags holes before they page, a holiday calendar overlays PTO pulled from Personio or Rippling, schedules and escalation policies live in Terraform with a worked CI example, and the On-Call Pay Calculator exports active-versus-standby hours to Excel or CSV for payroll. I found no public information on rest-period rules being enforced or warned. 2 6 9 16 17

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

Voice, SMS, push, Slack and email with automatic retries, fallbacks and do-not-disturb override for critical alerts, plus routing rules on alert source, normalized fields and raw payload via JSONPath with regex operators, live preview against historical alerts, deferral paths, and first-party heartbeats. Alert grouping is documented deeper than most pager vendors I have evaluated — the leader pages, members join silently, status and noise propagate, rolling windows run from five minutes to seven days, and grouping different monitors is cleanly separated from deduplicating repeat firings. I found no public information on delivery receipts or the countries and channels where SMS and voice are delivered. 2 6 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 SRE Lead

Incidents are declared in Slack, Teams or Google Chat with roles auto-assigned, a timeline, tasks assigned by tagging Rootly, severities SEV0 through SEV4 and incident types that attach their own playbooks and workflows. Status pages come public and private with components, two-level groups, subscribers and import from Atlassian Statuspage, follow-ups push to Jira or Linear, and AI drafts updates and probable root cause with data handling spelled out — providers neither store nor train on the data, nothing crosses customers, and Azure OpenAI can stay inside your own tenant. I found no public information on an AI opt-out or on per-plan limits beyond status pages and organization counts. 5 6 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 SRE Lead

Prometheus Alertmanager, Grafana, Sentry and Datadog feed alerts in, Slack, native Teams, Jira, ServiceNow, Zendesk and Zoom sit on the outbound side, and a generic webhook source covers anything else — the captured pages give different totals for the directory (94 listings against a 100-plus claim), but either way the catalog is deep. The JSON:API REST API is documented with an OpenAPI spec, Go and Python SDKs, published rate limits and scoped global, team and personal keys; Terraform manages on-call as code; SAML SSO works with any identity provider; SCIM 2.0 assigns roles by group; RBAC is granular with an auditor role; audit logs are retained without limit and export on a schedule; isolated tenants separate operations; and migration from PagerDuty, Opsgenie and Splunk On-Call is documented with a contract buyout. I found no public information on bidirectional ticketing sync or on stated API-to-interface parity. 6 8 10 17 22 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 SRE Lead

A 99.99% uptime SLA on a multi-region redundant architecture, the vendor's own public status page with per-component uptime and incident history, SOC 2 Type II with the report available under NDA, a pentest report, cyber insurance, BC/DR, and audit logging with unlimited retention and automatic redaction of secrets. The SLA states no credits, no redundant notification carriers are named, certifications appear without their scope, and DORA shows up as a framework the product helps teams comply with rather than a dedicated addendum. 2 11 12 15 20 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 SRE Lead

Contracting is with Rootly, Inc. of San Francisco and the service is hosted and operated in the United States on Amazon Web Services, so alerts, timelines and contact data sit outside the EU. The stated safeguards are EU-US Data Privacy Framework certification backed by FTC enforcement, a published subprocessor list, and a data processing addendum available through the account team; the AI providers are US firms, though Azure OpenAI can run inside your own Azure environment. I found no public information on EU hosting, an EU contracting entity, or a European representative. 6 11 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 SRE Lead

Two public per-user prices exist — Incident Response at $20 per user per month and On-Call at $20 per user per month — with status pages included with Incident Response, on-call paging as a separate seat type, and some limits stated such as one external and one internal status page per plan. But I found no public information on SMS and voice volumes or overage pricing, the price of AI SRE or the size of the bundle discount, the enterprise tier, minimum seats, billing terms or VAT treatment — so the real annual cost cannot be worked out from public pages alone. 2 6 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 →