Rootly
Rest of world Report an errorPanel 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
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
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Rootly is an AI-native platform for on-call scheduling, incident response, status pages and retrospectives. Scores cluster highest at 8-9 on on-call scheduling, incident response, and integration and administration: 94 integrations across 10 categories (other captured pages say 100+), a documented REST API with Terraform and an MCP server, SEV 0-4 incidents in Slack, Teams or Google Chat, and schedules managed as code. Sovereignty is the low, clustered at 4: the services are hosted and operated in the United States through Rootly and its service providers on Amazon Web Services, with EU-US Data Privacy Framework certification the stated safeguard, and we found no public information on EU hosting or a self-hosted edition. Pricing transparency scores 4-5: On-Call and Incident Response are published at $20 per user / month each, but we found no public information on SMS and voice volumes, the enterprise tier or VAT treatment. Most criteria split by a point: higher scores credit documented depth, lower ones flag missing delivery receipts, API parity or an AI opt-out. One judge is recorded at 0 on every criterion.
Speaks for it
- On-call scheduling covers daily, weekly, biweekly, monthly and custom 8- or 12-hour rotations with layered primary and secondary cover, automated gap detection and schedules managed as Terraform code.
- Paging runs over voice, SMS, push, Slack and email with automatic retries, fallbacks and a do-not-disturb override on critical alerts.
- Incidents run in Slack, Teams or Google Chat with severities SEV 0–4, playbooks that attach automatically, and public or private status pages that import from Atlassian Statuspage.
- The integrations directory lists 94 integrations across 10 categories — other captured pages say 100+ — over a documented REST API with an OpenAPI specification, Go and Python SDKs, a CLI, a Terraform provider, an MCP server and published rate limits.
- SAML 2.0 single sign-on works with any identity provider, SCIM 2.0 assigns roles by group, and the audit log retains every event for the tenant's lifetime with sensitive-field redaction and scheduled export.
Held against it
- The services are hosted and operated in the United States through Rootly and its service providers on Amazon Web Services, and we found no public information on EU hosting, an EU contracting entity or a self-hosted edition.
- Only two prices are public — $20 per user / month each for On-Call and Incident Response — and on-call paging requires a separate seat type; we found no public information on SMS and voice volumes, overage prices, the enterprise tier, AI SRE or VAT treatment, so a real annual cost is not computable from public pages.
- We found no public information on delivery receipts, on the countries where SMS and voice are delivered, or on named redundant notification carriers.
- We found no public information on SLA credits, certification scopes, or a DORA or NIS2 addendum from the vendor itself.
- We found no public information on an opt-out for the AI features or on enforced rest periods for on-call schedules.
Best for
- You run incidents in Slack or Microsoft Teams and want scheduling, paging, status pages and retrospectives from one platform with SAML single sign-on and SCIM 2.0.
- You are migrating from PagerDuty or Opsgenie and want a vendor-run migration included on every plan with a buyout of up to 12 months of a remaining PagerDuty contract.
- Your audits depend on an audit log retained for the tenant's lifetime, with sensitive fields automatically redacted and scheduled export over the API.
- You want AI drafting with published data handling — providers neither store nor train on the data and cross-customer use is ruled out — plus an Azure OpenAI option inside your own environment.
Avoid if
- You need EU hosting, an EU contracting entity or a self-hosted edition: the privacy policy states the services are hosted and operated in the United States through Rootly and its service providers, and we found no public information on European options.
- You must compute your full annual cost before talking to sales: only the two $20 per user / month prices are public, on-call paging requires a separate seat type, and we found no public information on SMS and voice volumes, overages or the enterprise tier.
- You need a vendor-issued DORA or NIS2 addendum or regulatory reporting templates: DORA is named as a framework the product helps teams comply with, and we found no public information on such documents from the vendor.
The scores
| Criterion | Panel median |
|---|---|
| On-call schedules, rotations & escalation | 4 of 5 |
| Alert delivery, routing & noise reduction | 3.5 of 5 |
| Incident response, status pages & post-incident review | 4 of 5 |
| Integrations, API & administration | 4.5 of 5 |
| Platform reliability, security & compliance | 3.5 of 5 |
| European sovereignty | 2 of 5 |
| Pricing transparency | 2.5 of 5 |
On-call schedules, rotations & escalation
panel disagrees
Show reasoningHide 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.
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
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
The MSP NOC Lead
Rotations run from daily to custom 8- or 12-hour shifts with per-rotation timezones, layered primary/secondary and shadow cover, overrides and one-click coverage requests from Slack or the app, holiday and HR-PTO overlays, automated gap detection that pages a fallback, and escalation policies with per-step delays, acknowledgement timeouts and round robin. Schedules, rotations and escalations are manageable as code in Terraform, and the on-call pay calculator exports per-person hours to Excel or CSV — exactly what our night-shift and per-account rotas need; we found no public information on rest-period enforcement or per-plan scheduling limits. 2 6 9 16 17
The ICT Risk Officer
Daily, weekly, biweekly, monthly and custom-length rotations with primary/secondary layering, per-rotation time zones, overrides and shadow shifts are documented, alongside multi-step escalation with acknowledgement timeouts and round robin, automated coverage-gap detection with fallback paging, schedules and escalation policies managed in Terraform, and an on-call pay calculator that exports active versus standby hours to Excel or CSV for payroll. Time-off overlays from Personio, BambooHR and similar HR systems support working-time planning, and an on-call metrics dashboard shows page distribution per responder. We found no public information on rest-period enforcement or on per-plan scheduling limits. 2 16 17 6 9
The Engineering Manager
Rotations cover daily, weekly, biweekly, monthly and custom 8- or 12-hour shifts with a per-rotation time zone, layered primary/secondary cover, round-robin escalation with per-step delays and acknowledgement timeouts — enough to build our follow-the-sun rota across three time zones. Coverage swaps run from the mobile app or Slack and create the override when a teammate accepts, gaps are flagged before a shift goes uncovered, PTO overlays from Personio or BambooHR keep the rota honest, and the On-Call Pay Calculator exports active-versus-standby hours to Excel or CSV for payroll — three of my four asks answered directly. The on-call metrics dashboard shows page distribution per responder, but we found no public information on an automatic warning when the same person is paged several nights running. 17 2 16 6
The Skeptic
Rotations run daily, weekly, biweekly, monthly or custom 8- and 12-hour shifts with per-rotation time zones, layered primary and secondary cover, overrides, shadow shifts and one-click coverage requests from Slack or the mobile app; escalation policies carry per-step delays, round robin and urgency-based paging, and automated gap detection pages a fallback before a shift goes uncovered. Schedules and escalation policies are managed as Terraform code, PTO overlays import from BambooHR, Personio, Rippling and others, and the on-call pay calculator exports hours to Excel or CSV for payroll. We found no public information on fairness or fatigue reports, enforced rest periods, or scheduling limits per plan. 2 6 9 16 17
Alert delivery, routing & noise reduction
panel disagrees
Show reasoningHide 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.
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
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
The MSP NOC Lead
Voice, SMS, push, Slack and email with retries, automatic fallback and do-not-disturb override for critical alerts is stated, routing conditions match payload fields via JSONPath with documented limits, and grouping and deduplication have their matching logic, time windows and leader behaviour fully documented. Heartbeats, live call routing with IVR trees and voicemail-to-page, and a per-alert timeline of the route, rule and destinations paged round it out; we found no public information on per-notification delivery receipts, per-country SMS and voice coverage, or maintenance-window suppression. 2 16 18 19
The ICT Risk Officer
Voice, SMS, push, Slack and email delivery with urgency-based channel choice, automatic retries and fallbacks and do-not-disturb override is documented, and the grouping logic is published in detail — leader and member behaviour, rolling windows from five minutes to seven days, content matching on payload fields via JSONPath — together with first-party heartbeats, live call routing with IVR trees and failover, deferral paths and route disabling for suppression, and a per-alert timeline recording the route applied and destinations paged. We found no public information on delivery receipts, on the countries and channels where SMS and voice are delivered, or on named redundant carriers. 2 7 18 19
The Engineering Manager
Voice calls, SMS, push, Slack and email are documented with automatic retries, fallbacks and a do-not-disturb override on critical alerts, and alert grouping is explained in unusual depth: leader/member behaviour, matching on title, urgency or payload via JSONPath, rolling windows from five minutes to seven days, and deduplication kept as a separate concept for repeat firings. Routing on payload fields with live preview of matching historical alerts, a timeline per alert recording route, rule and paged destinations, deferral paths, heartbeats and live call routing with IVR trees and voicemail-to-page round out the picture. We found no public information on the countries where SMS and voice are delivered or on delivery receipts per channel. 2 19 18
The Skeptic
Voice, SMS, push, Slack and email paging with automatic retries, fallbacks and a do-not-disturb override on critical alerts sits on routing that evaluates alert source, normalized fields and raw payload values via JSONPath with regex operators, time-window deferrals and first-match logic. Alert grouping and deduplication are documented down to leader and member mechanics with a rolling five-minute to seven-day window, live call routing handles IVR trees and voicemail-to-page, and heartbeats catch silent failures as a first-party liveness check. We found no public information on delivery receipts, on which carriers deliver SMS and voice or in which countries, or on notification volumes by plan. 2 7 8 18 19
Incident response, status pages & post-incident review
panel disagrees
Show reasoningHide 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.
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
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
The MSP NOC Lead
Incidents are declared in Slack, Teams or Google Chat with severities SEV 0 to 4, incident types driving their own workflow and playbooks, custom roles including security lead and legal counsel, and a timeline of events and decisions. Public and internal status pages carry components, groups, subscribers and a documented import from Atlassian Statuspage, postmortem templates include MTTR and cost metrics, follow-ups flow into Jira or Linear, and AI drafting is documented with named providers and a stated policy that providers neither store nor train on the data. We found no public information on an AI opt-out or per-plan limits, which keeps it off the very top. 4 5 6 15 20 21 25
The ICT Risk Officer
Incidents are declared from Slack or Teams with severities SEV 0 to SEV 4, custom roles, an incident timeline recording events and decisions, playbooks that attach on severity, service or incident type and carry tasks, workflows that page on-call and file tickets, public and private status pages with components, groups, subscribers and import from Atlassian Statuspage, and postmortem templates with follow-up action items tracked into Jira or Linear. The AI features come with their data handling described: providers named, no storage or training by the AI providers, no cross-customer use, an Azure-hosted model option and bring-your-own keys on Enterprise. We found no public information on major-incident or regulatory reporting templates, which is exactly what I would need to classify and report a major ICT incident within DORA deadlines. 4 5 6 9 15 20 21 25
The Engineering Manager
Incidents run in Slack or a native Teams experience with SEV 0–4 severities, auto-assigned roles, workflows that page, file Jira tickets and update the status page, and playbooks that attach automatically by severity, service or incident type. Public and private status pages carry components, subscribers, custom domains and SAML authentication, follow-ups track into Jira or Linear, and the AI drafting, root-cause suggestions and retro generation come with their data handling stated — providers neither store the data nor train on it, and you can bring your own key. We found no public information on an AI opt-out or on response limits per plan. 20 21 25 5 15 6
The Skeptic
Incidents are declared from Slack, Teams or Google Chat with SEV 0–4 severities, incident types that drive their own workflows, playbooks auto-attaching by severity, service or team, and a timeline of events and decisions; public and private status pages carry components, groups, subscribers, custom domains and SAML authentication, with import from Atlassian Statuspage. Follow-up actions track into Jira and Linear, retrospectives draft from AI blocks, and the AI data handling is stated: providers neither store nor train on the data and cross-customer use is ruled out. We found no public information on major-incident or regulatory reporting templates, or an opt-out for the AI features. 4 5 6 9 15 20 21 25
Integrations, API & administration
panel disagrees
Show reasoningHide 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.
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
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
The MSP NOC Lead
Roughly a hundred named integrations across ten categories — native Teams, Jira, ServiceNow, Zendesk, Zoom — plus a generic webhook alert source that would take our Zabbix, sit on top of a documented REST API with an OpenAPI specification, Go and Python SDKs, a CLI, a Terraform provider and an MCP server. SAML single sign-on works with any IdP, SCIM 2.0 maps groups to roles, granular role-based access covers teams, services and severities, isolated tenants give per-customer separation, the audit log keeps unlimited history with scheduled API export, and migrations from PagerDuty and Opsgenie are documented. We found no public information on a native Autotask or ConnectWise connector or on full API parity for every setting — for a PSA-driven shop like mine that is the gap. 2 6 8 10 17 21 22 23 24
The ICT Risk Officer
Ninety-plus named integrations including Datadog, Prometheus, Sentry, Jira, ServiceNow and Zoom, a documented REST API with an OpenAPI specification, Go and Python SDKs, published rate limits and OAuth 2.0, a Terraform provider covering schedules and escalation policies as code, SAML 2.0 single sign-on and SCIM 2.0 with role assignment via identity-provider groups, granular access control down to severity and incident type, isolated tenants, and migration from PagerDuty and Opsgenie on every plan. The audit log retains every create, update and delete event for the tenant's lifetime, redacts secrets automatically and exports on a schedule over the API, which is what I would feed into our SIEM. We found no public statement that every setting is reachable by API with parity to the user interface. 6 7 8 10 17 22 23 24
The Engineering Manager
Around a hundred named integrations across alerting, ticketing, ITSM, catalogue and HR, a documented JSON:API REST API with an OpenAPI specification, official Go and Python SDKs and published rate limits, plus a Terraform provider that manages schedules, rotations and escalation policies as code. SAML 2.0 single sign-on with domain-enforced redirect, SCIM 2.0 provisioning with group-to-role mapping, granular role-based access down to severity and component, a read-only auditor role, unlimited audit log retention with export, and isolated tenants for full separation are all documented. Migration from PagerDuty and Opsgenie is documented and included on every plan, with a contract buyout of up to 12 months. 6 8 17 22 23 24 10 9
The Skeptic
Ninety-four integrations across ten categories in the directory — other captured pages say 100+ — cover Datadog, Prometheus, Grafana, Sentry and Splunk inbound and Slack, Teams, Jira, ServiceNow, Linear and Zendesk outbound plus a generic webhook; the REST API publishes an OpenAPI spec with Go and Python SDKs, a CLI, an MCP server, and a Terraform provider that manages schedules and escalation policies. SAML single sign-on redirects matching domains, SCIM 2.0 maps groups to roles, permissions are granular per team, service, severity and component, the audit log is retained for the tenant's lifetime with sensitive-field redaction and a JSON:API export endpoint, isolated tenants are offered, and migration from PagerDuty and Opsgenie is run by a migration team. We found no public information on bidirectional ticketing sync or on full API parity with the product's settings. 6 8 10 17 22 23 24
Platform reliability, security & compliance
panel disagrees
Show reasoningHide 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.
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
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
The MSP NOC Lead
A multi-region redundant architecture, a 99.99% uptime SLA with multi-channel fallbacks, and a public status page with per-component uptime and incident history are stated, and the trust centre offers a SOC 2 Type II report under NDA and a pentest report. Security incident management with separate technical and legal channels plus DORA among the named frameworks speaks to regulated buyers; we found no public information on SLA credits, named redundant notification carriers, certification scope, or service-level encryption at rest. 2 11 12 15 20 24 25
The ICT Risk Officer
A 99.99% uptime SLA on a multi-region redundant architecture, a public status page with per-component uptime and history, SOC 2 Type II with the report available under NDA, a trust centre listing a pentest report, backups, erasure and cyber insurance, and an audit trail retained for the tenant's lifetime and exportable on a schedule. The SLA credits are not stated, certification scope is not published and no notification carriers are named; the DORA reference extends only to helping teams keep documented, testable incident processes, and we found no public information on a DORA or NIS2 addendum or mapping. 2 11 12 15 20 24
The Engineering Manager
A public status page with per-component uptime, a stated 99.99% uptime SLA on a multi-region redundant architecture, SOC 2 Type II with the report available under NDA, a pentest report on request, and a trust centre covering encryption, backups, BC/DR and endpoint security give me most of what an audit asks for, and the xz and NPM supply-chain notices show active security communication. We found no public information on SLA credits, named redundant carriers or certification scope, and DORA appears only as a framework the product helps teams comply with rather than as an addendum or mapping. 2 12 24 11 20
The Skeptic
A 99.99% uptime SLA on a multi-region redundant architecture, a public status page with per-component uptime, SOC 2 Type II with the report available under NDA, a pentest report, a trust centre, and an audit log retained indefinitely with export — this is evidenced operation rather than a badge wall. Retention and deletion are described, custom retention is accommodated, and security-incident workflows produce audit-ready records for SOC 2. We found no public information on SLA credits, named redundant notification carriers, certification scopes, or a DORA or NIS2 addendum offered by the vendor itself. 2 11 12 14 15 24
European sovereignty
panel opinion
panel disagrees
Show reasoningHide 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.
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
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
The MSP NOC Lead
Rootly, Inc. is a United States company whose privacy policy states the services are hosted and operated in the United States through Rootly and its service providers. A subprocessor list is published, a data processing addendum is available through the account team, and EU–US Data Privacy Framework compliance with FTC enforcement is claimed; we found no public information on EU hosting, an EU contracting entity, or a self-hosted edition — the documented chain runs through the US. 11 14 15 24
The ICT Risk Officer
The contracting and operating entity is Rootly, Inc. of the United States, the privacy policy states the services are hosted and operated in the United States through Rootly and its service providers on Amazon Web Services, and it reserves disclosure to United States public authorities including national security requests; the subprocessor list is published and a data processing addendum is available through the account team rather than published. Transfer cover rests on EU-US Data Privacy Framework certification, and the AI chain runs through OpenAI, Anthropic, Google and Mistral with an Azure-hosted boundary option; we found no public information on EU hosting or a European contracting entity. 6 11 15 24
The Engineering Manager
Rootly, Inc. is the contracting entity and the service is hosted and operated in the United States on Amazon Web Services, with a published subprocessor list, a data processing addendum available through the account team, and EU-U.S. Data Privacy Framework certification. AI providers include OpenAI, Anthropic, Google Gemini, Mistral and Azure OpenAI, with Azure keeping models inside your own compliance boundary. We found no public information on an EU hosting option, an EU contracting entity or a self-hosted edition — a real discussion point for my works council, since on-call contact data and phone numbers sit in the US chain. 15 11 24 6
The Skeptic
The chain is American end to end: Rootly, Inc. of San Francisco hosts and operates the service in the United States on Amazon Web Services, subprocessors are listed publicly, the data processing addendum is available through the account team, and EU-US Data Privacy Framework certification with FTC enforcement is the stated transfer safeguard. AI assistance connects to OpenAI, Anthropic, Google and Mistral, with an Azure OpenAI option that keeps data inside the customer's own Azure boundary. We found no public information on a European hosting option, an EU contracting entity, or a self-hosted edition. 6 11 15 24
Pricing transparency
panel disagrees
Show reasoningHide 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.
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
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
The MSP NOC Lead
Both On-Call and Incident Response are published at "$20 per user / month" with main inclusions such as status pages bundled with Incident Response, on-call paging is called out as a separate seat type, and a PagerDuty contract buyout of up to 12 months is offered. Notification volumes and per-country SMS and voice overages, AI SRE pricing, the Enterprise tier, minimum terms and VAT treatment are not publicly priced, so I cannot compute a real annual cost from these pages alone. 2 9 24
The ICT Risk Officer
On-Call and Incident Response are each listed at $20 per user / month with entitlement tables covering organizations, status pages, single sign-on, SCIM, audit logs and support by tier, Status Pages included with Incident Response, on-call paging as a separate seat type, an unquantified bundle discount and a buyout of up to 12 months of a remaining PagerDuty contract. We found no public prices for AI SRE or the enterprise tier, no SMS or voice volumes or per-country overage prices, and no billing-term or VAT treatment, so a real annual cost is not computable from the public pages alone. 2 9 24
The Engineering Manager
The two main products are priced publicly at $20 per user / month each, with status pages included in Incident Response, entitlements listed per plan, a bundle discount, and a PagerDuty contract buyout of up to 12 months. On-call paging requires a separate seat type, which suggests the managers who only read along may not need a paging seat, but we found no public information on whether read-only stakeholder seats are free, or on Enterprise pricing, SMS and voice volumes, VAT treatment and billing options — so I cannot yet compute the real annual cost my finance team will ask for. 9 24 2
The Skeptic
Two products are priced publicly at $20 per user / month each — On-Call and Incident Response — status pages are included with Incident Response, SSO with SAML appears in the listed tiers, per-plan entitlements for status pages and organizations are shown, and it is disclosed that on-call paging requires a separate seat type. We found no public information on the price of the enterprise tier or AI SRE, the size of the bundle discount, SMS and voice volumes or overage prices, stakeholder seats, billing terms or VAT treatment, so a buyer cannot compute the real annual cost from public pages. 2 9 24
European sovereignty — proven facts
1 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
|---|---|---|---|
| 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
- Evidence ages. The oldest capture behind this page is from 6 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data processing agreement. 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.
- Weak sourcing — Legal entity. Not confirmed on the vendor’s own pages as captured.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
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.
- 30 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 19 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 15 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 15 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 6 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 subprocessors facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 data fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
Sources (25)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage rootly.com Checked 6 Nov 2026 Details →
- 2 Features page (on-call) rootly.com Checked 6 Nov 2026 Details →
- 3 Features page (incident response) rootly.com Checked 6 Nov 2026 Details →
- 4 Features page (retrospectives) rootly.com Checked 6 Nov 2026 Details →
- 5 Features page (status pages) rootly.com Checked 6 Nov 2026 Details →
- 6 Integrations page rootly.com Checked 6 Nov 2026 Details →
- 7 Documentation docs.rootly.com Checked 6 Nov 2026 Details →
- 8 API documentation docs.rootly.com Checked 6 Nov 2026 Details →
- 9 Pricing page rootly.com Checked 6 Nov 2026 Details →
- 10 Security / trust page rootly.com Checked 6 Nov 2026 Details →
- 11 Trust centre security.rootly.com Checked 6 Nov 2026 Details →
- 12 Public status page status.rootly.com Checked 6 Nov 2026 Details →
- 13 About page rootly.com Checked 6 Nov 2026 Details →
- 14 Terms of service (names the operating company) rootly.com Checked 6 Nov 2026 Details →
- 15 Privacy policy rootly.com Checked 6 Nov 2026 Details →
- 16 On-call schedules, rotations & escalation — found from sitemap rootly.com Checked 6 Nov 2026 Details →
- 17 On-call schedules, rotations & escalation — found from sitemap rootly.com Checked 6 Nov 2026 Details →
- 18 Alert delivery, routing & noise reduction — found from sitemap docs.rootly.com Checked 6 Nov 2026 Details →
- 19 Alert delivery, routing & noise reduction — found from sitemap docs.rootly.com Checked 6 Nov 2026 Details →
- 20 Incident response, status pages & post-incident review — found from sitemap rootly.com Checked 6 Nov 2026 Details →
- 21 Incident response, status pages & post-incident review — found from sitemap docs.rootly.com Checked 6 Nov 2026 Details →
- 22 Integrations, API & administration — found from sitemap docs.rootly.com Checked 6 Nov 2026 Details →
- 23 Integrations, API & administration — found from sitemap docs.rootly.com Checked 6 Nov 2026 Details →
- 24 Platform reliability, security & compliance — found from sitemap docs.rootly.com Checked 6 Nov 2026 Details →
- 25 Platform reliability, security & compliance — found from sitemap rootly.com Checked 6 Nov 2026 Details →