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 (9th), Critical Event Management (CEM) (1st)
xMatters
Ranking in IT Alerting and Incident Management
9th
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 April 2025, in the IT Alerting and Incident Management category, the mindshare of PagerDuty Operations Cloud is 22.1%, down from 30.1% compared to the previous year. The mindshare of xMatters is 6.0%, down from 9.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

"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."
"The most valuable feature is definitely the flexibility of the schedule. The mobile app is quite also good for what we do: for receiving alerts, acknowledging, assigning, adding new responders. It has rich features for our needs."
"PagerDuty's best features are the dedicated application that allows me to reach my engineers immediately and the ability to directly assign specific tasks to individuals and have them report back."
"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."
"A cool feature is that it helps us to understand the flow of the alert. If the alert was coming to the current on-call and he didn't catch the call or didn't notice it for any reason, it starts being escalated automatically, according to the escalation schedule, or to other teammates. You can see the flow very easily on your phone or via the website, if you want to do a post-mortem."
"It reduces the amount of white noise. If something comes through, then it will alert somebody. However, if it's a bit of white noise that comes through at night, then it gets dealt with the next day. Everything is visible to everybody. It's not just a single person getting an SMS, then going, "Oh, I'm not going to worry about that." The visibility to everybody on the team is one of the great things about it because it reduces the white noise."
"Alert deduplication and noise reduction for alerts are the major features that I found useful."
"The most valuable feature of PagerDuty is its integration with other tools, such as Amazon AWS, to receive notifications or create automatic instances."
"We have not noticed any scalability issues in the two years that we have used the system."
"Made it very easy to implement our roster of people who receive alarms with the REST API."
"We're able to point all of our alerting tools at xMatters and have it route alerts to the right people at the right time. We're able to generate major instant notifications for product outages, get all of our people on the bridge at the same time, and include information from our monitoring tools with that. So everyone is speaking the same language and seeing the same information. We're able to route those notifications not only to people, but also to other tools like Slack channels, where everyone can get in and collaborate."
"The customer service is quite responsive. They are quick to answer your calls or emails."
"​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."
"For us, their biggest feature is event alerting and the retention of those events. This way, if something goes wrong, we can provide a report of everything that was sent out and everything that was captured."
"Allows us to define scenarios that notify only the necessary people when we need to open a conference bridge."
"Support has been great. They responded very quickly to all the support cases that I have submitted.​"
 

Cons

"PagerDuty could improve the event orchestration by enhancing features, such as easier condition setup inside the orchestration."
"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 am not a direct end user of PagerDuty. It's hard to consider its shortcomings in that sense."
"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."
"The product can be improved by including out-of-the-box integration with other standard tools used in our fields such as Confluence, and Jira."
"PagerDuty should be integrated with other tools, so it can import the IT roster automatically. Our other rules continue to work once they're configured, but the roster must be added manually."
"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."
"The solution's analytics are okay. I don't think the features, at this point, give you a lot of insights. We have actually been trying to get insights from it but it hasn't really given us a lot of extra points to explore. We were looking at the number of alerts to see where many of the alerts were coming from. We never managed to get many insights on this."
"We would like to see the integration between our ITSM solution and xMatters."
"I would like to see some more user templates. There are roles — administrator, user, etc. — but it would be nice to create a user template that restricted what people assigned that role could do."
"While the documentation is good, the knowledge base - the collection of user supported community forums - is a little weak compared to some of the other products I've used. If I have a problem that I can't find the answer to in the documentation, there are very few places to go after that, because the user base, the community forums, are not strong for me to find someone who's had the same issue as me, and find out what the answer to their problem was. That's somewhat of a weak point."
"Additional built-in integrations with other applications would be an area of improvement."
"The data validation and verification need to be enhanced so that when data is changed, it reviews it in an automated manner and catches all of the anomalies."
"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."
"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."
"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."
 

Pricing and Cost Advice

"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."
"The price is very high."
"The pricing may be about $1,000 per user."
"The solution is paid on a monthly basis and represents about 1% of the platform's budget."
"Licensing costs are around $700 a month, and the only additional costs, are phone costs in some instances."
"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 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."
"​I do not think it is worth the value.​"
"xMatters is pricey, but you have to consider what a critical incident costs your organization."
"I am not really privy to how much my client is paying for this service. They just tell me the number of licenses that they have. Every time that I say, "I need extra licenses to make sure that all Level 1 and 2s have their own xMatters account," they keep telling me that it is too expensive. If the only purpose is to call people, it doesn't justify the cost of paying more than the number of licenses that they already have."
"Then, in pricing, you are limited on your number of SMS messages that you can send a month and the licensing cost annually."
"I'm not really involved with the cost standpoint. I've only heard rumors of how much it costs, and if it costs what I think it costs, its cost is very high as compared to a lot of other tools that we're using here. It seems on the higher end from a cost standpoint."
"Licensing varies widely, depending on usage. It can be cheap or quite expensive, depending on volume and features."
"xMatters shortens the time to resolution, so the amount saved in potential lost revenue and productivity has justified the cost for our organization.​"
report
Use our free recommendation engine to learn which IT Alerting and Incident Management solutions are best for your needs.
845,040 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
21%
Financial Services Firm
13%
Manufacturing Company
7%
Healthcare Company
6%
Computer Software Company
32%
Financial Services Firm
21%
Manufacturing Company
7%
Healthcare Company
5%
 

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: March 2025.
845,040 professionals have used our research since 2012.