Xurrent IMR (Zenduty)
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 Xurrent, Inc. · zenduty.com
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.
Xurrent IMR (Zenduty) at a glance
- Vendor
- Xurrent, Inc.
- Headquarters
- Not stated on the vendor’s pages as of 7 Nov 2026
- Data hosting
- Outside the EU by default source, captured 7 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 7 Nov 2026
- Panel verdict
- The AI panel rates Xurrent IMR (Zenduty) 3/5, the mean of 6 judges. Xurrent IMR (Zenduty), an on-call and incident management platform sold by Xurrent, Inc., earned persona-weighted totals of 5.4 to 6.2. how scores are made
- As of
- Vendor pages captured 6 Nov 2026 to 7 Nov 2026; evaluated by the panel 7 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Xurrent IMR (Zenduty), an on-call and incident management platform sold by Xurrent, Inc., earned persona-weighted totals of 5.4 to 6.2. It is strongest on incident response, integration and admin, and on-call scheduling, each 6 to 7: judges cited rotations with time-zone and daylight-saving handling, escalation policies with acknowledgement timeouts and fallback when nobody is on call, playbooks auto-attached to incidents, AI postmortems and an AI SRE agent in every plan, 150+ claimed integrations with a documented REST API, and one-click migration from PagerDuty, Opsgenie or Incident.io with up to 12 free parallel months. Alerting and routing and pricing transparency sit at 6, with free call and SMS quotas published but the status-page add-on unpriced and overages covered by "T&C apply". Sovereignty is the outlier at 2 to 4: the contracting entity is US-based, the GDPR page updated 28 May 2019 states AWS US-east and US west, the parent trust centre lists AWS regions including Ireland and Germany, and the captured pages give different figures for residency — judges crediting the subprocessor list scored higher than those weighing the 2019 statement.
Speaks for it
- Layered rotations with time-zone and daylight-saving handling, plus escalation policies with acknowledgement timeouts, repeat cycles and fallback to the next rule when nobody is on call.
- An AI incident summarizer, AI-generated postmortems with root-cause analysis and an AI SRE agent listed as included in every plan.
- 150+ integrations claimed with Datadog, Grafana, New Relic, Jira, Slack and Teams named, plus a documented REST API with JavaScript, Ruby and Python SDKs.
- One-click migration scripts from PagerDuty, Opsgenie and Incident.io, with an offer to run free in parallel for up to 12 months.
- Starter at $5 per user per month billed yearly ($6 monthly) and Growth at $14 ($16) published with free call and SMS quotas per plan and a 14-day trial with no credit card required.
Held against it
- Sovereignty scored 2 to 4, the lowest range on the card, with the contracting entity Xurrent, Inc. headquartered in Santa Barbara and a GDPR page last updated 28 May 2019 stating AWS US-east and US west hosting.
- The captured pages give different figures for where this product's data sits, since the parent trust centre lists AWS regions including Ireland and Germany alongside the US.
- We found no public information on an availability SLA with credits, encryption in transit and at rest, SCIM provisioning or audit logs.
- We found no public information on delivery receipts, heartbeat monitoring or a do-not-disturb override, and no named carrier for the SMS and voice traffic.
- We found no public price for the status-page add-on, and notification overages beyond the free quotas are given only as "T&C apply".
Best for
- You are moving off PagerDuty, Opsgenie or Incident.io and want automated migration scripts with an option to run free in parallel for up to 12 months while the old contract winds down.
- You want AI incident tooling — a summarizer, AI-generated postmortems with root-cause analysis and an AI SRE agent — on the base plans, since the vendor states features are not gated by plan.
- You run a team within Growth's caps (up to 50 users, 5 teams, 25 integrations) and manage schedules through the documented API or Terraform.
- You value published pricing, per-plan free call and SMS quotas, and a 14-day trial with no credit card required.
Avoid if
- You need a European chain for this product: the contracting entity is a US company, the captured pages give different figures for residency, and we found no public information on a data processing agreement or EU hosting for it.
- You operate under HIPAA: the terms state that the Zenduty Cloud Solutions are not HIPAA compliant.
- Your procurement requires audit logs, an availability SLA with credits or DORA and NIS2 documentation before signature: we found none publicly, and confidential documentation requires an NDA.
- You must compute the full annual cost before committing: the status-page add-on carries no public price, notification overages are "T&C apply" and Enterprise is a custom proposal.
The scores
| Criterion | Panel median |
|---|---|
| On-call schedules, rotations & escalation | 3 of 5 |
| Alert delivery, routing & noise reduction | 3 of 5 |
| Incident response, status pages & post-incident review | 3.5 of 5 |
| Integrations, API & administration | 3.5 of 5 |
| Platform reliability, security & compliance | 3 of 5 |
| European sovereignty | 2 of 5 |
| Pricing transparency | 3 of 5 |
On-call schedules, rotations & escalation
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
The rotation engine is well documented: daily, weekly or custom rotations, layered shifts with time restrictions, time-zone and daylight-saving handling, overrides and round-robin, plus escalation policies with acknowledgement timeouts, repeat cycles, cross-team escalation and automatic move to the next rule when nobody is on call. The API exposes an on-call module and Terraform appears on the feature list, so schedules as code looks possible. I found no public information on calendar export, shift reminders, coverage-gap warnings or on-call hours exported for pay and working-time rules — that last one I need for a sixty-engineer German organisation. 14 15 5 6 12
The IT Operations Manager
The documentation shows layered schedules with daily, weekly or custom rotations, cumulative layers, time zones with daylight-saving handling, overrides, and day/week/month views, and escalation policies that combine schedules and individuals — the documented example escalates after five minutes to the backup schedule and after ten minutes to the manager, with repeat cycles and an automatic move to the next rule when a rule has nobody on call, which is exactly the deputy-after-ten-minutes behaviour I need for five admins on weekly standby. Round-robin scheduling and API modules for on-call and routing rules are documented, and the pricing page claims full API and Terraform. I found no public information on calendar export, shift reminders, coverage-gap warnings before they happen, or exporting on-call hours for pay and working-time rules. 14 15 5 6 2
The MSP NOC Lead
Documented schedules support layers with daily, weekly and custom rotations that can be restricted to specific times — enough for separate night and weekend rotas — with timezone and daylight-saving handling, overrides, and round-robin, plus escalation policies combining schedules and individuals, acknowledgement timeouts, repeat cycles and fall-through to the next rule when nobody is on call. On-call objects are also reachable through the documented API. I found no public information on calendar export, shift reminders, or an on-call hours report I could hand to payroll for working-time rules. 5 14 15
The ICT Risk Officer
The schedule documentation is genuinely deep: layered rotations with daily, weekly and custom periods, round robin, cumulative rotations, overrides, time-zone and daylight-saving handling, and escalation policies mixing schedules and individuals with acknowledgement timeouts, repeat cycles and a documented fallback when a rule finds nobody on call, all reachable through the API and a named Terraform provider. I found no public information on calendar export, shift reminders, or on-call hours exported per person for pay and working-time rules, so the compliance side of scheduling cannot be verified. 14 15 5 6 1
The Engineering Manager
The documentation covers layered schedules with daily, weekly and custom rotations, per-schedule time zones with a daylight-saving option, overrides, round-robin, and escalation policies with acknowledgement timeouts, repeat cycles and behaviour when nobody is on call — the mechanics for my three-country rota are there, though follow-the-sun hand-offs are not described as such. What our works council agreement needs is not in the captured pages: we found no public information on swapping a shift from the mobile app, on-call hours exported for payroll, or a warning when the same person is paged night after night. On-call objects are reachable through the documented API, which lifts it above the middle anchor. 14 15 5 1 2
The Skeptic
Schedules with layers, daily, weekly and custom rotations, cumulative layers, overrides, time-zone and daylight-saving handling and round-robin are documented, and escalation policies mix schedules and individuals with acknowledgement timeouts, configurable repeat cycles and a documented fallback to the next rule when a rule has nobody on call. I found no public information on calendar export, shift reminders, on-call hours reports for pay and working-time rules, or shift swaps from the mobile app, so this stops short of the top band. 14 15 5 6 12
Alert delivery, routing & noise reduction
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
Push, SMS, phone, email, Slack and Teams are all named as delivery channels, with per-person notification rules set by the user or a team manager, acknowledgement straight from the push notification, maintenance mode as an API module, and alert correlation that groups by time or content claiming up to 80 percent less noise; live call routing has its own documentation section and the public status page shows a real voice-delivery incident for India being resolved. Sentry, Grafana, Datadog and CloudWatch all appear by name in the integration list, so my stack reaches a pager. I found no public information on heartbeat monitoring for dead integrations — instead the docs describe auto-disabling an integration after repeated unassigned incidents — nor on delivery receipts, a per-alert notification log, suppression rules or acknowledgement by SMS reply. 9 1 15 6 5 13 8
The IT Operations Manager
Email, SMS, phone calls and iOS and Android push are all documented, with per-person notification rules, acknowledgement from the push notification, alert correlation that groups redundant alerts "by time or content — up to 80% less noise", a team maintenance-mode module, a live call routing section in the documentation, and free domestic call and SMS for the US, Canada and India with per-plan international volumes. For my plant's hard requirements I found no public information on critical alerts overriding do-not-disturb, on acknowledging a voice call by keypad, or on delivery receipts, heartbeat monitoring and suppression rules. 9 1 15 6 5 13
The MSP NOC Lead
Email, SMS, phone calls and iOS/Android push are all documented, with per-person notification rules settable by users or team managers, acknowledgement straight from the push notification, maintenance windows in the API, and live call routing with its own documentation section; AI correlation groups redundant alerts by time or content with a claimed 80% noise reduction. The pricing page names the countries with free domestic call and SMS — US, Canada, India — with international handled separately, and the public status page shows a resolved voice-delivery incident for India, so delivery is being watched publicly. I found no public information on delivery receipts, heartbeat monitoring or suppression rules. 1 6 8 9 13 15
The ICT Risk Officer
Push, SMS, phone, email and chat delivery with per-person notification rules, acknowledgement from the mobile push, routing through a global router and alert rules, team maintenance mode and a documented live call routing section; the AI correlation is stated to group redundant alerts by time or content with up to 80% less noise, and free SMS and voice quotas are broken out for the US, Canada, India and the rest of the world. I found no public information on delivery receipts, heartbeats, do-not-disturb override or named redundant carriers, so delivery reach is claimed rather than evidenced. 9 6 15 5 13 1
The Engineering Manager
Email, SMS, phone calls and iOS and Android push are all documented, with per-person notification rules that team managers can also set, acknowledgement from the push notification, and alert correlation that groups redundant alerts by time or content with a stated claim of up to 80% less noise. Live call routing has its own documentation section and the free SMS and voice volumes are stated per plan for domestic and international use. We found no public information on delivery receipts, a per-alert notification log, heartbeats, or a critical-alert override for do-not-disturb — the one my night rota really needs. 9 15 6 13 1 5
The Skeptic
Email, SMS, phone calls and iOS and Android push are the stated channels, with per-person notification rules, acknowledgement from the push notification, alert routing and live call routing as documentation sections, and alert correlation claimed at "up to 80% less noise" in every plan. No carrier is named for the SMS and voice traffic, and I found no public information on per-channel retries, delivery receipts, do-not-disturb override or heartbeats; the status page does honestly show a real voice-call delivery failure to India. 9 1 15 6 13 8
Incident response, status pages & post-incident review
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
The API covers incidents, roles, notes, tags, responders, priorities, task templates, SLAs, postmortems and analytics, playbooks auto-attach to incidents, and public and private status pages update from the incident itself with subscriber limits stated per plan. The AI side matches my wish list: an incident summariser, AI-drafted postmortems with automated root-cause analysis, and an AI SRE agent, all included in every plan. I found no public information on declaring an incident from Slack with one command or on incident types with their own process; a Zoom access token is stored so a video bridge seems implied but never stated, and the only data-handling statement for the AI features is the trust centre naming AWS Bedrock as the inference provider. 6 1 5 13 1 10
The IT Operations Manager
Playbooks attach automatically to incidents, task templates and postmortems are API modules, AI workflows auto-assign responders, notify them, update tickets and trigger postmortems, and AI incident summaries plus AI-generated postmortems with root-cause analysis are listed as included in every plan, with the trust centre naming AWS Bedrock as the AI inference provider. Public and private status pages with subscriber numbers, stakeholder management, incident roles, priorities, SLA and analytics are all evidenced. I found no public information on declaring incidents from Slack or Teams, a per-incident timeline, incident types with their own process, or follow-up actions tracked into Jira or Linear. 1 6 5 9 13 7
The MSP NOC Lead
Incident roles, priorities, responders, task templates and postmortems are covered in the API and documentation, playbooks attach automatically to incidents, and AI workflows auto-assign, notify responders, update tickets and trigger postmortems, with an AI summariser and root-cause agent in every plan. Public and private status pages exist with subscriber limits per plan, a stakeholder management module is listed, and an analytics section sits behind the MTTA and MTTR claims my monthly customer reports would lean on. I found no public information on declaring incidents from Slack or Teams or on follow-up actions tracked into Jira. 1 5 6 9 13
The ICT Risk Officer
Incident roles, notes, responders, task templates, priorities, SLA and postmortems all exist as API modules, playbooks are automatically attached to incidents, public and private status pages carry per-plan subscriber limits, and the AI suite (summariser, root-cause agent, AI postmortems) sits in every plan, with the trust centre naming AWS Bedrock as the AI inference provider. For a BaFin-supervised house the gaps are concrete: no regulatory or major-incident reporting templates, no documented follow-up tracking into Jira or Linear, and the timeline is only described as activity tracked across the lifecycle — whether it would hold up as evidence for a DORA classification is not shown. 5 6 1 13 7
The Engineering Manager
Incident roles, playbooks attached automatically to incidents, task templates, postmortems, stakeholder management and analytics with MTTA and MTTR reporting are all documented, and the AI side is unusually deep: an incident summariser, AI-generated postmortems with automated root-cause analysis, and an AI SRE agent, all listed as included in every plan. Public and private status pages carry stated subscriber limits of up to 5,000 public subscribers, with the page as a priced add-on on the middle plan. We found no public information on declaring an incident from Slack or Teams or on follow-up actions tracked into Jira, and the AI data handling is evidenced only by the named AWS Bedrock inference subprocessor, with the AI whitepaper behind an NDA. 1 6 5 7 13
The Skeptic
Incidents, incident roles, responders, tags, task templates, SLA, postmortems and analytics are named as API modules, playbooks are claimed to auto-attach to incidents, public and private status pages are sold with subscriber counts, and an AI summarizer, postmortem generator and root-cause agent are claimed in every plan. Much of this is module names and marketing claims: I found no public information on declaring from Slack or Teams, an incident timeline, a video bridge or follow-up actions tracked into Jira, and the AI features carry no model or data-handling description for this product. 1 5 6 9 13
Integrations, API & administration
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
Over a hundred and fifty integrations are claimed with my exact stack named — Sentry, Grafana, Datadog, CloudWatch, plus Jira, Slack and Teams — a documented REST API with Python, Ruby and JavaScript SDKs covering incidents and on-call, a Terraform provider on the feature list, SAML single sign-on with its own documentation, and one-click migration scripts aimed at PagerDuty, Opsgenie and Incident.io. That covers most of what eight product teams need. The administration side is thin at our size: I found no public information on SCIM provisioning, audit logs or bidirectional Jira and ITSM sync, and the only roles documented are owner, admin and user at account level. 4 5 6 13 9
The IT Operations Manager
The integrations page claims 150-plus integrations across ten categories with dozens of named monitoring and chat tools, the REST API is documented with bearer authentication, JavaScript, Ruby and Python SDKs, and modules covering incidents, on-call, routing rules, maintenance windows and analytics, and the pricing page claims full API and Terraform. SAML single sign-on and role-based access control have their own documentation sections, and one-click migration scripts with up to twelve free parallel months target PagerDuty, Opsgenie and Incident.io. I found no public information on SCIM provisioning, audit logs, bidirectional ITSM sync or multi-tenant set-ups, and while the API accepts alerts from any system, I found no public information on connectors for Checkmk or PRTG, the two systems I run. 4 5 6 13
The MSP NOC Lead
More than 150 integrations are claimed with Slack, Teams, Jira, Datadog, Grafana and New Relic named, the REST API is fully documented with JavaScript, Ruby and Python SDKs and modules covering incidents and on-call, and the feature list names SSO and RBAC — with a SAML section in the docs — plus Terraform and an MCP server in every plan. One-click migration scripts from PagerDuty, Opsgenie and Incident.io are offered, with up to 12 months free in parallel while a contract winds down. As a Zabbix and Autotask shop I found no public information on connectors for either, nor on SCIM provisioning, audit logs or multi-tenant separation between my customers. 4 5 6 13
The ICT Risk Officer
More than 150 named integrations including Slack, Teams, Jira, Datadog, Grafana and New Relic, a documented REST API with SDKs and a Postman collection, a Terraform provider, an MCP server, SAML single sign-on and role-based access control, plus one-click migration and a twelve-month parallel-run offer targeting PagerDuty, Opsgenie and Incident.io. I found no public information on SCIM provisioning, bidirectional ITSM sync, or audit logs — the missing audit trail is what I would raise before entering this service in our ICT third-party register. 4 5 6 13 16
The Engineering Manager
Over 150 integrations are claimed with monitoring, chat and ticketing tools named — Datadog, Grafana, New Relic, Jira, Slack and Teams — and the REST API is documented down to on-call, routing-rule and postmortem objects, with JavaScript, Ruby and Python SDKs and single sign-on and role-based access control each having their own documentation. One-click migration scripts from PagerDuty, Opsgenie and Incident.io and an MCP server included in every plan go beyond what I expected. Terraform appears in a feature list rather than its own documentation, and we found no public information on SCIM provisioning, audit logs or bidirectional ticketing sync. 4 5 6 13 16
The Skeptic
Over 150 integrations are claimed with names like Datadog, Grafana, New Relic, Jira, Slack and Teams, a documented REST API with JavaScript, Ruby and Python libraries covers incidents, schedules, routing rules and maintenance mode, documentation sections exist for role-based access control and SAML single sign-on, and Terraform is named in the feature list. Migration is unusually concrete, with automated one-click scripts and an offer to run free for up to 12 months in parallel against PagerDuty, Opsgenie or Incident.io; I found no public information on SCIM provisioning, audit logs or bidirectional ITSM sync. 4 5 6 13 9
Platform reliability, security & compliance
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
There is a public status page with ninety-day uptime per component (notification at 99.98 percent) and visible incident history, and the trust centre lists ISO 27001 and 27018 plus SOC 2 reports — one specifically for the former-Zenduty product — behind an NDA, with 2026 penetration test reports for the sibling products. Hosting is named as AWS US-east and US-west, but that statement sits on a GDPR page last updated in May 2019, and I found no public information on an SLA with credits, encryption in transit and at rest beyond password hashing, multi-region failover, or DORA and NIS2 documentation. The terms also state plainly that the service is not HIPAA compliant and that data liability stays with the customer. 8 7 11 9
The IT Operations Manager
There is a public status page on Atlassian Statuspage showing six components with 90-day uptime figures and a real incident history, including a resolved voice-delivery failure to India, which tells me the pager runs on infrastructure separate from my own network. The trust centre lists ISO 27001:2022 and 27018 certificates, a SOC 2 report covering this product specifically, penetration-test reports for the sibling products, insurance and whitepapers behind an NDA, and data retention is stated per plan. I found no public information on an availability SLA with credits, encryption in transit and at rest, multi-region failover, redundant notification carriers, or DORA and NIS2 documentation, and the terms state plainly that the service is not HIPAA compliant. 8 7 6 9
The MSP NOC Lead
There is a public status page on Atlassian Statuspage showing 90-day component uptime and incident history, a trust centre with an ISO 27001 and 27018 certificate for 2026, SOC 2 reports covering this product, 2026 penetration-test reports under NDA, hosting stated as AWS US-east and US-west, and data retention published per plan. I found no public information on an availability SLA with credits, on encryption in transit and at rest, or on anything for DORA and NIS2, and the terms state plainly that the cloud is not HIPAA compliant. 6 7 8 9 11
The ICT Risk Officer
A public status page shows 90-day uptime per component with the notification service at 99.98% plus a visible incident history, and the trust centre lists ISO 27001:2022 and 27018, a SOC 2 report scoped to this product, penetration tests and insurance behind an NDA. I found no public information on a service-level agreement with credits, encryption in transit and at rest, or any DORA or NIS2 support, and the published penetration tests cover the vendor's other products rather than this one. 8 7 11 6 9
The Engineering Manager
There is a public status page with 90-day component uptime figures (99.98% for the notification service) and visible incident history, and the trust centre lists ISO 27001:2022 and ISO 27018 certificates plus SOC 2 reports including one covering this product line, with penetration-test artifacts and reports available under NDA. Data retention is described per plan. We found no public information on a service-level agreement with credits, multi-region failover or redundant notification carriers, the only encryption statement we found covers password hashing, and the terms state the cloud is not HIPAA compliant. 8 7 6 11 9
The Skeptic
The public status page shows per-component uptime over 90 days with notifications at 99.98% plus real incident history, and the trust centre lists ISO 27001:2022, ISO 27018 and a SOC 2 report covering this product for 2024-2025, though confidential documents require an NDA and the published penetration test reports cover sibling products. I found no public information on an SLA with credits, failover architecture, encryption in transit and at rest, or DORA and NIS2 support, and the terms state plainly the product is not HIPAA compliant. 8 7 11 9
European sovereignty
panel opinion
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
The contracting entity is Xurrent, Inc., headquartered in Santa Barbara with a W-9 on the trust centre, and the only Zenduty hosting statement I found puts the data at AWS US-east and US-west on a page from 2019; the parent trust centre lists EEA regions including Ireland and Germany, so I cannot tell from the captured pages where my incident timelines and phone numbers land today. The subprocessor list names AWS for hosting and AI inference via Bedrock, Google for email, Slack and Pendo — corporate functions — and I found no SMS or voice carrier or alert-delivery processor named, nor a published data processing agreement. A GDPR page and privacy policy exist, but nothing here gives me a European chain I could defend to our works council. 11 7 4 9 10
The IT Operations Manager
The contracting entity is Xurrent, Inc., a US company headquartered in Santa Barbara, and the product's own GDPR page — last updated 28 May 2019 — states data is stored at AWS US-east and US-west zones, while the parent's trust centre lists AWS regions including Ireland and Germany, so the captured pages give different indications for where this product's data sits today. The trust centre does publish a subprocessor list with locations — AWS for hosting and AI inference, Google for email, Slack for internal communication, Pendo in the European Economic Area — and ISO 27001 and SOC 2 are stated. I found no public information on a data processing agreement for this product, an EU contracting entity or representative, or a documented EU hosting option for it. 11 7 9 4
The MSP NOC Lead
The contracting and parent entity is Xurrent, Inc., headquartered in Santa Barbara, and Zenduty's own GDPR page states data is stored at AWS US-east and US-west, so neither entity nor hosting is European — awkward for a Nuremberg MSP answering to customers on GDPR. The parent trust centre does list subprocessors with regions — AWS for hosting and Bedrock AI inference including Ireland and Germany, Google and Slack in the USA, Pendo in the EEA — alongside ISO and SOC certifications. I found no public information on a data processing agreement, and the captured pages give different figures for where Zenduty data sits, with the Zenduty-specific statement sitting on a page last updated 28 May 2019. 7 9 11
The ICT Risk Officer
The contracting entity is Xurrent, Inc. of Santa Barbara, and the vendor's own GDPR page (last updated 28 May 2019) states data is stored at AWS US-east and US-west, while the parent trust centre lists AWS regions including Ireland and Germany — the captured pages give different positions on residency, and a seven-year-old privacy page is itself a finding. A subprocessor list with locations is published (AWS also serving as AI inference via Bedrock, Google and Slack in the US, Pendo in the EEA), but I found no EU hosting option for this product, no EU contracting entity, and no published data processing agreement. 11 9 7
The Engineering Manager
Zenduty is a product of Xurrent, Inc., headquartered in Santa Barbara, and the captured pages give different figures for hosting: the product's own GDPR page (last updated May 2019) states AWS US-east and US-west, while the parent's trust centre lists AWS regions including Ireland and Germany. The trust centre does list subprocessors with their locations — AWS for hosting and AI inference, Google in the USA for email hosting, Slack in the USA, Pendo in the EEA — and ISO 27001 is stated, which is more than many US vendors publish. We found no public information on a data processing agreement, and no EU contracting entity or confirmed EU hosting for this product. 11 7 4 9
The Skeptic
The contracting entity is Xurrent, Inc. with headquarters in Santa Barbara, the captured GDPR page last updated 28 May 2019 puts data at AWS US-east and US west, and the terms claim compliance with United States national laws. The parent's trust centre does list subprocessors with their locations, including AWS regions in Ireland and Germany alongside the US, Google and Slack in the US, and AWS Bedrock named for AI inference, so parts of the chain are visible; I found no public information on an EU contracting entity, EU hosting for this product, or a data processing agreement. 11 7 9
Pricing transparency
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
Starter is $5 per user per month billed yearly ($6 monthly, with the vendor's own words "up to 16% less") and Growth $14 yearly / $16 monthly, each with user, team and integration caps, and the pricing page states free call and SMS volumes per plan — one hundred domestic (US, Canada, India) and twenty-five international per user monthly on Starter, unlimited on Growth and Enterprise — plus USD billing, tax treatment, net-30 terms and refund rules, and a plain statement that features are not gated by plan. The gaps that bite: the status page add-on on Growth carries no price on any page I read, SMS and voice overages are covered only by "T&C apply", and Enterprise is "Talk to Us" — so I cannot compute a full annual cost for sixty responders with a status page from public pages alone. 6 9
The IT Operations Manager
Starter at "$5"/"$6 per user / month" and Growth at "$14"/"$16 per user / month" are public with their user, team, integration and data-retention limits, and notification volumes are stated per plan — "Users × 100/mo" free domestic call and SMS for the US, Canada and India and "Users × 25/mo" international on Starter, "Unlimited" on Growth and Enterprise. Billing is in US dollars, net thirty days, taxes paid by the customer, with proration, late fees and refund terms published. The status-page add-on on Growth carries no public price, overage costs beyond the free volumes are given only as "T&C apply", and Enterprise is "Talk to Us" with a custom proposal, so I cannot compute the full annual cost from public pages alone. 6 9
The MSP NOC Lead
Starter is $5 per user per month billed yearly and $6 monthly with "up to 16% less", Growth is $14 yearly and $16 monthly, both with published user, team, integration and data-retention limits, and call/SMS quotas per plan — domestic US, Canada and India at Users × 100/mo on Starter with international at Users × 25/mo, Unlimited on Growth. The vendor also states features are not gated by plan and that only scale limits, status pages and enterprise support differ, with billing terms covering USD, net 30, pro-rating and refunds. Enterprise is "Talk to Us" with a custom proposal, and I found no public price for the status-page add-on or for SMS and voice beyond the included quotas, nor any word on stakeholder or viewer seats. 6 9
The ICT Risk Officer
Starter and Growth are published at $5 per user per month billed yearly and $6 monthly, and $14 yearly and $16 monthly, with user, team and integration limits, free SMS and voice quotas, status page subscriber caps, a 14-day trial without a credit card, and unusually open billing terms (net thirty, refund windows, taxes borne by the customer). The enterprise tier is "Talk to Us", the status page add-on carries no price, and overage rates beyond the free notification quotas are not stated, so the real annual cost is not computable from public pages alone. 6 9
The Engineering Manager
Starter at $5 per user per month billed yearly ($6 monthly) and Growth at $14 ($16) are public with user, team and integration limits per plan, a statement that features are not gated by plan, and — rare in this market — stated free SMS and voice volumes (users × 100 domestic and × 25 international on Starter, unlimited on Growth). The terms add the currency (US Dollar), taxes paid by the customer, net-30 payment and detailed refund rules. The status page add-on is named but unpriced, the enterprise tier is a sales conversation, we found no public information on overage prices beyond the included volumes, and nothing answers my key question of whether managers who only read along are charged. 6 9
The Skeptic
Starter is "$5 $6 per user / month" for up to 5 users and Growth is "$14 $16 per user / month" for up to 50, each with integration limits, free SMS and voice quotas stated per plan ("Users × 100/mo" domestic and "Users × 25/mo" international on Starter), USD billing, taxes paid by the customer and refund terms spelled out including a ten-day full refund on new subscriptions. The status page is "Available as add-on" with no price on it, Enterprise is "Talk to Us", and beyond the free quotas the SMS and voice terms say "T&C apply", so the full annual cost cannot be computed from public pages alone. 6 9
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 |
Outside the EU
unverified
Why unverified?Statement sits on a GDPR page last updated 28 May 2019, and the parent Xurrent Trust Center lists AWS hosting regions including the EEA, the UK, Switzerland and Australia, so current Zenduty-specific residency may differ. |
0/4 pts | 11 Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Xurrent IMR (Zenduty)
Is Xurrent IMR (Zenduty) European?
No. whats-best.ai classifies Xurrent IMR (Zenduty) as Rest of world.
Where does Xurrent IMR (Zenduty) store data?
Xurrent IMR (Zenduty) stores customer data outside the EU by default, per the vendor’s page captured 7 Nov 2026.
Does Xurrent IMR (Zenduty) have a free plan?
Not stated on the vendor’s pages as of 7 Nov 2026.
What are the best alternatives to Xurrent IMR (Zenduty)?
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: Xurrent IMR (Zenduty) 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 — Legal entity. Not confirmed on the vendor’s own pages as captured.
- Weak sourcing — Hosting location. Statement sits on a GDPR page last updated 28 May 2019, and the parent Xurrent Trust Center lists AWS hosting regions including the EEA, the UK, Switzerland and Australia, so current Zenduty-specific residency may differ.
- 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.
- 87 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
- 29 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
- 17 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
- 13 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
- 7 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
- 7 support 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 hosting 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
- We read 16 of the 22 pages we planned to read for this product; the others could not be captured yet. Everything on this page rests on the pages we read. Know more? Tell us
Sources (16)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage zenduty.com Checked 7 Nov 2026 +3 earlier captures: 6 Nov 2026, 6 Nov 2026, 6 Nov 2026 Details →
- 2 Features page (on-call) www.xurrent.com Checked 7 Nov 2026 Details →
- 3 Features page (alert routing) www.xurrent.com Checked 6 Nov 2026 Details →
- 4 Integrations page zenduty.com Checked 7 Nov 2026 Details →
- 5 API documentation apidocs.zenduty.com Checked 7 Nov 2026 Details →
- 6 Pricing page zenduty.com Checked 7 Nov 2026 Details →
- 7 Trust centre trustcenter.xurrent.com Checked 7 Nov 2026 Details →
- 8 Public status page status.zenduty.com Checked 7 Nov 2026 Details →
- 9 Terms of service (names the operating company) zenduty.com Checked 7 Nov 2026 Details →
- 10 Privacy policy zenduty.com Checked 7 Nov 2026 Details →
- 11 GDPR page zenduty.com Checked 7 Nov 2026 Details →
- 12 On-call schedules, rotations & escalation — found from sitemap zenduty.com Checked 7 Nov 2026 Details →
- 13 Documentation www.xurrent.com Checked 7 Nov 2026 Details →
- 14 Documentation (schedules and rotations) www.xurrent.com Checked 7 Nov 2026 Details →
- 15 Documentation (escalation policies) www.xurrent.com Checked 7 Nov 2026 Details →
- 16 Integrations, API & administration — found from sitemap zenduty.com Checked 7 Nov 2026 Details →