Try our new research platform with insights from 80,000+ expert users

PagerDuty Operations Cloud vs xMatters comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Jan 2, 2025

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

PagerDuty Operations Cloud
Ranking in IT Alerting and Incident Management
1st
Average Rating
8.8
Reviews Sentiment
7.3
Number of Reviews
37
Ranking in other categories
Process Automation (14th), AIOps (9th), Critical Event Management (CEM) (1st)
xMatters
Ranking in IT Alerting and Incident Management
10th
Average Rating
8.8
Reviews Sentiment
7.5
Number of Reviews
31
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of May 2025, in the IT Alerting and Incident Management category, the mindshare of PagerDuty Operations Cloud is 21.4%, down from 30.0% compared to the previous year. The mindshare of xMatters is 6.1%, down from 9.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
IT Alerting and Incident Management
 

Featured Reviews

JeremyEmmett - PeerSpot reviewer
Centralized alert management with customizable routing and superior scheduling
Everything can always be better. Operations are somewhat limited by their integration package. For example, integrating with Jira was problematic until they updated to a better plug-in. The ability to build customized modules would be advantageous, allowing organizations to define their own integration modules. It would be useful to have a way to define all configurations in code that is similar to how Terraform operates.
Dean-Robinson - PeerSpot reviewer
A versatile solution with excellent logging capabilities that reduced our time to resolve
The reporting functionality could be improved, though I know that's something xMatters, inc. is working on. For example, sometimes I need to go into the platform and find users who aren't in groups that have been created recently, haven't logged in and so on. Previously, this was hard work, but they added loads of filters, making it more accessible. Still, the ability to create custom-designated reports that I could run and schedule would be fantastic for me. It would be good if they keep improving the reporting functionality, as it can be somewhat restrictive sometimes. There are a couple of improvements that xMatters could make to the incident hub, where we can manage high-priority incidents. More sharing capability between collaborating incident managers would be good to see, including the ability to whiteboard. That would allow them to share and sketch out ideas while looking for a solution. Those two features are essential, and that's why we want to use the solution in conjunction with Everbridge because xMatters doesn't have them.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The most valuable feature is the phone app that allows us to send notifications without the additional fees when sending by SMS or phone calls."
"PagerDuty helps you bifurcate teams and redirect alerts to specific teams"
"The solution's most valuable features are that it adds each alert as a service, has good scheduling capabilities, and includes the ability to write logic based on texts."
"The most valuable features of PagerDuty are customization, access, policies, and different rules regarding the path of escalation. Additionally, it's easy to use and create overrides. For example, if you all are on a call for one week each, but somebody wants to go on PTO, the team needs to swap shifts in PagerDuty. This is easy to do by creating overrides to switch up the set schedules. It's very user-friendly in that aspect. It works well for monitoring and alerting."
"The alerts are immediate in this solution, which allows us to respond to errors quickly."
"Alert deduplication and noise reduction for alerts are the major features that I found useful."
"The initial setup is a simple process."
"PagerDuty let us set up rosters based on our shifts. We could assign a hierarchy for how the calls should be escalated and the number of times the call will be transferred between people before it is answered. It makes it easy to access an agent via mobile phone."
"It has been easy to use and very reliable."
"It has improved our time to respond. Prior to the use of xMatters, it might take hours or even a day to get someone involved on a problem. Now, it's down to minutes."
"Support has been great. They responded very quickly to all the support cases that I have submitted.​"
"Being able to split the week however we want is definitely most valuable. We can create shifts and also see other teams' schedules. It is a very easy search to do these things."
"The automated callouts, without a doubt, are most valuable. They have been a huge gain for our company. Previous to xMatters, there was no real management of the on-call resources or rotas. So, having that centralized and automated has been a huge gain."
"One of the things that really attracted me is in workflows, you can write your own custom steps in JavaScript. You are not restricted to the steps that they provide. If you can write it in JavaScript, you can pretty much do anything. It gives me flexibility in ways that other platforms don't. For example, the online dashboard system we use is not a widely used one, but they have an API. So, I'm able to write the JavaScript steps to do things like check if a system's in the maintenance window or create an instant on the dashboard or change the status of an instant. I'm not dependent on the dashboard provider or xMatters creating steps for me."
"Workflows and messaging are most valuable. Workflows are very useful. They are important for consolidating information or stopping duplication from happening. We put all the information into xMatters and then the workflow will push the same information in the correct format directly through to other applications that our end users frequently use, such as Slack, email, and Workplace."
"We're able to communicate better with specific groups or offices. We didn't have that capability or granularity before. It has helped in that regard."
 

Cons

"It is difficult to send underlying trace files or statuses using PagerDuty."
"Something that needs to be improved, is adding multilingual support."
"The On-Call Teams feature could be better in terms of levels of conditions related to which team or member should get the responsibility of handling a matter or incident."
"I would like the UI to be more intuitive. I would like to be able to group or color-code the discoveries. When you create a system, you have a listing of all the different configurations. You can list them by teams, but some additional color coding would be helpful. I would break it down by incident controls. In other words, it should be broken down it into response teams and engineering divisions."
"I would like to see more content in the notification messages; although, that might be a configuration on our end."
"Because of the way you have to structure the rosters, if an engineer has to go on leave (or something), you can't just go in and reassign/take this person out of all of the different rosters that they're in. You have to go into each of the rosters and take them out. There might be a roster for business hours, after hours rotation, and monitoring deployments. Each time we need to take an engineer out of the pool, e.g., if they're sick or on leave, then we have to go and touch all of those rosters, updating and replacing them. Whereas, if we could just take the person out and have it automatically fill in the rostering, then that would make life a lot easier for managing it."
"PagerDuty's webhooks need some improvement."
"I am not a direct end user of PagerDuty. It's hard to consider its shortcomings in that sense."
"In terms of intuitiveness and flexibility of xMatters when it comes to customizing on-call schedules, rotations, and escalations, for me, as an IT professional, setting it up isn't that big of a deal, but I understand that some people struggle with it because when you get wrapped up into it. You can get lost. It's not super complex, but it's complicated enough to the point where you can say that you should have done it another way. The shift part can be confusing for some people. In that respect, one of the shortcomings my team has found is when we have to add another person, such as a new hire, to xMatters, we can't add them to a group within xMatters without having to put them on a shift. If we put them in a group, they have to be on-call. We can create their account, and then they're just out there in limbo until their team says, "You have to be on this shift." One piece of feedback for xMatters is to figure out how to have manageable groups so that they're contactable from xMatters. They do not necessarily have to be on a shift right from the start or at all for that matter."
"We cannot go back in time to check out the previous schedules that we had. We can only see them moving forward. I wish we were able to go back and see the previous schedules that we had. That's the biggest thing."
"They recently released an incident module that allows users, or at least teams, to track major incidents and other things, and you can send out communication via that one webpage. You can engage on-call teams and communicate to stakeholders as well, but one thing that is missing there is a group chat. If there is a group chat on the same webpage that all of the support teams could use, it would be a one-stop shop that all of the major incident managers would use as their product to manage a major incident. Without that, at the moment, they are mainly referring to teams and then adding data into xMatters as and when they can."
"When you are not using the conference bridge from xMatters and you are using an external one, it is a little bit hard to get the person whom xMatters calls to jump directly to the external bridge. They need to hang up the phone and then get to the email to get the URL so that they can jump on the bridge. There is no direct connection from xMatters to that external bridge, but I understand that part of the business."
"On-call management scheduling is difficult."
"One of the main reasons why we don't use xMatters for monitoring and alerting is that it doesn't use the rota to call the person who's on-call. It doesn't look up the rota to find out who's on-call and then contacts that person directly. I am not sure if this has changed now, but the last time we checked, this functionality wasn't there. This is one of the main improvements. We're happy with the rest of it."
"Beyond the typical grouping, xMatters has what is referred to as dynamic teams. Dynamic teams are criteria for setting up and targeting a group of people that meet specific criteria. The bad thing about this setup is that you cannot alter those criteria through the typical xMatters import/export process. The attributes that create the criteria for dynamic teams can only be altered via the Web UI. So, if you want to create a new dynamic team in a mature xMatters environment (one that is already populated with hundreds of users), and you want to add, say, 100 users to that dynamic team, you have to do it manually."
"We would like to see the ability to support custom devices. We have a lot of users who use Slack, which is another tool for communication. xMatters currently does not support Slack as a communication method. It can't send events to Slack and respond to them."
 

Pricing and Cost Advice

"The cost is based on the package you select."
"They're very good in pricing compared to the competitors in the area. I would rate them a five out of five in terms of pricing."
"The cost is quite high. But if you want to get a full-featured application and you have a big team..."
"Licensing costs are around $700 a month, and the only additional costs, are phone costs in some instances."
"If we wanted phone calls or additional SMSs, we would have to pitch up for those. They give us so many per month per user, then we have to pay extra if it goes over that."
"There is a license needed to use PagerDuty."
"PagerDuty has monthly and yearly licenses available, the costs of which can get quite high if you have a large number of users."
"The pricing may be about $1,000 per user."
"Then, in pricing, you are limited on your number of SMS messages that you can send a month and the licensing cost annually."
"I know roughly what we pay per year. For what we use it for and what its purpose is, it is very valuable."
"It seemed comparable or more reasonable than some of the other solutions, at least when we evaluated it. There are no extra costs in addition to the standard licensing fees. Its cost is good, given the breadth of features provided by xMatters."
"It is worth the cost. You need to know the number of users that are going to use it, which is usually pretty easy to calculate. It's on a per-user license."
"It feels like good value in the sense that the service is excellent. The people above me who look at such things have renewed it a couple of times, and I think they would have thought whether it was good value, whether it was wildly overpriced, or whether there were better and cheaper alternatives. So, from that perspective, the pricing is fair and proper."
"We're currently per license. We're paying around $44,000 per year for 80 full users and 300 standard users. For a new implementation, we also need to pay for an expert."
"​Pricing is pretty straightforward and listed on their website. I recommend starting small and expanding later.​"
"The cost depends very much on the company's size and usage. We're a very high use case compared to many companies, so we had to consider licensing costs carefully. If we added all our users, that would be 30,000, and that's no good; we wouldn't have been able to afford it. For example, we had to put in customization to sync across on-call users. For the license per user, the price is very reasonable and comparable to ServiceNow when factoring in everything that needs to get up and running."
report
Use our free recommendation engine to learn which IT Alerting and Incident Management solutions are best for your needs.
850,747 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
21%
Financial Services Firm
12%
Manufacturing Company
7%
Healthcare Company
6%
Computer Software Company
35%
Financial Services Firm
18%
Manufacturing Company
6%
Healthcare Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about PagerDuty?
The product easily integrates with other solutions.
What is your experience regarding pricing and costs for PagerDuty?
The solution was expensive, but if all its features were utilized, it was considered worth the cost. The tier-based pricing model was cumbersome, and there was a desire for a service-based catalog ...
What needs improvement with PagerDuty?
Everything can always be better. Operations are somewhat limited by their integration package. For example, integrating with Jira was problematic until they updated to a better plug-in. The ability...
Ask a question
Earn 20 points
 

Also Known As

No data available
xMatters IT Management
 

Overview

 

Sample Customers

40% of the Fortune 100 TrustPagerDuty. Customers include: Slack, Intuit, Zendesk, Panasonic, Pinterest, Airbnb, eHarmony, McKesson, Comcast
Over 2.7 million users trust xMatters daily at successful startups and global giants including athenahealth, BMC Software, Box, Credit Suisse, Danske Bank, Experian, NVIDIA, ViaSat and Vodafone. xMatters is headquartered in San Ramon, California and has offices worldwide.  Visit our website to see how business like yours found solutions with xMatters.
Find out what your peers are saying about PagerDuty Operations Cloud vs. xMatters and other solutions. Updated: April 2025.
850,747 professionals have used our research since 2012.