Xurrent IMR (Zenduty)

Rest of world Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 1 of 6 dimensions proven

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by Xurrent, Inc. · zenduty.com

Report an error on this page Is this your product? →

Link to this page

Xurrent IMR (Zenduty): AI-assisted analysis on whats-best.ai Xurrent IMR (Zenduty): AI-assisted analysis on whats-best.ai (dark)

Add ?theme=dark to the image address for dark backgrounds. The badge shows the category and the month of the latest evaluation, and EU-Made where that is the product’s provenance. It never shows a score.

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

Xurrent IMR (Zenduty) alternatives, European ones first →

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

The MSP NOC Lead

Weighted verdict

Leads the network operations centre of a managed service provider in Nuremberg that looks after sixty mid-sized customers, with Zabbix, Microsoft Sentinel and Autotask in the stack. Wants alerts routed by customer and contract hours, tickets opened and closed in the PSA without anyone copying text, a separate on-call rota for the night shift and for each key account, one customer never seeing another's data, and a monthly report per customer on response times.

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

Scored by The MSP NOC Lead

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

On-call schedules, rotations & escalation

How this is scored

Who is on call and what happens when nobody answers: schedules with daily, weekly and custom rotations, layers and follow-the-sun hand-offs across time zones, overrides, swaps and holiday cover, escalation policies with timeouts, repeat and fallback levels, round-robin and team escalation, calendar export and sync, reminders before a shift, on-call reports and hours exported for on-call pay and working-time rules, and a mobile app that shows the shift and lets a responder hand it over.

0 — No schedules or escalation of any kind; alerts go to a fixed list of people.

3 — A simple weekly rotation and one escalation step; overrides, layers, time zones and on-call reports are basic or not described.

5 — Schedules with several rotation types and layers, overrides and swaps from the app, escalation policies with timeouts and several levels, time-zone handling, calendar export, shift reminders, and a report of who was on call when.

8 — Follow-the-sun and multi-team schedules, round-robin and conditional escalation, coverage gaps flagged before they happen, schedules and policies managed as code or by API, and on-call hours exported per person for pay and working-time rules, all documented.

10 — Scheduling a large organisation runs on: every feature above with fairness and fatigue reports, rest-period rules enforced or warned, schedules imported from HR or workforce tools, and every scheduling limit documented per plan.

Report an error

The 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

Report an error

Alert delivery, routing & noise reduction

How this is scored

Whether the alert reaches a human and only the right one: notification by push, SMS, voice call, email and chat, critical alerts that override do-not-disturb on iOS and Android, personal notification rules with retries and fallbacks, acknowledgement by app, SMS reply or keypad, delivery receipts, live call routing for a hotline, routing rules by service, severity, payload and time, deduplication, grouping and correlation of related alerts, suppression and maintenance windows, heartbeats for silent failures, and inbound email and webhook endpoints.

0 — Sends no alerts to people; a dashboard or log viewer only.

3 — Push and email notifications with acknowledgement; SMS, voice, routing rules and noise reduction are basic or not described.

5 — Push, SMS, voice and email with personal notification rules and retries, critical alerts on mobile, acknowledgement from the app or by phone, routing by service and severity, deduplication, and maintenance windows.

8 — Alert grouping or correlation with its logic documented, routing on payload fields and time conditions, delivery receipts and a notification log per alert, live call routing, heartbeat monitoring, suppression rules, and the countries and channels where SMS and voice are delivered stated.

10 — Delivery that is evidenced, not promised: redundant SMS and voice carriers named with automatic failover, delivery statistics published, AI or rule-based noise reduction with measurable results, and every notification limit per plan documented.

Report an error

The 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

Report an error

Incident response, status pages & post-incident review

How this is scored

What happens once the alert is a real incident: declaring an incident from Slack, Microsoft Teams or the app, a dedicated channel and video bridge, incident roles and commander, severities and incident types, runbooks, tasks and automated workflows, stakeholder updates, public and internal status pages with subscribers, a timeline, post-incident reviews and postmortem templates with follow-up actions, analytics such as MTTA and MTTR, and AI features that summarise, suggest causes or draft the review.

0 — No incident record of any kind beyond the alert itself.

3 — An incident list with status and notes; channels, roles, status pages and post-incident reviews are basic or not described.

5 — Incidents declared from chat or the app with severities, a Slack or Teams channel created, incident roles, a timeline, a public status page, stakeholder notifications, postmortem templates, and MTTA and MTTR reports.

8 — Workflows and runbooks that automate the response, incident types with their own process, internal and public status pages with components and subscribers, follow-up actions tracked into Jira or Linear, service catalogue and dependencies, and AI summaries with their data handling described.

10 — A response process a regulated enterprise runs on: every feature above with major-incident and regulatory reporting templates, cross-team analytics and learning reviews, AI features documented with model provider, data handling and an opt-out, and every limit per plan stated.

Report an error

The 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

Report an error

Integrations, API & administration

How this is scored

How the tool fits the stack and the organisation: inbound integrations with monitoring and observability tools (Prometheus, Grafana, Datadog, Zabbix, Checkmk, PRTG, Azure Monitor, CloudWatch, Sentry), outbound integrations with chat, ticketing and ITSM tools (Slack, Microsoft Teams, Jira, ServiceNow, ConnectWise, Autotask), bidirectional sync, a documented REST API, webhooks and a Terraform provider, teams and services, roles and permissions, single sign-on (SAML or OIDC) and SCIM, audit logs, multi-tenant or customer separation for service providers, and migration help from other tools.

0 — No integrations and no administration beyond a single shared account.

3 — Email and webhook intake and a few named integrations; the API, roles and single sign-on are basic or not described.

5 — Dozens of named inbound and outbound integrations including Slack or Teams and Jira, a documented REST API and webhooks, teams with roles, two-factor authentication, single sign-on, and an import path from at least one other tool.

8 — Bidirectional ITSM and ticketing sync, a Terraform provider or configuration as code, SCIM provisioning, granular roles per team, audit logs, service-provider or multi-tenant set-ups, and API coverage of schedules, escalations and incidents documented.

10 — Administration that scales across many teams and customers: every setting reachable by API with parity stated, audit logs exportable to a SIEM, SSO enforced with SCIM, white-label or sub-account management for service providers, and documented migration from the major competitors.

Report an error

The 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

Report an error

Platform reliability, security & compliance

How this is scored

Whether the pager works on the day everything else is down and holds up in an audit: an architecture independent of the customer's own cloud, multi-region or multi-zone hosting with failover, a stated availability or SLA with credits, the vendor's own public status page and incident history, delivery via redundant carriers, encryption in transit and at rest, security certifications (ISO 27001, SOC 2, BSI C5), penetration tests, data retention and deletion, audit trails, and what the vendor documents for DORA, NIS2, HIPAA or other regulated customers.

0 — Nothing on availability, security or how the service is operated.

3 — A claim of high availability or "enterprise security"; the SLA, status page, certifications and architecture are basic or not described.

5 — A public status page, a stated availability or SLA, hosting regions named, encryption in transit and at rest, ISO 27001 or SOC 2 stated, and data retention described.

8 — An SLA with credits published, the incident history public, multi-region failover or redundancy documented, redundant notification carriers named, certifications with their scope, a trust centre with reports on request, and a DORA or NIS2 addendum or mapping offered.

10 — Operation evidenced end to end: failover tested and published, independent audits (ISO 27001, SOC 2 Type II, BSI C5) with reports available, regulatory obligations for financial and critical-infrastructure customers explained in plain language, and the vendor's own post-incident reviews public.

Report an error

The 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

Report an error

European sovereignty

How this is scored

Who the contracting entity and the parent company are, where alerts, incident timelines, chat transcripts, contact data, phone numbers and account data are stored and processed, and who the subprocessors are (hosting, SMS and voice carriers, push services, email delivery, AI summary and transcription models, analytics, support and payment tools). Independently sourced by the sovereignty pipeline. Telephony and push providers needed to reach a responder in another country are part of what the product does and are not counted against it; where the data is stored and who processes it is. A self-hosted edition the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.

0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.

3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.

5 — EU hosting available and an EU contracting entity or EU representative, but parts of the chain (SMS and voice, AI, support, payment) run through non-EU providers without a stated safeguard.

8 — EU hosting on named infrastructure, EU contracting entity, subprocessors listed with their locations, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated — or a self-hosted edition documented that keeps every record on the customer's own servers.

10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor including the AI models and notification carriers, or a self-hosted edition with no call home, data export and deletion documented, and certifications published with their scope rather than implied.

Report an error

The 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

Report an error

Pricing transparency

How this is scored

Whether a buyer can compute the real annual cost from public pages alone: price per user or responder and per plan, whether stakeholders and viewers are free, how many SMS and voice notifications are included and what the rest cost per country, which features (incident response, status pages, AI, live call routing, SSO, audit logs) are add-ons or in higher plans, platform fees, minimum seats, annual versus monthly billing, and the currency and VAT treatment.

0 — No public prices at all; every customer is a sales call.

3 — A starting price per user exists, but notification limits, add-ons and the enterprise tier are unclear.

5 — Plans are public with their price per user and main inclusions, but at least one commonly needed piece (SMS and voice volume, status pages, AI, SSO or the top tier) is unpriced or "contact sales".

8 — Every plan priced publicly with its scaling rule, notification limits and overage prices stated, add-ons priced, stakeholder seats explained, minimum term and billing options and VAT treatment stated.

10 — Complete price computability: annual cost derivable for a given number of responders, stakeholders, notifications and status pages, with every add-on, overage and support fee and the cancellation and data-export terms published.

Report an error

The 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

Report an error

European sovereignty — proven facts

1 of 6 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

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

What we left out

A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.

Sources (16)

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

  1. 1 Vendor homepage zenduty.com Checked 7 Nov 2026 +3 earlier captures: 6 Nov 2026, 6 Nov 2026, 6 Nov 2026 Details →
  2. 2 Features page (on-call) www.xurrent.com Checked 7 Nov 2026 Details →
  3. 3 Features page (alert routing) www.xurrent.com Checked 6 Nov 2026 Details →
  4. 4 Integrations page zenduty.com Checked 7 Nov 2026 Details →
  5. 5 API documentation apidocs.zenduty.com Checked 7 Nov 2026 Details →
  6. 6 Pricing page zenduty.com Checked 7 Nov 2026 Details →
  7. 7 Trust centre trustcenter.xurrent.com Checked 7 Nov 2026 Details →
  8. 8 Public status page status.zenduty.com Checked 7 Nov 2026 Details →
  9. 9 Terms of service (names the operating company) zenduty.com Checked 7 Nov 2026 Details →
  10. 10 Privacy policy zenduty.com Checked 7 Nov 2026 Details →
  11. 11 GDPR page zenduty.com Checked 7 Nov 2026 Details →
  12. 12 On-call schedules, rotations & escalation — found from sitemap zenduty.com Checked 7 Nov 2026 Details →
  13. 13 Documentation www.xurrent.com Checked 7 Nov 2026 Details →
  14. 14 Documentation (schedules and rotations) www.xurrent.com Checked 7 Nov 2026 Details →
  15. 15 Documentation (escalation policies) www.xurrent.com Checked 7 Nov 2026 Details →
  16. 16 Integrations, API & administration — found from sitemap zenduty.com Checked 7 Nov 2026 Details →