No more typing reviews! Try our Samantha, our new voice AI agent.

Rootly vs xMatters comparison

Why PeerSpot?
 

Comparison Buyer's Guide

Executive Summary

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

Rootly
Ranking in IT Alerting and Incident Management
11th
Average Rating
8.0
Reviews Sentiment
5.6
Number of Reviews
4
Ranking in other categories
No ranking in other categories
xMatters
Ranking in IT Alerting and Incident Management
12th
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 September 2026, in the IT Alerting and Incident Management category, the mindshare of Rootly is 2.8%, down from 9.8% compared to the previous year. The mindshare of xMatters is 4.2%, down from 6.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
IT Alerting and Incident Management Mindshare Distribution
ProductMindshare (%)
Rootly2.8%
xMatters4.2%
Other93.0%
IT Alerting and Incident Management
 

Featured Reviews

Luis Vasconcelos - PeerSpot reviewer
System Architect at CI&T
Centralized incident workflows have improved visibility and streamlined communication across teams
Rootly helps me handle those issues by using a predefined template to define roles inside the workflow and utilizing a basic flow, which is very short in its lifecycle. The most powerful feature of Rootly is its visibility; we can create a dashboard and integrate with Slack and Jira, for example, automating many steps in the follow-up process, which helps to centralize all communications around issues. The best features Rootly offers include communication capabilities, particularly the integration with Slack, which stands out for me because it allows for very clean and direct communication with all clients and even with the resolution area. The Slack integration helps my team by creating a specific resolution group and an automation channel inside Slack once an incident is opened in Rootly, ensuring that everyone knows when a new incident arises. It is not just a notification; we create a group where all the relevant people can help solve the issue quickly. The workflow capability of Rootly to create flows is another key feature for our operation, allowing us to establish specific rules for incidents in Jira or manage the metrics we need during the incident lifecycle, effectively automating many manual processes. Rootly has positively impacted my organization, and we have measured its impact by analyzing the number of incidents we handle over a period. With the strategic approach of putting everyone in a Slack group to resolve incidents, we have reduced the percentage of incidents created in a month by thirty percent during the first three months of using Rootly. Other positive outcomes include time savings and improvements in collaboration; the groups inside Slack enable people to communicate across different areas and work directly with client operations, creating synergy and a strong integration between teams.
Dean-Robinson - PeerSpot reviewer
Sr. Developer at a media company with 10,001+ employees
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

"Rootly has positively impacted our organization because, in comparison to ObsGenie, the tool we used before Rootly, it is much more user-friendly, including the user interface and the whole approach to alerting and routing these alerts."
"Rootly has positively impacted my organization by saving time with manually adding timelines, as they are already built in when timelines are added in Slack through integration."
"With the strategic approach of putting everyone in a Slack group to resolve incidents, we have reduced the percentage of incidents created in a month by thirty percent during the first three months of using Rootly."
"Rootly has positively impacted my organization by allowing us to receive the on-call alerts successfully, whereas before Rootly, we had issues missing alerts."
"That automation is the critical aspect of xMatters. Without those workflows, then we would have a system that maintains an on-call schedule in Excel. So xMatters provides the notification workflow and ensures you're notifying the right person at the right time."
"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 haven't evaluated any product recently, but from what I can tell, looking around online, what xMatters has that others don't have are the custom forms. That's the big differentiator at the moment because that's something that we heavily use."
"xMatters is helpful for getting the right on-call resources. That is a key factor. It is also very user-friendly, and just a little documentation helps you to understand things such as how on-calls are configured, how groups are configured, and how users update their on-call devices."
"We can have a critical incident bridge spun up within 10 minutes, and all of the necessary teams join within 15 minutes, so it's cut our response time by 75%."
"The feature that I have found to be most valuable is the entire alert notification configuration, having an external system to trigger events that will process the alert to the supporting team. If a system is down, then you need to get it attention. Sometimes, it cannot wait until the next day. Therefore, how xMatters provides this type of integration is critical."
"The on-call schedule that they have for groups is amazing in terms of how it works and how it triggers. You don't need to do anything. You just upload the users, and you have the calendar of the schedules. It is amazing how it works and how easy it is to work with this feature."
 

Cons

"The integration process could be easier, perhaps with the addition of AI to facilitate smoother integrations with other applications, especially since those who manage integrations often need technical knowledge about web services and single sign-on processes, which can be challenging for non-technical users."
"Regarding Rootly's AI capabilities, we had one incident when we lost alerting generally because Rootly crashed, and we did not like it."
"There are a few areas where Rootly can be improved."
"We would like to see a greater variety of integrations with ServiceNow. It works fine as it is, but an enhancement would be the ability to interact with the major incident module in ServiceNow... The way our major incident process works, when an incident is elevated from a P1 to a major incident, that is an extra flag in ServiceNow. It would be awesome to have xMatters get notification when something goes from a P1 to a major and then have it go through a different workflow, rather than our regular P1."
"Every customer would like a free ride, of course, and being a customer, I definitely feel the pricing is too high."
"Support may take longer than desired to resolve some issues."
"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."
"Some of the workflow development work that we do for the in-house piece can be quite complicated if you don't have experience using the tool."
"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."
"As an agent, as someone who is on call, I can mark an absence time and I can optionally put somebody in my place, but once you've done that, you can't edit it. You have to delete it and create a new absence, which is annoying, but it's not a massive issue. It's a minor annoyance. That's probably about the only thing I can come up with because I absolutely love the product. It's met our needs so well."
"The reporting functionality could be improved, as it can be somewhat restrictive sometimes."
 

Pricing and Cost Advice

Information not available
"This is a subscription-based, SaaS solution."
"Then, in pricing, you are limited on your number of SMS messages that you can send a month and the licensing cost annually."
"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."
"​Pricing is pretty straightforward and listed on their website. I recommend starting small and expanding later.​"
"​I do not think it is worth the value.​"
"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."
"The only potential concern is professional services. They are capable, but like to bill on an hourly basis."
"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.
913,683 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Performing Arts
27%
Comms Service Provider
7%
Financial Services Firm
7%
Transportation Company
7%
Financial Services Firm
11%
Construction Company
10%
Performing Arts
9%
Outsourcing Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business4
Midsize Enterprise2
Large Enterprise24
 

Questions from the Community

What is your experience regarding pricing and costs for Rootly?
Regarding my experience with pricing, setup cost, and licensing, we got a license for one year. Generally, it is great and the price is great, and that is the reason we chose Rootly. The only thing...
What needs improvement with Rootly?
There are a few areas where Rootly can be improved. More customization options for postmortem templates and reports would be helpful. Enhancing search functionality to make it easier to locate hist...
What is your primary use case for Rootly?
I use Rootly every day to manage the end-to-end incident lifecycle. When a critical incident is reported, I create or join an incident on Rootly, assign the appropriate severity, and engage the req...
Ask a question
Earn 20 points
 

Comparisons

 

Also Known As

No data available
xMatters IT Management
 

Overview

 

Sample Customers

* **Atlassian** * **Cisco** * **Databricks** * **DigitalOcean** * **Google Cloud** * **IBM** * **JetBlue** * **LinkedIn** * **Lyft** * **Microsoft** * **MongoDB** * **Netflix** * **Pinterest** * **Qualcomm** * **Red Hat** * **Salesforce** * **Spotify** * **Square** * **T-Mobile** * **Twitter** * **Uber** * **VMware** * **WeWork** * **Workday** * **Xerox** * **Zoom**
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 Rootly vs. xMatters and other solutions. Updated: September 2026.
913,683 professionals have used our research since 2012.