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 (13th), AIOps (10th), 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 August 2025, in the IT Alerting and Incident Management category, the mindshare of PagerDuty Operations Cloud is 23.2%, down from 29.1% compared to the previous year. The mindshare of xMatters is 7.4%, down from 8.3% 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

"Alert deduplication and noise reduction for alerts are the major features that I found useful."
"The alerts are immediate in this solution, which allows us to respond to errors quickly."
"The most valuable feature of PagerDuty is its integration with other tools, such as Amazon AWS, to receive notifications or create automatic instances."
"The SMS pages and the mobile application are pretty much the top two features."
"The product has valuable on-call scheduling, escalation, and incident workflow management features."
"PagerDuty's notification process is the most valuable feature."
"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 initial setup is a simple process."
"We have reduced the time it takes to resolve major incidents through xMatters’s conference bridge management solution."
"​The ability to notify teams and monitor those notifications in real-time is valuable. Time-based escalation of notifications helps us resolve issues much more quickly."
"We have not noticed any scalability issues in the two years that we have used the system."
"Allows us to define scenarios that notify only the necessary people when we need to open a conference bridge."
"The UI: It is easily navigable."
"It helped change behavior across the organization to improve accountability."
"We saw the value by being able to import everyone's schedule into one common central repository and have one tool for all the operational teams, or any team for that matter. It gave us the technology to find out who is on call. The incident management of xMatters' integration was another key aspect, where we could say, "You can configure this when a high ticket fires.""
"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."
 

Cons

"PagerDuty can improve the integration with Terraform."
"The solution does not code all alerts correctly so sometimes you get false positives or multiple alerts for the same issue."
"PagerDuty could improve the event orchestration by enhancing features, such as easier condition setup inside the orchestration."
"They could include incident merging and alert grouping features in the product."
"It cannot be integrated with our upgraded Jira system."
"The biggest area for improvement with PagerDuty is noise suppression. There have been a handful of incidents through our use of PagerDuty over the years where one incident may lead to 30 to 50 pages because you're monitoring all these different things, and each thing is an individual page. There should be the ability to set up paging tiers and group correlations between some of the different pages. That is something that would be really valuable. We should be able to say this one page may have a group or a tree of effective other pages that may tier off of it. So, if you see those pages independently, go ahead and alarm, but if you see this plus that, don't do that."
"This solution works best in conjunction with a proper logging system, which can be an additional cost to organizations."
"I would like to see more content in the notification messages; although, that might be a configuration on our end."
"If you want to alter a custom field, you can do so via import/export. But you can't have an unlimited number of custom fields, so in a large environment with a lot of teams, team provisioning becomes more difficult."
"I've asked for the ability to have tags on groups, and for dynamic lists, meaning the ability to pull data from another location and use it in xMatters dynamically. Right now, for example, if I have a form and want to populate a list, it's a manual process. I have to copy and paste the list items."
"Reporting is the weakest point of xMatters. Since xMatters has very limited reporting and only maintains logs of events for a short period of time, we export event and conference logs to our ITSM solution."
"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 could make the product more customizable."
"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."
"I would like some minor UI changes. I believe I filed some enhancement requests with xMatters. For example, in one area, they have some way for you to look at a particular functionality with different sets of reporting UI. However, that same reporting UI is not yet available with some other functionalities. Essentially, in their existing functionality, the xMatters application does an excellent job, but in other functionalities within their UI, they don't have that. On the back-end, they are related. Instead of one click where you can see everything, right now you need to go to different areas to access similar information. It would be nice to have everything in one place. While they have an excellent element A, I am hoping that they could just simply make that feature also available in their element B."
"What I would like it to do is tell me anytime there is a P1 incident, except when the ticket is assigned to this team or when this word is in the summary, but there is no exclusion option. I have been complaining about this for a couple years. At one point, we created a ticket for this with the developers to review. I assume that once enough people complain about it, they will bump it up in priority to work on. However, if not enough people think it is an issue, then they prioritize their work and work on other features and functionality. However, this is something that has been challenging for us because we have needed to find ways to work around it or just deal with it. So, I would love to see an exclusion option."
 

Pricing and Cost Advice

"The price is very high."
"PagerDuty has monthly and yearly licenses available, the costs of which can get quite high if you have a large number of users."
"There is a license needed to use PagerDuty."
"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."
"If you add more people, then you have to pay more, which is always a thing with the SaaS solutions."
"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..."
"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."
"Licensing varies widely, depending on usage. It can be cheap or quite expensive, depending on volume and features."
"The pricing is tiered so we took that into account. If we were to license 10 or 20 people, that would be a certain price. And if we were to license 50 or 100, there would be a little bit of discounting. But the per-user license was right in line with what we were expecting."
"​Pricing is pretty straightforward and listed on their website. I recommend starting small and expanding later.​"
"​You pay for the user, not the number of alerts. Therefore, xMatters provides a better ROI, if you can leverage it for notifications based on alerts from other monitoring tools. ​"
"​I do not think it is worth the value.​"
"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."
"If you are willing to pay for the licensing of it, it is able to scale out.​"
report
Use our free recommendation engine to learn which IT Alerting and Incident Management solutions are best for your needs.
864,053 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
16%
Performing Arts
11%
Financial Services Firm
10%
Manufacturing Company
7%
Computer Software Company
28%
Financial Services Firm
12%
Performing Arts
7%
Manufacturing 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: July 2025.
864,053 professionals have used our research since 2012.