xMatters
Rest of world Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Everbridge, Inc. · www.xmatters.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.
xMatters at a glance
- Vendor
- Everbridge, 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
- Yes, per the vendor’s own page source, captured 6 Nov 2026
- Starting price
- “STARTER (Essentials) Scalable incident response and management for large teams US $15 user / month (up to 25 users)” (vendor’s words) source, captured 6 Nov 2026
- Panel verdict
- The AI panel rates xMatters 3/5, the mean of 6 judges. xMatters scores highest on reliability and compliance, 7 throughout: a public status page with three operational regions, per-plan uptime of 99.90 and 99.95 percent, TLS 1.2 with AES-256, and a trust centre listing ISO 27001, SOC 2, C5, FedRAMP Moderate and DORA with penetration test reports. 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
xMatters scores highest on reliability and compliance, 7 throughout: a public status page with three operational regions, per-plan uptime of 99.90 and 99.95 percent, TLS 1.2 with AES-256, and a trust centre listing ISO 27001, SOC 2, C5, FedRAMP Moderate and DORA with penetration test reports. Incident response, on-call scheduling and integration and administration cluster at 6-7 on documented escalation timelines, a REST API of 38 endpoint families and ServiceNow, Jira and Zendesk integrations; the lower on-call scores reflect judges needing time-zone hand-offs, calendar export and per-person on-call hours for pay and working-time rules. Alerting and routing sits at 6; we found no public information on delivery receipts or per-alert notification logs. Sovereignty is weakest at 2-3: the contracting side sits in the United States under California law and the privacy notice contemplates transferring UK and EEA residents' personal data to US servers; the higher scores credit trust-centre transfer-assessment material, the lower ones rest on hosting location left unconfirmed on the vendor's pages. Pricing transparency holds at 5: three public tiers, a contact-sales Advanced tier, and no public figures for SMS and voice volumes.
Speaks for it
- Per-plan uptime of 99.90 and 99.95 percent published alongside a public status page covering three regions with an incident history
- Escalation timelines with configurable delays, repeat escalations, absences with replacements and coverage-gap identification documented in the help and reachable through a REST API of 38 endpoint families
- A trust centre listing ISO 27001, SOC 2, C5, FedRAMP Moderate and DORA with penetration test reports and completed SIG Lite and CAIQ questionnaires
- Named integrations from ServiceNow, Jira and Zendesk across sixteen categories, plus a webhook that accepts any HTTP POST
- Free, Starter at US $15 per user per month up to 25 users, and Base at US $39 per user per month priced publicly, with a one-year subscription purchasable online
Held against it
- Sovereignty scored 2-3: the contracting side sits in the United States under California law, the privacy notice contemplates transferring UK and EEA residents' personal data to US servers, and hosting location for customer data is not confirmed on the vendor's own pages
- The Advanced tier is contact-sales, and we found no public information on stakeholder license prices, SMS and voice volumes, or per-country prices
- We found no public information on delivery receipts, per-alert notification logs, heartbeats for silent failures, or do-not-disturb override for critical alerts
- The licence terms disclaim any warranty that operation will be uninterrupted or error-free, and we found no public information on service credits
- The captured pages give different figures for the free plan's user limit — up to 5 users on the pricing page, small teams of up to 10 users in the FAQ
Best for
- You run weekly standby rotations and want escalation delays, repeat escalations, absence handling and coverage gaps documented and manageable through the REST API
- You need an audit file with published per-plan uptime, TLS 1.2 and AES-256 encryption details, and C5, DORA and ISO 27001 listings in a public trust centre
- You feed alerts from tools such as ServiceNow, Jira, Zendesk or any service that can send an HTTP POST
Avoid if
- Your data chain requires an EU contracting entity or confirmed EU hosting — the pages show a US entity under California governing law and a privacy notice contemplating transfers of UK and EEA residents' personal data to US servers
- You must compute a full annual cost before a sales conversation — ask the vendor: the public pages we read do not show it
- You need public subscriber-based status pages outside the top tier — status pages sit in Advanced plans and are described as shareable links inside the organization
- Your contract must warrant uninterrupted operation — the licence terms disclaim any warranty that the software will run uninterrupted or error-free
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.5 of 5 |
| European sovereignty | 1 of 5 |
| Pricing transparency | 2.5 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
Shift timelines with escalation delays, weekly rotations, repeat escalations and skip handling for absent members are documented in real depth, the mobile app handles swaps, absences and custom rotations, and the REST API exposes on-call, shifts and temporary absences so schedules can be managed by API. We found no public information on time-zone or follow-the-sun handling, calendar export, shift reminders, or on-call hours exported per person for pay and working-time rules. 14 15 2 8
The IT Operations Manager
The help pages describe exactly what my weekly standby rotation needs: a shift timeline that notifies two people immediately, the next pair after ten minutes and the manager after sixty, with escalations that can repeat on a timer, delays that pause delivery, and inactive members or uncovered absences skipped so the deputy genuinely gets called. Rotations spread the primary-responder duty, shift swaps, absences, custom rotations and coverage-gap fixes are shown, and the REST API carries on-call, shifts and temporary absences so schedules can be managed as code. I found no public information on follow-the-sun hand-offs across time zones, calendar export and sync, or on-call hours exported for pay and working-time rules. 2 8 14 15
The MSP NOC Lead
The documentation shows real escalation engineering: shift timelines with configurable delays, repeat escalations, weekly rotations, temporary absences with replacements, and a worked example where the manager is reached after sixty minutes total. Coverage gaps can be identified and fixed, shifts swapped from the app, per-group view/notify/modify rights restricted, and escalations and rotations are configurable for shifts of up to two hundred members. We found no public information on time-zone or follow-the-sun handling, calendar export, shift reminders, or exportable on-call hours for pay and working-time rules, which my night-shift and key-account rotas would need proven. 2 14 15 21
The ICT Risk Officer
Shift schedules, rotations and escalation timelines are documented in real depth — configurable delays, repeat escalations, absences with replacements, shift swaps, coverage-gap identification and mobile shift management — and schedules, shifts and temporary absences are reachable through the REST API. As a German employer I would still need time-zone hand-offs, calendar export and per-person on-call hours exported for pay and working-time rules; we found no public information on those. 2 8 14 15
The Engineering Manager
Rotations, escalation timelines with time-based delays and repeat escalations, shift swaps, absences and coverage-gap detection are documented, with a mobile app for managing shifts and API endpoints covering on-call and shifts. That covers the mechanics of a follow-the-sun rota, but we found no public information on time-zone hand-offs, calendar export, shift reminders, or on-call hours exported per person for payroll and rest-period rules — the pieces my works council agreement needs. 2 3 8 14 15
The Skeptic
Rotations, escalation timelines with delays and repeats, temporary absences, shift swaps and coverage-gap identification are documented in the help, and the REST API covers shifts and on-call summaries, with the 200-member shift limit and the licence dependence of rotations and escalations stated openly. We found no public information on calendar export, shift reminders, follow-the-sun hand-offs, or on-call hours exported per person for pay and working-time rules. 2 8 14 15
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
Correlation of related alerts, redundant-alert blocking, adjustable thresholds, flood control and suppression are all documented, live call routing lines are priced per plan, and the supported countries for SMS and voice are published. We found no public information on critical alerts overriding do-not-disturb, personal notification rules with retries and fallbacks, delivery receipts, or heartbeats for silent failures. 5 9 16 17
The IT Operations Manager
SMS and voice are offered with a published list of supported countries, live call routing includes one line even on the base plan, and the mobile apps acknowledge alerts through configurable response options that can auto-connect a conference bridge — though I found no public information on acknowledging a voice call by keypad, which is how my night crew works. Noise reduction is real and documented: adjustable rules for what triggers a notification, how urgent each event is and who gets notified, filtering and suppression settings, flood control, and automatic correlation of related alerts. I found no public information on delivery receipts, do-not-disturb override for critical alerts, heartbeat monitoring for silent failures, or the included SMS and voice volumes. 5 9 16 17 21
The MSP NOC Lead
Routing by team, role, skillset, schedule and location with adjustable thresholds for triggers, urgency and recipients is documented, and the noise-reduction story is concrete: automatic correlation of related alerts, Event Flood Control, filtering and suppression settings, and documented duplicate-notification handling. Live call routing is priced per plan with one line on the entry plan and three on the top plan, and the vendor states global SMS and voice coverage with a country list. We found no public information on delivery receipts or a per-alert notification log, heartbeat monitoring for silent failures, or critical alerts overriding do-not-disturb on the phone. 5 9 16 17 21
The ICT Risk Officer
Delivery spans SMS and voice with a supported-countries list, mobile apps with configurable response options and comments, and routing by team, role, skillset and priority, backed by duplicate blocking, automatic correlation of related alerts, suppression, flood control and live call routing priced per plan. For an alerting chain I can defend in an incident review, we found no public information on delivery receipts, a per-alert notification log, heartbeat monitoring, or critical alerts overriding do-not-disturb. 5 9 16 17 21
The Engineering Manager
Push via the iOS and Android apps, SMS and voice with global coverage and a published list of supported countries, device preferences, acknowledgement with configurable response options, and documented threshold filtering, correlation, suppression and event flood control. We found no public information on delivery receipts, a per-alert notification log, heartbeat monitoring, or redundant carriers, which is what would let me trust delivery on a bad night. 5 9 16 17 21
The Skeptic
The mobile apps for Android and iOS deliver notifications with one-tap acknowledgement and comments, global SMS and voice coverage is claimed with a supported-country list referenced, suppression, flood control and automatic correlation of related alerts are documented, and live call routing lines are stated per plan. We found no public information on delivery receipts, per-alert notification logs, retries, heartbeats for silent failures, critical alerts overriding do-not-disturb, or the carriers that actually place the calls — so delivery is promised rather than evidenced. 5 9 16 17 21
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
An Incident Console with a live timeline, resolver roles, severity and time-to-respond metrics, Slack or Teams bridges on the fly, exportable post-incident reports and post-incident analytics covers most of how I run incidents, and Flow Designer with predefined runbooks automates escalation; an AI Scribe Agent transcribes Teams incident meetings. Status pages sit in Advanced plans with no subscriber mechanism or components described, and we found no public information on follow-up actions tracked into Jira or on AI data handling. 3 19 1 7 4 18
The IT Operations Manager
Incidents are initiated with severity and status, worked from an Incident Console with a live timeline, resolvers assigned and dismissed, and Slack, Microsoft Teams, Zoom or the built-in bridge added on the fly; guided runbooks and hundreds of pre-built workflows automate the response, and analytics track severity, response time and team performance with exportable post-incident reports. An AI agent guides responders and a Scribe Agent transcribes Teams incident meetings, with services and their dependencies feeding it. Status pages live in the Advanced tier and are described as shareable links inside the organization; I found no public information on public subscriber-based pages, page components, or follow-up actions tracked into a ticketing system. 1 3 7 18 19
The MSP NOC Lead
An incident console with severities, resolver roles, a live timeline with real-time collaboration, bulk status updates and an exportable post-incident report is documented, plus status pages with a permanent shareable link and stakeholder opt-in subscriptions, which covers the monthly reporting I owe each customer. Predefined runbooks, guided remediation workflows, incident-type properties usable in reporting and exports, service dependencies, and an AI scribe that transcribes Teams incident meetings take this well past the basics. The status pages are described for stakeholders inside the organisation rather than clearly public pages with subscribers, and we found no public information on follow-up actions tracked into Jira beyond alert-driven issue creation. 1 3 7 18 19
The ICT Risk Officer
The incident process is well documented: a detailed live timeline with real-time collaboration, incident types with typed properties, resolver roles, exportable post-incident reports with review and edit on the top plan, severity/time-to-respond/team-performance metrics, automation via built-in workflows and runbooks, and an AI incident agent plus a Microsoft Teams transcription scribe with an AI usage guide in the trust centre. For a BaFin reporting file, we found no public information on public status-page subscribers or components, follow-up actions tracked into ticketing, or regulatory reporting templates. 1 3 7 10 18 19
The Engineering Manager
The pages document an incident console with severities, roles and a live timeline, collaboration channels added on the fly, runbook-driven workflows, incident-type properties, service dependencies, an exportable post-incident report, status pages in the top plan, and an AI scribe transcribing Teams meetings with an AI usage guide in the trust centre. We found no public information on status-page components and subscribers or follow-up actions tracked into ticketing, so the review loop is thinner than the response itself. 1 3 4 7 18 19
The Skeptic
Incidents carry severities, resolver roles, a live timeline, bulk updates, an exportable post-incident report and metrics including time to respond, while predefined runbooks, hundreds of workflow steps, service dependencies in the API and an AI scribe and incident agent extend the process. Status pages exist but only in the Advanced plan and without any evidence of subscriber management, and the AI features are named without their data handling described beyond an AI usage guide in the trust centre. 1 3 7 18 19
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
The REST API is properly documented with dozens of endpoint objects covering on-call, shifts, incidents and audits, Slack, Teams, Jira, ServiceNow and more are named integrations, and groups carry granular per-group permissions with audit endpoints behind them. We found no public information on a Terraform provider, SCIM provisioning, or multi-tenant setups for service providers, which is what I would need to run this as code across eight teams. 8 6 20 15 21
The IT Operations Manager
The REST API exposes 38 endpoint objects — on-call, shifts, incidents, services, subscriptions, audits — with OAuth, API keys and rate limits, and the webhook integration accepts an HTTP POST from any tool, which is how I would feed Checkmk and PRTG. Slack, Microsoft Teams, Jira, ServiceNow, Zendesk, New Relic and Dynatrace are named across sixteen integration categories, an SSO/SAML category and email MFA exist, roles run from group supervisor down to per-group restrictions on who may view, notify or modify, and audit records have dedicated endpoints. I found no public information on SCIM provisioning, a Terraform provider, or a documented migration path from another tool. 6 7 8 15 20
The MSP NOC Lead
Sixteen integration categories with named ServiceNow, Jira, Slack, Teams and Zendesk connectors, inbound and outbound integrations with JavaScript transformation scripts, a webhook that accepts any HTTP POST, and a REST API spanning thirty-eight object types including on-call, shifts, incidents, roles and audits, so my Zabbix and Autotask could at least be wired in through the generic webhook. Roles are granular down to per-group restrictions with custom roles, SSO/SAML is an integration category, and email MFA for native login is documented. We found no public information on SCIM provisioning, a Terraform provider, bidirectional PSA or ticketing sync, or service-provider multi-tenant separation, which is the part my sixty customers would hinge on. 6 8 15 20 21
The ICT Risk Officer
A documented REST API with 38 endpoint objects — groups, shifts, on-call, incidents, people and audit records — using OAuth, API-key and basic authentication, webhooks and a no-code flow builder, plus named ServiceNow, Jira, Zendesk, Slack and Microsoft integrations across 16 categories, SAML single sign-on and email MFA, covers most of a regulated IT estate's needs. Custom roles, group supervisors and per-group access restrictions are documented, and audit records are reachable through dedicated endpoints. We found no public information on SCIM provisioning, a Terraform provider, explicit bidirectional ITSM synchronisation or multi-tenant separation for service providers. 6 7 8 15 20
The Engineering Manager
A documented REST API with endpoints for on-call, shifts, incidents, groups, people and audits, webhook intake and outbound calls to any internet API, a browser script editor, group-level roles, and SAML single sign-on listed among sixteen integration categories alongside named ServiceNow, Jira, Zendesk, Slack and Teams integrations. We found no public information on SCIM provisioning, a Terraform provider, bidirectional ticketing sync, or multi-tenant set-ups for service providers. 6 7 8 15 20
The Skeptic
A REST API with thirty-eight endpoint families including shifts, on-call, incidents and audits, a webhook builder with transformation scripts, SAML single sign-on, email MFA, per-group permission restrictions and named integrations from ServiceNow and Jira to Zendesk are all documented. We found no public information on SCIM provisioning, a Terraform provider, explicit bidirectional ITSM sync, multi-tenant set-ups for service providers, or a documented migration path from named competitors. 6 8 15 20 21
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
A public status page with incident history and three operational regions, per-plan availability of 99.9 and 99.95 percent, AES-256 at rest with Google Cloud key management, TLS 1.2 or higher in transit, and a trust centre with penetration test reports, SOC 2, ISO 27001 and a DORA listing is a strong audit file. We found no public information on SLA credits, a documented multi-region failover architecture, or redundant notification carriers. 11 9 23 10 1 8
The IT Operations Manager
Uptime is stated per plan at 99.90% and 99.95% with 24x7 support, and the public status page shows North America, EMEA and Asia-Pacific operational with an incident history and subscription to updates — an independent platform I can watch when my own network is the thing that is down. Encryption is TLS 1.2 or higher in transit and AES-256 at rest under Google Cloud key management with rotating master keys, runtime data is held for 30 days with history per plan, and the Everbridge trust centre publishes penetration test reports, SOC 2 and business-continuity documents alongside ISO 27001, SOC 2, C5, FedRAMP and DORA listings. I found no public information on SLA credits, documented multi-region failover or named redundant notification carriers; the license terms state the software is not warranted to run uninterrupted or error-free. 8 9 10 11 22 23
The MSP NOC Lead
Published SLAs of 99.90 and 99.95 percent depending on plan, a public status page with an incident history and subscribe-to-updates showing three regions operational, AES-256 at rest with rotating master keys under GCP KMS and TLS 1.2 or higher in transit, plus a trust centre listing ISO 27001 with a Statement of Applicability, SOC 2 and 3, BSI C5, HIPAA and even DORA, with penetration test reports and completed SIG Lite and CAIQ questionnaires available. The C5 reference alone matters for our German public-sector customers. We found no public information on SLA credits, tested multi-region failover, or redundant notification carriers. 9 10 11 23
The ICT Risk Officer
Uptime is published per plan (99.90% and 99.95% with 24x7 support on the paid tiers), a public status page covers three regions with an incident history, and the trust centre lists ISO 27001, SOC 2, C5, ISO 22301, penetration test reports and architecture documents on request, with DORA named in the compliance list and AES-256 at rest under GCP KMS and TLS 1.2+ in transit documented. What I cannot yet put in the ICT register: we found no public information on service credits in the captured licence terms, on multi-region failover, or on named redundant notification carriers, and the licence terms expressly disclaim any warranty that operation will be uninterrupted or error-free. 1 9 10 11 22 23
The Engineering Manager
A public status page showing regional operations and an incident history, published availability of 99.90% and 99.95% depending on plan, TLS 1.2 or higher and AES-256 encryption, retention described, and a trust centre carrying ISO 27001 with a statement of applicability, SOC 2, C5, DORA and penetration-test reports on request. We found no public information on service credits for missed availability, multi-region failover, or redundant notification carriers. 8 9 10 11 23
The Skeptic
A public status page covering three regions with an incident history and subscription option, per-plan uptime percentages of 99.90 and 99.95 percent, TLS 1.2 and higher with AES-256 under rotating master keys, and a trust centre listing C5, ISO 27001, SOC 2 and FedRAMP Moderate with penetration test reports. The uptime figures come with no published credits, we found no public information on multi-region failover or redundant notification carriers, and the software licence itself disclaims any warranty of uninterrupted operation. 9 10 11 22 23
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 parent and contracting side is Everbridge, a US company, and the privacy notice states that EEA personal data may be transferred to servers in the United States. The trust centre publishes technical and organisational measures and points to a subprocessor list, but the captured pages show no subprocessor names or locations, no confirmed data processing agreement, and hosting location for the service is not stated on the vendor's own pages we captured. 13 10 12 22
The IT Operations Manager
The contracting entity is American — xMatters, inc. of San Ramon, California, under Everbridge, Inc., with California governing law — and the privacy notice states that personal data of UK and EEA residents may be transferred to servers in the United States, with Google Analytics among the website providers and the EU-US Data Privacy Framework listed in the certification set. Hosting location for customer data is not confirmed on the vendor's own pages beyond Google Cloud key management, a subprocessor list is available at the trust centre but its contents are not shown, and I found no public information on a data processing agreement or an EU hosting option. As far as the evidence goes, this is a US chain for my plants' alert and contact data. 10 13 22 23
The MSP NOC Lead
The contracting side is clearly American: xMatters is an Everbridge company, the privacy notice names Everbridge, Inc., correspondence goes to San Ramon, California, and the agreement is governed by California law. The same notice states that EEA residents' personal data may be transferred to servers in the United States, and we found no public information on where alert, incident and contact data is hosted, on a data processing agreement, or on named subprocessors beyond a pointer to a subprocessor list in the trust centre. For my customers in Bavaria that is not a chain I can currently evidence, though the GDPR claims, EU-US DPF listing and the data-subject request process show more than nothing. 10 12 13 22
The ICT Risk Officer
The contracting entity and parent are US-based (Everbridge, Inc. of Vienna, Virginia, with correspondence to xMatters, inc. in San Ramon, California), and the privacy notice expressly contemplates transferring EEA residents' personal data to servers in the United States; hosting location for alerts, timelines and contact data is not confirmed on the captured vendor pages, although EMEA appears as an operational region on the status page. A subprocessor list, technical and organisational measures and transfer-assessment material exist behind the trust centre, but we found no public information on a published data processing agreement, an EU contracting entity or representative, or subprocessor locations — as a DORA-regulated buyer I would need all three contractually. 10 11 12 13 22 23
The Engineering Manager
The captured pages show a United States parent and contracting entity, California governing law for the service agreement, Google Cloud key management, and a privacy notice stating that EEA residents' personal data may be transferred to servers in the United States. We found no public information confirming EU hosting, an EU contracting entity or representative, or the identities and locations behind the subprocessor list the trust centre offers — for a Hamburg works council this is the deciding dimension. 10 12 13 22 23
The Skeptic
The contracting entity is American — Everbridge, Inc. of Vienna, Virginia, with California governing law — and the privacy notice states that UK and EEA residents' personal data may be transferred to servers located in the United States. A subprocessor list and technical measures exist behind the trust centre, but we found no public information confirming EU hosting, a published data processing agreement, or the named locations of the subprocessors that carry alerts, timelines and contact data. 10 12 13 22
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
Free, Starter at US $15 user / month and Base at US $39 user / month are published with a one-year subscription term and tax treatment, but the Advanced tier is contact-us, status pages live in that tier, and stakeholder licenses, SMS and voice volumes and overage prices are not published, so I cannot compute a real annual cost for my team. 9 18 22
The IT Operations Manager
A free plan at US $0 and the Starter and Base plans at US $15 and US $39 per user per month are public, with a one-year subscription purchasable online — though the pricing pages give different figures for the free plan's user limit — and the base plan already includes one live-call-routing line. What I cannot compute: the Advanced tier is "Contact Us", status pages and editable post-incident reports sit in that tier, notification volumes and per-country SMS or voice costs are not stated, "more available" lines and non-production instances carry no published price, and the terms say fees exclude taxes. For my five-person standby with phone-based alerting, the real annual number needs a sales call. 9 18 19 22
The MSP NOC Lead
Free, Starter at US $15 per user per month up to 25 users, and Base at US $39 per user per month are public, with usable per-plan inclusions such as live call routing lines, attachment limits, non-production instances, support hours and the SLA, though the captured pages give different figures for the free plan's user limit, five on the plan card and ten in the FAQ. The Advanced tier is contact-us only and status pages sit inside it, and we found no public information on SMS and voice volumes or per-country prices, stakeholder license prices, or the cost of additional call routing lines. Tax treatment, with the customer paying taxes excluding those on xMatters' net income or property, and annual-in-advance billing are stated in the agreement. 9 18 22
The ICT Risk Officer
Free, Starter (US $15 per user per month, up to 25 users) and Base (US $39 per user per month) plans are public with inclusions such as live call routing lines, non-production instances, support hours and uptime per tier, a user definition, one-year online billing, and tax treatment in the licence terms (fees exclude VAT and similar taxes, which the customer pays). The Advanced tier is contact-sales, stakeholder licenses are available but we found no price for them, we found no published SMS and voice volumes or overage prices, status pages sit in the Advanced tier, and the captured pages give different figures for the free plan's user limit (up to 5 users on the pricing page, small teams of up to 10 users in the FAQ). 9 18 22
The Engineering Manager
Three tiers are priced publicly — US $0 for the free plan, US $15 user / month up to 25 users, US $39 user / month for the Standard plan — with a one-year subscription, live call routing lines and non-production instances stated per plan, though the captured pages give different figures for the free plan's user limit. The top tier is contact-sales, stakeholder licences are named but unpriced, and we found no public information on SMS and voice volumes or overage prices, so I cannot compute what my read-along managers would actually cost. 9 18 22
The Skeptic
Prices are public for three tiers — US $0 up to 5 users, US $15 user / month up to 25 users, US $39 user / month — with per-plan uptime, live call routing lines, attachment limits and non-production instances stated, and the agreement says taxes are the customer's and support bills annually in advance. But the Advanced tier is contact-sales, we found no public information on included SMS and voice volumes or per-country prices, and stakeholder licenses are 'available' without a price; the captured pages also give different figures for the free plan's user limit. 9 18 22
European sovereignty — proven facts
0 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 | — | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined | — | uncited Report an error |
| Hosting options |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | 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 xMatters
Is xMatters European?
No. whats-best.ai classifies xMatters as Rest of world.
Where does xMatters store data?
Not stated on the vendor’s pages as of 6 Nov 2026.
Does xMatters have a free plan?
Yes. xMatters has a free plan, per the vendor’s page captured 6 Nov 2026.
What are the best alternatives to xMatters?
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: xMatters 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 — Hosting options. 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.
- 11 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
- 11 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
- 10 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
- 5 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
- 4 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
- 2 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
- 2 hosting 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 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us
Sources (23)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.xmatters.com Checked 6 Nov 2026 Details →
- 2 Features page (on-call management) www.xmatters.com Checked 6 Nov 2026 Details →
- 3 Features page (incident response) www.xmatters.com Checked 6 Nov 2026 Details →
- 4 Features page (workflow automation) www.xmatters.com Checked 6 Nov 2026 Details →
- 5 Features page (event management) www.xmatters.com Checked 6 Nov 2026 Details →
- 6 Integrations page www.xmatters.com Checked 6 Nov 2026 Details →
- 7 Documentation help.xmatters.com Checked 6 Nov 2026 Details →
- 8 API documentation help.xmatters.com Checked 6 Nov 2026 Details →
- 9 Pricing page www.xmatters.com Checked 6 Nov 2026 Details →
- 10 Trust centre (Everbridge) trust.everbridge.com Checked 6 Nov 2026 Details →
- 11 Public status page status.xmatters.com Checked 6 Nov 2026 Details →
- 12 About page www.xmatters.com Checked 6 Nov 2026 Details →
- 13 Privacy policy (names the parent company) www.everbridge.com Checked 6 Nov 2026 Details →
- 14 On-call schedules, rotations & escalation — found from sitemap help.xmatters.com Checked 6 Nov 2026 Details →
- 15 On-call schedules, rotations & escalation — found from sitemap help.xmatters.com Checked 6 Nov 2026 Details →
- 16 Alert delivery, routing & noise reduction — found from sitemap help.xmatters.com Checked 6 Nov 2026 Details →
- 17 Alert delivery, routing & noise reduction — found from sitemap help.xmatters.com Checked 6 Nov 2026 Details →
- 18 Incident response, status pages & post-incident review — found from sitemap help.xmatters.com Checked 6 Nov 2026 Details →
- 19 Incident response, status pages & post-incident review — found from sitemap help.xmatters.com Checked 6 Nov 2026 Details →
- 20 Integrations, API & administration — found from sitemap help.xmatters.com Checked 6 Nov 2026 Details →
- 21 Integrations, API & administration — found from sitemap www.xmatters.com Checked 6 Nov 2026 Details →
- 22 Platform reliability, security & compliance — found from sitemap www.xmatters.com Checked 6 Nov 2026 Details →
- 23 Platform reliability, security & compliance — found from sitemap www.xmatters.com Checked 6 Nov 2026 Details →