This piece is for teams weighing up the choice between these three tools (or a combination). We’ll be focusing on these platforms as incident management/ incident response tools, but of course, you may plug PagerDuty or xMatters into ServiceNow or run ServiceNow as your standalone.
For SREs looking for a pager service or ServiceNow users wondering if they need something else in the stack, this is for you.
Incident management tools at a glance
| PagerDuty | xMatters | ServiceNow | |
|---|---|---|---|
| Product scope | Two routes: Professional plan, or bundled PD Reliability Platform | Standalone tool inside Everbridge; more bundled per tier | Assembled from ITSM and ITOM modules |
| Alert ingestion | 750+ integrations; ServiceNow integration not on Professional | 200+ integrations; ServiceNow ticketing on every tier | No ticketing integration needed; ITOM licence required |
| Noise reduction | Key-based deduplication; grouping via AIOps add-on or platform | Rule-based flood control included from Free | ML correlation; needs ITOM; best with a maintained CMDB |
| On-call and notifications | Unlimited phone and SMS on Professional; included on platform | Phone and SMS capped below Advanced | No phone or SMS until Notify configured |
| Response automation | Platform: remediation actions within AI allowance; Runbook Automation extra | Flow Designer on every tier; can reach behind firewall | Creates records across ServiceNow products; admins build rules |
| Pricing | $21 per user per month, or from $2,800/year (platform) | $15–$39 per user per month; Advanced by quote | Quote only, across ITSM and ITOM |
| Compliance | SOC 2, ISO 27001, FedRAMP Low | SOC 2, ISO 27001 | SOC 2, ISO 27001, PCI DSS, HITRUST |
| Data residency | US or EU, fixed at sign-up | North America, Europe including London, Australia | UK, EU, Australia; Singapore per partners |
| Setup and ownership | Self-serve entry; Expert Services required from Essential | Self-serve up to Base | Quote-led; admin roles and Notify setup |
| AI assistance | Included on platform tiers; add-on on Professional | Incident Agent on Advanced; AI suggestions from Free | Built into every packaging tier |
When to choose PagerDuty, xMatters or ServiceNow
Choose PagerDuty if your engineering team wants to own its paging. It’s self-serve, it has the largest published integration catalogue, and phone and SMS are unlimited on Professional and included on the platform. It now sells two routes: the Professional plan at $21 per user per month, with noise reduction, AI and scripted remediation as add-ons, or its new flagship PD Reliability Platform, which bundles noise reduction, AI and built-in remediation actions, within usage allowances, for an annual fee. It’s hosted in the US or EU only.
xMatters is the better-value choice if you need what PagerDuty’s Professional plan sells separately. Noise reduction and automation are in the base price, and ServiceNow ticketing works on every tier. It’s also the simplest route to Australian hosting, and has a London data centre. However, check the phone and SMS caps: teams that rely on calls at night will probably need Advanced, which is priced by quote.
ServiceNow makes sense if you already run ServiceNow ITSM, with a platform team and a maintained CMDB. Incidents, problems and changes then live on a single platform, and it has the broadest compliance set of the three. You pay for that in quote-based pricing across two product lines, and in setup that sits with ServiceNow admin roles rather than the people being paged.
Product scope: incident response tool or single platform?
What all three do
At the core, all three do the same job: take an alert from a monitoring tool, page the right person and track the incident until it’s resolved.
Where they differ
What comes in the box. PagerDuty now sells two things. Its Incident Management plans, Free and Professional, are a standalone incident response product covering the entire incident lifecycle. Professional includes post-incident reviews and a status page for up to 250 subscribers; machine-learning noise reduction (AIOps), generative AI (PagerDuty Advance), script-based remediation (Runbook Automation) and live call routing are add-ons.
Its new flagship, the PD Reliability Platform, bundles most of those add-ons into four tiers, each with an annual platform fee and usage allowances. PagerDuty’s main pricing page presents the Incident Management plans as options for teams testing PagerDuty. Its older Business and Enterprise plans are still listed on its incident management pricing page, but not on the main one.
xMatters is also a standalone product, owned by Everbridge, whose main business is critical event management. It bundles more into each tier: noise reduction, workflow automation and a service catalog are included from the free plan; status pages need Advanced.
Whether it’s a product or a platform. ServiceNow isn’t an incident response product in itself. You assemble the response layer from On-Call Scheduling, an application within ITSM, and Event Management, part of the separately licensed ITOM product. The payoff is that incidents are ITSM records, linked to problems, changes and the CMDB.
Verdict
This dimension sets up every decision that follows:
- PagerDuty: two products now: a narrow entry plan you extend with add-ons, or a bundled platform you commit to annually
- xMatters: a focused tool with more included up front; good if you’d otherwise buy PagerDuty’s add-ons
- ServiceNow: only worth it if you already run ServiceNow; otherwise you’re adopting a platform to get a pager
Alert ingestion and integrations
What all three do
When a monitoring tool such as Datadog or CloudWatch spots a problem, it sends an alert to your incident tool. PagerDuty calls this an ‘event’ sent to a ‘service’. xMatters calls it a ‘signal’ received by a ‘workflow’. ServiceNow calls it an ‘event’ received by Event Management. The names differ; the mechanism doesn’t.
All three offer pre-built integrations: ready-made connectors for specific monitoring tools. You pick the tool from a list, paste a key or URL into it, and alerts start flowing without anyone writing code. For tools without a connector, all three accept alerts through an API or by email.
Where they differ
Catalogue size. PagerDuty lists 750+ integrations, xMatters 200+, and ServiceNow publishes no count. Don’t read much into the numbers. Vendors count integrations differently, and a bigger catalogue only matters if it covers a tool you run, so check your existing systems against each list.
What connecting costs you. PagerDuty doesn’t charge more however many systems you monitor. xMatters charges a user licence for each integration that authenticates as a system account. ServiceNow’s alert ingestion sits in ITOM, a separate licence from the ITSM product that runs on-call.
Getting alerts into your ticketing system. If you use ServiceNow for tickets, PagerDuty and xMatters both need their ServiceNow integration. PagerDuty includes it on every Reliability Platform tier but not on Professional, and two-way sync of custom fields, with related workflow actions, needs Plus or Ultimate; Business and Enterprise include it too, where PagerDuty still sells them. xMatters includes it on every tier, free plan included. ServiceNow doesn’t need one: an alert becomes an incident in the same system.
Verdict
Not much in it on ingestion itself. For most teams, any of the three will connect to the monitoring tools they already use. The differences are in what surrounds it:
- PagerDuty: the largest published catalogue, so the likeliest to cover niche monitoring tools, but ServiceNow users need a platform tier (or Business, where PagerDuty still sells it)
- xMatters: the cheapest route into ServiceNow ticketing; count integration accounts in your licence numbers
- ServiceNow: nothing to integrate, but only because you’re paying for ITOM on top of ITSM
Alert noise reduction
What all three do
When something breaks, monitoring tools rarely send one alert; a failing database can produce hundreds in minutes. All three merge repeat alerts about the same problem so your engineer is paged once, not 200 times. That’s deduplication, and all three include it.
Where they differ
How each decides two alerts are the same. PagerDuty deduplicates on a matching key, usually set by the monitoring tool; email integrations can match on the subject line instead. The key only works within a single integration: the same key sent through two integrations creates two incidents.
xMatters relies on rate. By default, once alerts from the same integration to the same recipients arrive at more than four a minute, the rest are suppressed; you can edit that rule or write custom rules that match on other properties. ServiceNow first converts events from different tools into one standard format, so it can compare them.
Grouping alerts that are related but not identical. This is the harder problem. A database failure also sets off alerts in every application that depends on it, and deduplication alone won’t join them up.
On Professional, PagerDuty sells grouping and suppression as its AIOps add-on, from $699 a month billed annually or $799 billed monthly; on every Reliability Platform tier they’re included, up to the tier’s allowance of events (5,000 on Starter), with credit packs beyond that. xMatters groups similar incidents on its Base and Advanced plans.
ServiceNow correlates alerts with machine learning. With a CMDB (its database of your systems, recorded as configuration items, and how they connect), it links each alert to the affected system and that system’s history; without one, it groups alerts by their tags. Operators can correct the groupings, and the model learns from the corrections.
Verdict
Basic deduplication is equal across all three. The difference is what smarter grouping costs and what it depends on:
- PagerDuty: fine on Professional if your monitoring tools send consistent keys; smarter grouping means buying AIOps or moving to the platform
- xMatters: good-enough grouping from Base, with no add-on to buy; the right pick for most teams that don’t want another line on the invoice
- ServiceNow: correlation tied to your CMDB and incident history, but only as good as that CMDB; a stale CMDB gives you confident correlations pointing at the wrong systems
On-call, escalation and notification delivery
What all three do
A schedule decides who’s on call. When an incident comes in, that person is notified, and if they don’t respond within a set time, the page moves to the next person in line. All three work this way, and all three can reach people by mobile push, SMS, voice call and chat tools.
Where they differ
What starts the escalation. In PagerDuty and xMatters, the incoming alert or incident starts it.
ServiceNow adds a step. A trigger rule watches a record, typically an incident, and starts escalation when that record meets its conditions. Shift administrators create these rules for all groups. Shift managers can create them for their own groups, but only as workflows, which ServiceNow no longer shows to new users from the Zurich release onward. So an alert has to become an incident, and the incident has to match a rule, before anyone is paged. That’s more to configure and more to get wrong.
Phone and SMS. This is the biggest practical difference in the section. PagerDuty includes unlimited SMS and phone calls on Professional. Its main pricing page lists SMS and phone as included on every Reliability Platform tier without stating a cap, and the free plan gets 100 a month.
xMatters caps them per user per month below its top tier. The free plan gets none; Starter gets 50 SMS and ten voice calls; Base gets 100 SMS and 20 voice calls; only Advanced is unlimited. ServiceNow can’t text or call anyone until you’ve configured its Notify service with at least one phone number and an escalation workflow.
Tier limits. PagerDuty’s free plan allows one schedule and one escalation policy, and round-robin assignment needs a platform tier, or Business where PagerDuty still sells it. xMatters’ escalations and rotations work only for shifts of 200 members or fewer, which affects only very large teams.
Verdict
The escalation model is identical across all three. What differs is how reliably the page reaches a sleeping engineer:
- PagerDuty: the least to think about; calls and texts just work, with no cap on Professional
- xMatters: fine if your team works from push and chat notifications; if you rely on phone calls, ten a month on Starter runs out in one bad week
- ServiceNow: capable once it’s built, but two configuration steps stand between an alert and a phone call, and each one is a place for paging to fail silently
Response automation
What all three do
All three offer workflow automation: once an incident exists, they can pull in extra responders, post updates, open a chat channel and, with the right setup, run a fix.
Where they differ
What starts it. PagerDuty’s Incident Workflows start from the incident type, from conditions such as priority P1, manually or through the API. Professional gets one workflow, started by incident type. xMatters’ Flow Designer flows start from a monitoring signal, an email, a web request, a form, or activity on an alert such as a response or an escalation. ServiceNow’s alert management rules act on alerts that match criteria you set.
Whether it can fix things, and at what cost. On Professional, running scripts against your infrastructure needs Runbook Automation, an add-on. Every Reliability Platform tier includes Premium Workflow Actions, which run diagnostics and remediation, such as restarting services or redeploying containers, against the tier’s AI-action allowance. Full Runbook Automation remains an add-on on every tier, and conditionals, loops and delays in workflows need Plus or Ultimate.
xMatters includes Flow Designer on every tier, free plan included. Flows can mix built-in steps with custom JavaScript, and they can run on an agent inside your own network, so they reach systems behind the firewall. Playbooks need Base or Advanced.
In ServiceNow, your team can build remediation actions, such as retrieving a log file, freeing disk space or restarting a service, that run automatically or are started from the alert.
What it can touch. PagerDuty and xMatters automate the incident and the systems around it. ServiceNow’s rules can also create records across its products: incidents, change requests, security incidents, even customer service cases. However, your administrators build each rule and flow themselves.
Verdict
This is one of the real dividing lines:
- PagerDuty: strong on coordinating people; remediation is an add-on on Professional, and the platform includes basic remediation actions, metered as AI actions
- xMatters: the most automation for the money, with automated remediation and behind-the-firewall workflows on every tier, free plan included
- ServiceNow: the most reach, because it can raise records across the ServiceNow estate, but every automation is a build project for your platform team
Pricing model
What all three do
Little in common here. PagerDuty’s Professional plan and xMatters both charge per user per month, and both count anyone on a schedule or receiving notifications as a user. PagerDuty’s Reliability Platform charges an annual platform fee that includes set allowances of seats (stakeholders included), events and AI actions, with credit packs for more. ServiceNow doesn’t publish prices.
Where they differ
List price. PagerDuty has a free plan for up to five users, and Professional costs $21 per user per month on annual billing ($25 monthly). Reliability Platform tiers cost $2,800 a year (Starter, ten seats), $12,000 (Essential, 20 seats), $48,000 (Plus, 40 seats) or a custom price (Ultimate), each with allowances of events and AI actions and credit packs to top up. Payment is upfront, and Essential and above carry a required Expert Services add-on with no published price.
xMatters has a free plan (for up to five or ten users; its pricing page gives both), then Starter at $15 for up to 25 users, Base at $39 and Advanced by quote. Paid plans are annual subscriptions.
What the price includes. On Professional, PagerDuty sells noise reduction (from $699 a month billed annually, $799 billed monthly), AI (from $415 a month), Runbook Automation and live call routing as add-ons. The platform tiers include noise reduction, AI and built-in remediation actions, within their event and AI-action allowances; Runbook Automation is still an add-on. xMatters includes noise reduction and automation on every tier, and stakeholder licences on Base and Advanced.
For 20 responders on annual billing, PagerDuty Professional costs $420 a month before add-ons, PagerDuty Essential $12,000 a year (equivalent to $1,000 a month), with all 20 seats taken by responders, plus its required Expert Services, and xMatters Base $780 with noise reduction and automation included. That said, xMatters’ phone and SMS caps can push you to Advanced, which has no published price.
How you buy. ServiceNow is quote only. Its products come in three tiers, Foundation, Advanced and Prime, defined by AI capability, with entitlements set by your account team. For incident response you’re buying at least ITSM, for on-call, and ITOM, for alert handling.
Verdict
Hard to compare like for like, because each vendor puts the line between base price and extra in a different place:
- PagerDuty: Professional is cheap until you add what most teams want; the platform bundles it for an annual fee, with usage allowances and, from Essential, required services
- xMatters: better value for most teams once you count what’s included, unless phone call volume forces you onto Advanced
- ServiceNow: no way to compare until the quote arrives; if you already license ITSM and ITOM, the marginal cost may be small
Compliance attestations
What all three do
All three hold SOC 2 Type II and ISO 27001. For most commercial buyers, that’s what a security review asks for, so there’s not much in it.
Where they differ
The differences only matter if you’re in a regulated sector.
PCI DSS. ServiceNow lists PCI DSS for its platform. PagerDuty claims it only for its hosting providers’ data centres, not for PagerDuty itself, and xMatters doesn’t list it.
FedRAMP. PagerDuty holds FedRAMP Low, which covers low-impact federal data only. ServiceNow’s FedRAMP High covers only its Government Community Cloud, not the commercial platform.
Everbridge holds FedRAMP Moderate, but its authorisation names the Everbridge Suite, and we found nothing extending it to xMatters. A green tick on Everbridge’s trust centre isn’t an xMatters authorisation.
Healthcare. HIPAA has no formal certification; HHS doesn’t recognise private Security Rule ‘certifications’. xMatters says a third-party audit confirmed it meets HIPAA security requirements, and Everbridge’s trust centre has a HIPAA entry, but it links to a privacy notice rather than an attestation. ServiceNow holds HITRUST. PagerDuty lists neither.
Verdict
Equal for most buyers; different only in regulated sectors:
- PagerDuty: covers standard commercial reviews, and is the only one of the three with a commercial FedRAMP authorisation, albeit at Low
- xMatters: covers standard commercial reviews; ask for the HIPAA audit if you’re in healthcare
- ServiceNow: the strongest set, and the only one to list PCI DSS for its own platform, which matters if your incident data touches card environments
Data residency
What all three do
All three can host your data in the US or the EU.
Where they differ
UK and Australia. xMatters’ Europe region includes London alongside Germany, with both labelled ‘European Union’, and doesn’t say whether UK data can be pinned to London. Its Asia-Pacific region is hosted in Sydney and Melbourne.
ServiceNow runs a UK-sovereign data centre pair in London and Newport, and its own documentation places site pairs in Asia and Australia too. Its SPP AU service offers strictly in-country Australian hosting for government and regulated industries, subject to ServiceNow approval. Community and partner sources name Singapore, Japan and India.
PagerDuty offers no UK or Australian region.
Flexibility. PagerDuty sets your region at sign-up. Changing it later means a paid migration by its Professional Services team, where possible, or rebuilding in a new account without your incident history. Some data, including logs and support data, may be processed outside the chosen region. Its regions page says all pricing plans are available in both regions, but it predates the Reliability Platform, so confirm a platform tier is offered in the EU region before buying.
Verdict
Equal if US or EU hosting is enough; decisive if it isn’t:
- PagerDuty: fine for US and EU data, but choose your region carefully, because changing it later is costly
- xMatters: the simplest route to Australian hosting, and to a London data centre, though its European region also spans Germany, so confirm where UK data replicates
- ServiceNow: the widest footprint of the three, including a UK-sovereign pair and an Australian in-country option open to regulated industries
Setup and ownership
What all three do
Whichever you choose, someone has to connect your monitoring tools, build the schedules and design the escalation paths. None of the three does that for you.
Where they differ
How you buy and start. PagerDuty is self-serve at the entry level: a free plan for up to five users, or a 14-day trial with no credit card, then card payment online. The Reliability Platform is paid upfront, and Essential and above require an Expert Services add-on. xMatters is self-serve up to Base: you can upgrade online by card, but Advanced, or any change once you’re on a paid plan, goes through xMatters. ServiceNow is bought by quote.
Who owns the setup. With PagerDuty and xMatters, the team being paged builds and changes its own schedules and escalation policies in the app.
ServiceNow splits the work across roles. Shift administrators set up contact methods and create trigger rules for all groups. Shift managers can create them for their own groups, but only as workflows, which ServiceNow no longer shows to new users from the Zurich release onward. SMS and voice also need Notify configured on the instance.
Verdict
This is the sharpest dividing line in the comparison:
- PagerDuty: on Professional, the on-call team can be live the same day and owns every change after that; the platform adds an upfront commitment and, from Essential, required services
- xMatters: the same, until you need Advanced
- ServiceNow: shift managers run their rosters, but what starts an escalation, how people are contacted and whether SMS works all sit with ServiceNow admin roles and instance configuration; fine if that team is responsive, a bottleneck if it isn’t
AI assistance and how it’s licensed
What all three do
All three now offer generative AI that summarises incidents and helps responders decide what to do next.
Where they differ
How you pay. PagerDuty includes its AI on every Reliability Platform tier, within each tier’s allowance of AI actions, with credit packs for more. On Professional it’s an add-on, from $415 a month on an annual commitment, though PagerDuty’s incident management pricing page also lists a one-time allowance of 1,000 AI actions.
xMatters puts its conversational Incident Agent only on the Advanced plan, which is priced by quote, with no separate metering published. Lighter AI features are lower down: root-cause and change-correlation suggestions on every tier, and suggested resolvers from Base. ServiceNow builds AI into its packaging: every product tier is defined by AI capability, and all tiers include incident summarisation.
How far it acts. PagerDuty’s SRE Agent can diagnose a problem and run remediation, with a human approving each action. Its other agents transcribe incident calls, resolve on-call coverage conflicts and surface operational insights.
xMatters’ Incident Agent suggests resolvers, summarises, recommends next steps and drafts stakeholder updates. Its own documentation tells users to verify the recommendations before acting.
ServiceNow’s Now Assist for ITOM rewrites hard-to-read alerts in plain language, with a probable cause and suggested fixes. Custom AI agents and its ‘autonomous AI workforce’ are Prime only.
Verdict
Three vendors, three commercial models: platform bundling or add-on, top-tier bundling and a packaging restructure:
- PagerDuty: an acting agent, included on platform tiers and an add-on on Professional; know which task you want automated before you pay for either
- xMatters: a conversational assistant only on Advanced, though AI root-cause and change suggestions are on every tier
- ServiceNow: AI comes with whatever tier you buy; the question is whether your tier covers the capability you actually want
How we can help
At Just After Midnight, we help teams support complex applications 24/7, 365. This could mean you hand over to our 24/7 support team from any one of these platforms or that we jump in to ensure you make the best decision on the tool that fits your use case.
If you think we can help, just get in touch.
