# Rootly Reviews **Vendor:** Rootly **Category:** [Incident Management Software](https://www.g2.com/categories/incident-management) **Average Rating:** 4.8/5.0 **Total Reviews:** 68 ## About Rootly Rootly is the AI-native on-call and incident management platform that helps you resolve incidents faster, improve system resilience, and streamline on-call operations. It’s your always-on production AI copilot that automates root cause analysis and identifies patterns that drive continuous improvement—trusted by thousands of companies like LinkedIn, NVIDIA, Replit, Elastic, Canva, Clay, DoorDash, SoFi, and Superhuman. ## Rootly Pros & Cons **What users like:** - Users appreciate the **ease of use** of Rootly, enabling quick and intuitive incident management without overwhelming complexity. (10 reviews) - Users love the **automation features** in Rootly that streamline incident management and enhance team efficiency. (7 reviews) - Users appreciate the **seamless integration with Slack** , enhancing communication and speeding up incident management processes. (7 reviews) - Users commend Rootly's **responsive customer support** , valuing their engagement and willingness to integrate feedback effectively. (6 reviews) - Users find the **easy setup** of Rootly impressive, allowing for quick onboarding and efficient configuration. (5 reviews) - Users love the **seamless integrations** of Rootly, enhancing incident management and collaboration with existing tools like Slack. (5 reviews) - Easy Integrations (4 reviews) - Team Collaboration (4 reviews) - Efficiency (3 reviews) - Intuitive (3 reviews) **What users dislike:** - Users note **integration issues** with Rootly, lacking extensive out-of-the-box options compared to competitors. (3 reviews) - Users note the **missing features** in Rootly compared to competitors, impacting functionality and integration options. (3 reviews) - Users note **feature issues** with Rootly, particularly regarding clunky UI and weaker metrics dashboards impacting usability. (2 reviews) - Users experience **notification overload** with Rootly, which can hinder focus during major incidents and complicate workflows. (2 reviews) - Users find the **notification overload** during major incidents in Rootly can be quite overwhelming, affecting productivity. (2 reviews) - Users find that Rootly's **initial complexity** can be challenging for smaller teams lacking dedicated DevOps resources. (1 reviews) - Users find the **complex setup** of Rootly daunting, especially for smaller teams lacking dedicated DevOps support. (1 reviews) - Users note a **lack of tutorials** for advanced workflows, leading to trial-and-error in customizations. (1 reviews) - Users find the **learning curve challenging** , especially with the UI and navigating custom workflows in Rootly. (1 reviews) - Limited Customization (1 reviews) ## Rootly Reviews ### 1. Friendly, Easy to Configure, Powerful and Highly Customizable for Incident Management **Rating:** 4.5/5.0 stars **Reviewed by:** Guillermo S. | International Project Manager, Enterprise (> 1000 emp.) **Reviewed Date:** May 08, 2026 **What do you like best about Rootly?** It’s friendly, easy to use, and simple to configure, with an extremely high level of customization. Having the flexibility of adding different integrations and putting together use specific workflows and scenarios has allowed us to automate value delivered from the incident management perspective. **What do you dislike about Rootly?** It is slightly buggy for new features, however, this is not a detriment, while it does have some slight implications, the team listens to feedback and acts on it with incredible speed! **What problems is Rootly solving and how is that benefiting you?** It is streamlining our incident management process overall. Having everything automated and flexible is extremely valuable for us ### 2. Standardized Incident Management in Slack with Fast, Reliable Escalations **Rating:** 5.0/5.0 stars **Reviewed by:** Art S. | Director, Platform Engineering, Mid-Market (51-1000 emp.) **Reviewed Date:** January 26, 2026 **What do you like best about Rootly?** Rootly has helped us standardize our incident management practices within Slack, which is our primary means of communication. It reduces context switching and lets operations engineers stay focused on the actual issue, rather than bouncing between multiple tabs trying to find the right one. It’s also easy to use and enables quick, reliable escalations when we need them. **What do you dislike about Rootly?** Rootly does not have as many out of the box integrations as some of its competitors. You are able to work around this using webhooks, but the native integrations are more powerful and feature rich. **What problems is Rootly solving and how is that benefiting you?** Rootly provides a single pane of glass for incident management. It’s an all-in-one solution for managing incidents from initiation through retrospectives. Rootly makes it easier to stay focused on the active problems themselves, rather than getting bogged down in the constructs used to frame the problem. ### 3. Streamlined Issue Logging with Clean, Fast Functionality **Rating:** 4.5/5.0 stars **Reviewed by:** Modi M. | Product Specialist, Mid-Market (51-1000 emp.) **Reviewed Date:** March 26, 2026 **What do you like best about Rootly?** I like Rootly for its clean and fast functionality. It's not difficult to navigate, which makes interactions smoother and more efficient. The speed of Rootly makes my work more productive. I appreciate how Rootly creates a separate space and Slack channel for interacting on a single issue with multiple stakeholders from cross-functional teams. **What do you dislike about Rootly?** I think it could be improved by having a guided tour whenever there's a new change or update to the product. It would make navigation easier, instead of us having to guess the next step. **What problems is Rootly solving and how is that benefiting you?** I use Rootly for logging issues, which creates a separate space and Slack channel for interacting with multiple stakeholders across teams. ### 4. Effortless Incident Management with Seamless Integrations **Rating:** 5.0/5.0 stars **Reviewed by:** Jason N. **Reviewed Date:** January 14, 2026 **What do you like best about Rootly?** I like that everything is stored in one place and integrates easily with all our existing tools. The workflow feature enables the automation of many tasks, eliminating manual steps, helping us ensure consistency of our processes, and allowing us to quickly respond to changes. The setup was very easy, and I was able to get up and running in about 2 hours and have the majority of the configuration for our needs in a day or less. **What do you dislike about Rootly?** There have been a couple of minor issues with integrations but the support team was quick to respond to our issues and fix them in the platform. **What problems is Rootly solving and how is that benefiting you?** Rootly helps coordinate incident resolution efforts, tracks items, supports compliance reporting, and integrates with existing tools. It stores everything in one place, automates tasks, and eliminates manual steps, ensuring process consistency and quick response to changes. ### 5. Engineering manager view: consistency + visibility **Rating:** 5.0/5.0 stars **Reviewed by:** Anthony P. | Sr. Manager Engineering, Mid-Market (51-1000 emp.) **Reviewed Date:** January 22, 2026 **What do you like best about Rootly?** From an engineering manager’s perspective, the biggest value of this product is the consistency and visibility it brings. It helps me stay aligned with the team and quickly understand what’s happening across the group, without having to chase down updates. **What do you dislike about Rootly?** Easier, more automatic shift changes linked to the Outlook calendar. **What problems is Rootly solving and how is that benefiting you?** As an engineering manager, Rootly has improved my visibility into incidents without requiring me to constantly chase down context. The incident pages and timelines are easy to read, and it’s much simpler to spot recurring themes across services. ### 6. Effortless On-Call Management at a Great Price **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Electrical/Electronic Manufacturing | Small-Business (50 or fewer emp.) **Reviewed Date:** November 10, 2025 **What do you like best about Rootly?** Rootly has been a simple on-call alerting platform that meets many of our needs, all at a very competitive price compared to competitors. What I like best is how easy it is to use and get going out of the box - the platform is intuitive and does exactly what we need. Customer support / relations has been fairly engaged and happy to work with us on feature requests - even with being a relatively small team and small customer. It was quick and seamless to get up and running, especially with popular integrations that are supported and well documented. **What do you dislike about Rootly?** Being a simple platform, some features and complex use cases (such as automatic scheduling) is where Rootly falls behind the competitors . Although, this has not been a dealbreaker for us as the platform is quite simple, easy to use and sits at a very competitive price. **What problems is Rootly solving and how is that benefiting you?** On-call alerting and shift scheduling ### 7. Simple, powerful, and configurable incident management. **Rating:** 5.0/5.0 stars **Reviewed by:** Matt B. | Senior Infrastructure Engineer, Small-Business (50 or fewer emp.) **Reviewed Date:** August 05, 2025 **What do you like best about Rootly?** Rootly is a fantastic tool for both incident management and on-call handling. It has opinionated defaults that are often great on their own, but are also configurable. It integrated easily with our alerting systems, and provided both an easy initial setup but also the promise of more power and flexibility in routing alerts into pages if we needed it in the future. The on-call tool has much better ergonomics than our previous solution, for a fraction of the price of other pager solutions. Why have separate tools for incident management, on-call/paging, statuspages, and incident workflows when you could have one well-considered one that just works without jumping through hoops? Perhaps the biggest secret though is the customer support which is fantastic, even for a smaller team like ours. They've been responsive to both feature requests and bug reports, and clearly care about their product and their customers. I can recommend Rootly without hesitation if you're looking to level-up your incident management and paging systems. **What do you dislike about Rootly?** As a relatively newer product (compared to its competitors at least), there are some rough edges especially around the terraform provider. Additionally there are some events you'd expect to be able to trigger workflow that don't exist. But given the already high quality of the rest of the product and the rate at which it's improving, working around these things is a tradeoff I'm more than happy to make. **What problems is Rootly solving and how is that benefiting you?** Incident Management On-Call Management Paging Alert routing Incident Retrospectives / Post mortems ### 8. Easy Setup, Reliable Performance, and Helpful Support **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Information Technology and Services | Enterprise (> 1000 emp.) **Reviewed Date:** May 08, 2026 **What do you like best about Rootly?** Ease of use and reliability. It was very easy to set up, and the support has been good. **What do you dislike about Rootly?** Alerts tend to be noisy and disruptive. Marking them as noise doesn't seem to work as well. **What problems is Rootly solving and how is that benefiting you?** On call organization and shift planning have been the biggest benefits of using rootly. ### 9. Rootly Makes Incident Declaration Fast and Low-Stress On-Call **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Computer Software | Small-Business (50 or fewer emp.) **Reviewed Date:** January 22, 2026 **What do you like best about Rootly?** Rootly helped me reduce my cognitive load while on-call recently. Declaring an incident and getting the basics clearly defined upfront (severity, owner, roles, conference bridge) is quick, and the prompts are actually helpful without being really annoying. **What do you dislike about Rootly?** Some workflows took a couple iterations to match how we actually operate (not a dealbreaker). **What problems is Rootly solving and how is that benefiting you?** Rootly helped me reduce my cognitive load while on-call recently. Declaring an incident and getting the basics clearly defined upfront (severity, owner, roles, conference bridge) is quick, and the prompts are actually helpful without being really annoying. ### 10. Seamless, Smart, and Stress-Free Incident Response **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Automotive | Mid-Market (51-1000 emp.) **Reviewed Date:** September 12, 2025 **What do you like best about Rootly?** What I like best about Root.ly is how seamless it makes the incident management process. It brings structure and automation to what can otherwise be a chaotic and stressful situation, and the intuitive workflows help keep everyone aligned. I also really appreciate how well it integrates with the tools we already use, which makes adoption painless and ensures it fits naturally into our existing processes. Overall, it creates a sense of confidence that incidents will be handled consistently and efficiently, without adding unnecessary overhead. **What do you dislike about Rootly?** There are so many options that it can feel overwhelming at first, but the flexibility is worth it. **What problems is Rootly solving and how is that benefiting you?** Root.ly is solving the challenge of coordinating incident response quickly and consistently. Before, incidents could feel scattered across different tools and teams, but Root.ly centralizes everything into one streamlined workflow. It reduces confusion, automates repetitive tasks, and ensures everyone is aligned from start to finish. The benefit is faster resolution times, less stress during high-pressure situations, and clear documentation afterward that helps us learn and improve for the future. ### 11. Slack-Native Incident Management That Speeds Coordination **Rating:** 4.5/5.0 stars **Reviewed by:** Deborah H. | NOC Engineer, Enterprise (> 1000 emp.) **Reviewed Date:** February 17, 2026 **What do you like best about Rootly?** Slack-native incident management: Instead of forcing teams into a separate tool, Rootly operates inside Slack—where incidents actually unfold. That reduces context switching and speeds up coordination. **What do you dislike about Rootly?** Slack fatigue. Some teams prefer separating incident response from normal chat. Running everything in Slack can create notification overload during major incidents. **What problems is Rootly solving and how is that benefiting you?** Faster Response Teams recover from issues quicker because everyone knows the playbook and steps are automated. ### 12. Delightful setup **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Computer Software | Small-Business (50 or fewer emp.) **Reviewed Date:** January 14, 2026 **What do you like best about Rootly?** It was so easy to set up. We got our entire engineering team onboarded to an on-call schedule in a single day! **What do you dislike about Rootly?** I can't say there's anything that jumped out as negative. **What problems is Rootly solving and how is that benefiting you?** An easy-to-manage on-call rotation is a hard requirement for our org. Rootly made it so easy to set up and manage. Thanks Rootly! ### 13. Smooth incident management with strong automation capabilities **Rating:** 4.0/5.0 stars **Reviewed by:** Verified User in Financial Services | Mid-Market (51-1000 emp.) **Reviewed Date:** September 12, 2025 **What do you like best about Rootly?** Rootly makes incident management simple and efficient. I really like how easy it is to integrate with existing tools like Slack, Jira, and PagerDuty. The automated workflows save a lot of manual overhead and ensure our team follows consistent processes during incidents. The interface is clean, and setup was straightforward, even for a relatively small IT team like ours. **What do you dislike about Rootly?** Occasionally, some of the deeper customizations require a bit of trial and error, and documentation can be improved in a few places. It’s not a blocker, but more real-world examples for advanced workflows would help us unlock even more value quickly. **What problems is Rootly solving and how is that benefiting you?** Rootly helps us standardize and automate our incident management process. Before Rootly, our workflows during incidents were scattered across multiple tools and depended heavily on manual steps. With Rootly, we’ve automated incident creation, escalation paths, and notifications directly in Slack and Jira, which has saved us time and reduced human error. It’s also made postmortems much easier to generate, ensuring we can learn from each incident quickly. ### 14. Effortless and Responsive Integration with Slack **Rating:** 4.0/5.0 stars **Reviewed by:** Verified User in Information Technology and Services | Enterprise (> 1000 emp.) **Reviewed Date:** January 12, 2026 **What do you like best about Rootly?** Very easy to use and responsive, connects with Slack **What do you dislike about Rootly?** Often nagging behavior and inability to understand certain tasks - templates would make this better **What problems is Rootly solving and how is that benefiting you?** They are enabling us to create and resolve incidents much faster and cohesively as a team - it also increased discoverability through Slack integration ### 15. Quick & easy to use - Great customer service **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Public Safety | Enterprise (> 1000 emp.) **Reviewed Date:** September 03, 2025 **What do you like best about Rootly?** It was a breath of fresh air using Rootly having moved from one of their competitors where we weren't able to get the solution fully working (who also charged us for "premium" support!). Rootly is easy to set-up with support included in a straightforward no-nonsense affordable subscription plan. Furthermore, feedback/suggestions we had were taken seriously and as a result they've now improved the platform not only for us but all their other customers. **What do you dislike about Rootly?** We have no issues so far, Rootly just works with minimal admin. **What problems is Rootly solving and how is that benefiting you?** Rootly is currently being used for our on-call security incidents solution. ### 16. Effortless Incident Management **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Computer Software | Small-Business (50 or fewer emp.) **Reviewed Date:** October 24, 2025 **What do you like best about Rootly?** Rootly is an exceptional incident management platform that helps teams resolve issues faster and more effectively. Its seamless Slack integration and automated workflows make incident response feel effortless and organized. It's clearly been built with performant engineering teams in mind. **What do you dislike about Rootly?** The only downside is that Rootly can feel a bit complex to set up initially, especially for smaller teams without dedicated DevOps resources. **What problems is Rootly solving and how is that benefiting you?** Incident Management ### 17. One stop shop for streamlined Incident Management! **Rating:** 4.5/5.0 stars **Reviewed by:** Allen J. | Technical Program Manager- SRE, Enterprise (> 1000 emp.) **Reviewed Date:** February 25, 2025 **What do you like best about Rootly?** Rootly makes incident management much easier by integrating right into Slack and automating a lot of the busy work and enables unique processes for each type of incident. It keeps everything organized, enforces a consistent process, and saves a ton of manual effort. The customizable playbooks and integrations with tools like PagerDuty, Jira, and confluence are super helpful for fitting into different team workflows. AI based incident summarization/RCA drafting in slack is also really neat feature for incident management at scale. Rootly's customer support as well as initial onboarding experience was very good. **What do you dislike about Rootly?** One downside of Rootly is that the UI can feel a bit clunky at times, especially when navigating through incidents or setting up custom workflows. Some workflows take a bit of trial and error to get right, and certain integrations could be smoother. Also, while automation is great, there are times when it feels like there are too many notifications or updates in Slack, but overall the slack nagging gets people to action on things. **What problems is Rootly solving and how is that benefiting you?** Rootly helps streamline incident management by automating workflows across JIRA, PagerDuty, and slack by keeping everything organized in Slack, and reducing the manual effort needed to track and resolve incidents in other platforms. It makes it easier to follow a consistent process, ensures key updates don’t get lost, and speeds up response times. The built-in post-mortem feature also helps improve reliability by making it simple to review and learn from past incidents. ### 18. Game-Changer for Incident Management **Rating:** 5.0/5.0 stars **Reviewed by:** Richard H. | VP of Engineering, Mid-Market (51-1000 emp.) **Reviewed Date:** February 24, 2025 **What do you like best about Rootly?** We love using Rootly for incident management! The Slack integration makes real-time collaboration effortless, and the automated runbooks, along with Jira and PagerDuty integrations, have streamlined our workflow. **What do you dislike about Rootly?** No major downsides—occasional minor UI improvements would be nice, but the team iterates quickly! **What problems is Rootly solving and how is that benefiting you?** Rootly is solving the challenge of fragmented and inefficient incident management. Before using Rootly, coordinating incidents required a lot of manual effort—tracking updates across different tools, ensuring the right people were notified, and maintaining consistency in response processes. With Rootly, everything is streamlined. ### 19. Streamlined Incident Management with Great Automation and Support. **Rating:** 5.0/5.0 stars **Reviewed by:** Kieran W. | Service Delivery Manager, Mid-Market (51-1000 emp.) **Reviewed Date:** October 04, 2024 **What do you like best about Rootly?** Rootly is incredibly easy to use and configure, allowing us to streamline our entire incident management process. One of the standout features is the ability to create automated workflows, which saves a lot of time and ensures that key steps in the incident process are handled efficiently. For example, setting up automated reminders for SLA breaches or post-incident reviews is simple, and it keeps the team on track without manual intervention. The seamless integration with applications like Slack is another major benefit. We can manage almost the entire incident management process directly from Slack, from initiating incidents to updating timelines and coordinating with the team. This integration significantly improves communication and speeds up the resolution process. **What do you dislike about Rootly?** The main area for improvement is in the 'metrics' side of the application. Currently, there are some limitations around filters in certain panel options, which makes it harder to return the exact data we need for how we use the application. For example, it would be helpful if the graphs created within the metrics were more interactive. Ideally, users should be able to click on a specific data point, like the number of incidents between certain dates, and be taken directly to the relevant incident results. Improving this functionality would make Rootly even more effective in managing and analysing incident data. **What problems is Rootly solving and how is that benefiting you?** Rootly helps us solve the challenge of managing incidents efficiently by automating key parts of the incident management process. It enables us to streamline everything from incident creation to resolution, ensuring that nothing falls through the cracks. With its seamless integration into Slack, we can manage incidents in real-time and keep our teams aligned, reducing communication delays. One of the biggest benefits has been a significant improvement in our incident metrics. Rootly has directly contributed to reducing our Mean Time to Detect (MTTD), Mean Time to Mitigate (MTTM), and Mean Time to Resolve (MTTR) stats. Automation and clear workflows allow us to respond faster and work more effectively as a team. Additionally, Rootly’s automation enables us to update our status page in real-time, ensuring that our customer base is kept informed throughout the entire incident process without manual intervention. This keeps communication clear and efficient. The ability to automate SLA reminders, incident escalations, and post-incident reviews further enhances our incident management process, helping us stay on top of every incident and respond swiftly. ### 20. Fantastic Incident Management Product with Unrivalled Flexibility **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Computer Software | Enterprise (> 1000 emp.) **Reviewed Date:** February 19, 2025 **What do you like best about Rootly?** There is a lot of positives to talk about with Rootly, but by far the biggest draw for me was the flexibility of the product. Many products out there are very opinionated - they expect your Incident Management flow to follow the flow and process that THEY define. Rootly can give you an out-of-the-box template and opinions, but it also lets you customise almost everything to your organisation. From forms and fields, workflows, integrations, it's all there to be as flexible as possible. Another huge plus is quite simply the people working on Rootly - not only are they great to work with, but have been extremely receptive to feedback and feature requests, resulting in active development of features that my users care about - rather than only features that someone in the company cares about, which I've encountered with other vendors. We built Rootly from the perspective of "Anyone should be able to use this, with or without experience, and without needing to reference documentation" and Rootly has 100% enabled this. We have documentation and processes outlined, and they're entirely ignored because Rootly can literally guide you through the process from within Slack and the tooling, which is a huge win for adoption. **What do you dislike about Rootly?** My only real problems with Rootly are around certain features being a little weaker than the main Incident Management product, like the metrics dashboards not being as flexible as I would like. However, not only have I heard Rootly are working on overhauling this, but we also utilise this data externally within our own tooling (as Rootly allows us to export this data) which heavily negates this downside. **What problems is Rootly solving and how is that benefiting you?** Incident Management. Our previous Incident Management process and tooling was very difficult to work with, and resulted in very low engagement. By using Rootly to reduce barrier of entry we've massively increased adoption of the process, and in turn have a large amount of incident data that we can use to make informed decisions both about our progress and our future directions. ### 21. Convenient tool for incident management in slack with great features **Rating:** 4.0/5.0 stars **Reviewed by:** Michel G. | Staff Software Engineer, Mid-Market (51-1000 emp.) **Reviewed Date:** July 01, 2024 **What do you like best about Rootly?** A few things I like so far: - Easy to use with a great slack interface - Has an API which allows me to use Rootly's data when I eventually want to work with this data programatically - Although we don't use this feature, there's the ability to incorporate with JIRA which makes issue tracking for action items easier - Anytime I've found a bug I can work with rootly's support team to get the issue resolved quickly - **What do you dislike about Rootly?** Not too many things to dislike, but things I would love: - More automation around incident retros - automating creating meetings based on participent's gmail calendar would be sick. Even though we have manditory retros with our workflow, those are often skipped, meaning we lose the valuable lessons learned during an incident. - This may be a limitation of slack, but a clearer UI demarkation of who is playing which role in an incident would help users' tell who is playing which role in an incident **What problems is Rootly solving and how is that benefiting you?** Acting as the hub to the incident management process ### 22. Product with amazing capabilities and wondering TAT for anything **Rating:** 5.0/5.0 stars **Reviewed by:** Darshan S. | Product Support Manager, Mid-Market (51-1000 emp.) **Reviewed Date:** April 10, 2024 **What do you like best about Rootly?** Rootly Team frequently checks in and provides required support at every stage, this enhances our experience positively. Communication is easy via the Slack support channel. Product Workflows - Workflows are made easy for everyone to easily understand, providing great UX. Feature requests shared are taken seriously and they ensure they meet the expectations. Collaboration with the team is great. The best part is - Direct support from the founders when necessary. We were handling everything manually earlier, once we onboarded with Rootly, our team saved at least 2 hours a day. There is not even one day without using Rootly. Integration with multiple tools is simplified, especially JIRA. Given these points, adapting to Rootly was made easy, and moving to another similar tool was made unthinkable. **What do you dislike about Rootly?** I would say NOTHING! Given the fact we are using Rootly after handling everything manually, our experience with them is amazing. **What problems is Rootly solving and how is that benefiting you?** - Incident Management. - Oncall Escalations. - Oncall tasks. - Manage multiple Bugs within the product. - Easier Reporting. - Easy to collaborate. ### 23. Excellent start, and rapidly maturing product **Rating:** 4.0/5.0 stars **Reviewed by:** Colin F. | Incident & Problem Manager, Mid-Market (51-1000 emp.) **Reviewed Date:** December 19, 2023 **What do you like best about Rootly?** Rootly is an amazing beginning, and is getting better quickly. Each week they release updates, improvements and features that expand their capabilities, and it gets easier and easier to use. Initial implementation takes some work, but their team is there to help. The support they provide is excellent, and the troubleshooting is mostly fast, direct and responsive. I use the product for several hours a day, and have quickly become familiar with the feature set. It's made conversations about our incident system more powerful, provided data where it was needed most, and allows us the insight necessary to improve our processes. **What do you dislike about Rootly?** The integrations with Confluence, Jira, PagerDuty and Slack are decent. There is room for improvement in all of them, but they get most tasks done and done right. Custom forms and fields are a weak point (they are available but take significant hand holding in the product to make effective), and the reporting systems are "fine", but once again require quite a bit of manual labor to build and maintain. **What problems is Rootly solving and how is that benefiting you?** It provides us with data where there was none, allowed us to standardize our process, and has increased the automations that let our incident response team focus on responding and not on managing a third party product. ### 24. I would choose Rootly for the people alone **Rating:** 4.5/5.0 stars **Reviewed by:** Verified User in Computer & Network Security | Mid-Market (51-1000 emp.) **Reviewed Date:** February 12, 2024 **What do you like best about Rootly?** Rootly stood out as having the most number of integrations that are actually useful. It is simple, easy to use, yet highly customizable to your organization. We use it everytime there is an active incident - in fact, we have made Rootly the starting point of our organization's incident response process. The turn around time in fixing bugs are usually low (sometimes to the tune of hours instead of days). Not to mention, their customer facing team are all friendly, easy going, and highly responsive. I would pick Rootly for their people alone. **What do you dislike about Rootly?** Rootly's analytics/reporting feature and Confluence integration is not as polished as it can be. This is not a deal breaker though as you can easily exfiltrate Rootly data to your own data warehouse for reporting. Their Confluence export of retrospective can be further improved, this is especially around the Slack timeline feature where it is sometimes incomplete or in the incorrect order. Slack screenshots are also not embeded in the Confluence doc. **What problems is Rootly solving and how is that benefiting you?** Rootly has quickly become the starting point of our incident response process. It automated our 25 steps process down to 5 steps which significantly lowered the barrier to manage incidents. ### 25. Rootly got us up and running fast! **Rating:** 5.0/5.0 stars **Reviewed by:** Shrav M. | Founder and CEO, Mid-Market (51-1000 emp.) **Reviewed Date:** February 21, 2023 **What do you like best about Rootly?** After a couple of false starts with other tools, we finally found Rootly. The ease of use to get started running incidents stood out to me. As a fast growing startup, we needed to get going fast. My team was able link all our critical incident tooling into Rootly & build in the automation we needed in minutes. **What do you dislike about Rootly?** It solves our pain points around incident automation. Nothing to complain about. We’re excited to see what the team comes up with this year. **What problems is Rootly solving and how is that benefiting you?** Rootly helps ensure that our whole team is on the same page, quickly, during an incident. The start of an incident is crucial for us (as I’m sure it is for others), and Rootly gets us ready fast. It also helps ensure we follow our process consistently. We’ve seen a solid reduction in our MTTR metrics and the team is more confident than ever in their ability to respond to incidents. This year we’re looking forward to pushing automated communication even further to ensure partners & other internal stakeholders have all the information they need when we are responding to an incident. ### 26. Incident management that fits your workflow **Rating:** 5.0/5.0 stars **Reviewed by:** Shane B. | Mid-Market (51-1000 emp.) **Reviewed Date:** February 10, 2023 **What do you like best about Rootly?** First and foremost incidents are about communication, both internally and externally, and it was important to us at ROLLER that any tool we chose for incident management fit within our existing methods of communicating. Rootly with its deep integration with Slack fit the bill perfectly, removing the problem of disjointed conversations happening across different platforms that we had previously. Despite taking an unusual approach of being support-led in our incident creation, essentially allowing anyone to "pull the fire alarm", we were easily able to replace our cobbled-together custom webhooks with simple workflows that integrated with our existing tools, such as Jira, Opsgenie and Datadog. We were even able to repurpose a lot of the existing workflows that are available as soon as you first log into Rootly, a sign that the team has carefully considered each integration and how it will work inside Rootly. So far on our journey together, Rootly has improved incident ownership, mean-time to resolution and allowed for more effective communication for our geographically disparate teams. It has quickly become a vital tool for helping to keep our services up and running for our customers. **What do you dislike about Rootly?** The initial setup can be a little bit slow when your company already has a prescriptive incident workflow that you want to replicate inside Rootly. That said, it appears the team at Rootly was aware of this as they have released a Terraform plugin for configuring your workflow as code which would address this problem perfectly. **What problems is Rootly solving and how is that benefiting you?** Rootly allows us to focus on the issue at hand when we have an incident by removing a lot of the laborious tasks required when resolving an incident. It does this via simple commands and reactions in Slack, automation and integration with a lot of other popular tools used during the lifecycle of an incident. It even pre-populates an incident timeline to be included in the postmortem, saving you time after the incident is resolved. ### 27. Rootly - a tool that lets you focus more on the Incident, and less on the Management **Rating:** 5.0/5.0 stars **Reviewed by:** Enoch L. | Site Reliability Engineer, Mid-Market (51-1000 emp.) **Reviewed Date:** February 02, 2023 **What do you like best about Rootly?** During the initial evaluation, we compared Rootly against a variety of tooling that offered similar functionality. What was important was that we had a reliable and heavily customizable tool that also worked "out of the box" for processes we either didn't care to customize or that we used another vendor for (e.g., alerting via Pagerduty). Rootly met these requirements and more. We were able to set up custom workflows that would trigger based on a variety of incident attributes. With near-unlimited dimensionality/cardinality for incident attributes, we could use Rootly to automate processes that severely slowed down the incident investigation process. Furthermore, Rootly has rich integration with all of our other tools. In the case the integration didn't exist yet, Rootly went out and built it out for us. Combining the workflows, incident attributes that could determine which workflow(s) to run, and rich tooling integration meant that we spent less time figuring out what to do for different incident types and more time investigating the incident. Finally, Rootly is backed by a spectacular team eager to deliver. Working with Rootly feels like a partnership; as we continued to use their tool and found more use cases, our feature requests quickly found their way into (or, luckily for us, were already in) their backlog. Whether it was quality-of-life improvements to aid incident visibility on Slack (rich customization of Slack messages from Rootly) or Infrastructure-as-Code management for workflows via Terraform, Rootly continued to iterate and grow with our needs. **What do you dislike about Rootly?** With heavy customization comes a large amount of complexity when navigating the workflows. Rootly has done a lot of work improving this; visually via workflow groups and organizationally by adding a Terraform provider to store workflows as code. However, it is still daunting when opening the Workflows tab and seeing dozens of workflows. The large number of workflows is because workflows do not have strong conditional logic (e.g., notifying different teams based on an affected service results in a workflow for each team, rather than a single workflow with branching conditions). **What problems is Rootly solving and how is that benefiting you?** The most valuable part of Rootly is how it streamlined AND standardized the incident process across departments. Cross-department communication is now automated behind workflows and incident attributes. An on-call engineer or SRE no longer has to page out to the on-call for an affected service manually. Our customer success team now knows precisely what contextual incident information is required to trigger an incident from Slack without having to remember or consult a Confluence wiki page. The right people are automatically informed for high-priority or visible incidents; participants are no longer required from an incident because someone missed a line in an escalation document or used the wrong method of communication. Rootly has automated all the previously manual back-and-forth between folks with tribal knowledge and the respective tooling to notify, orchestrate, and review an incident. ### 28. Functional and flexible tool for incident management **Rating:** 5.0/5.0 stars **Reviewed by:** Matt L. | Mid-Market (51-1000 emp.) **Reviewed Date:** February 02, 2023 **What do you like best about Rootly?** There are two key areas we like: 1) The workflow engine in Rootly is really powerful. We've been able to encode a complicated set of communication requirements in a way that helps our OCEs manage the incident and not spend time looking up complicated business rules before communicating to customers. 2) The terraform support is tremendous -- nearly everything in Rootly is configurable via the terraform provider. This means we can manage our oncall tooling the same way we do our other infrastructure. This has been backed by a very responsive and friendly development team. **What do you dislike about Rootly?** We've barely scratched the surface of what we can do with Rootly. In some ways it is maybe a little too flexible; we haven't been able to sit down and fully customize everything to our liking or even internalize everything it can do. **What problems is Rootly solving and how is that benefiting you?** Rootly helps us manage our incidents. There are table stakes in this area that Rootly does well -- integrations, a slack bot, post-mortem guides, etc. It does all those just as well as its competitors, but the additional focus on the workflow engine and terraform integration has been really helpful. The main utility for us is that Rootly is a tool that allows us to encode our oncall process in a way reduces the cognitive load on our OCEs and supporting incident roles. One example of this relates to our communication flow. We have many customers that have different needs and different business rules: - "If it is a P1 incident for customer X, send emails to A, B and C. Send updates every 30 minutes" - "If it is a P2 incident for customer X, send emails to A and B. Send updates every hour" - etc for many customers We've encoded these rules in various Rootly workflows and now our Comms Lead will get a slack notification with a sample email at the right time as the incident evolves, and can send this email with a single click. ### 29. Incident Management tool for everyone! **Rating:** 5.0/5.0 stars **Reviewed by:** Karl K. | Incident Engineer, Mid-Market (51-1000 emp.) **Reviewed Date:** January 18, 2023 **What do you like best about Rootly?** Rootly synchronizes really with Slack and it's amazing that the entire incident lifecycle from the beginning of a new incident until an incident is resolved can be managed via different commands inside Slack. The interface is very basic, simple, and customizable and that's what makes it good. Each organization can decide and set up the exact fields (or use the existing ones) that are relevant to their Incident Management process. The Rootly Support team has been active and helpful when it comes to any technical question. New ideas are positively welcomed. Rootly has very clear and easy to use guidelines, helpful descriptions and that enables people with little to no previous experience in Incident Management to jump straight into creating their first incident! **What do you dislike about Rootly?** Depending on the size of the organization the workflow and automation management can become overwhelming for a single individual if the amount of automation/workflow rules grow large. Thankfully, Rootly has the option to group different workflows under different folders/categories (Slack, Jira, Pagerduty etc.). **What problems is Rootly solving and how is that benefiting you?** Rootly reduces most of the manual work needed to lay down the foundation for a new incident through automation and workflows. New incident along with a specific slack channel can be created in seconds by anyone. Same goes for tracking and creating action items or managing postmortem timeline if needed. Our way of using Rootly is also promoting transparency within the company, so that anyone and everyone can join the incident channel if they want to contribute or want to be up to date with the latest developments. Rootly sends out notifications in relevant channels and this often reduces the time to gather correct team of specialists and to resolve the incident itself. ### 30. Rootly is going places **Rating:** 5.0/5.0 stars **Reviewed by:** Matthew M. | Senior Site Reliability Engineer, Enterprise (> 1000 emp.) **Reviewed Date:** January 23, 2023 **What do you like best about Rootly?** Rootly is a great incident management tool for that will streamline your process and take out a lot of the manual effort and toil when starting an incident. Rootly will keep you consistent which helps speed up the process to recovery. The team at Rootly is very responsive to customer feedback and they are constantly implementing new features based around that feedback. With Rootly, incident spin-up time has been reduced from minutes to seconds and it covers over 90% of our needs. Overall, Rootly is the best tool currently available in the market. They have a ton of integrations to get you started and workflows that are flexible enough to meet most of your needs. I have been super impressed with Rootly and the capabilities it offers. With the constant feedback loop, you won't regret giving them your money. **What do you dislike about Rootly?** Specific fields are essentially hardcoded, making it hard to customize around them. Rootly is working towards making these parts more customizable, but this does limit you in some ways. I wouldn't say this is a deal breaker, as most of the time, we can figure out a way around it. The other thing that is a bit lackluster is the UI, but don't really need or use it anyway. We don't want to context switch and try to operate from Slack whenever possible. Rootly is looking to address this to reduce some of the cognitive load when looking at the UI. The UI is just another item that is hardly a deal breaker. **What problems is Rootly solving and how is that benefiting you?** Rootly takes out the toil and makes incident management repeatable. They also have other tools to help keep track of metrics and get from incident response to postmortem in an automated way. This greatly helps in managing your incidents and seeing where in the process something is at. ### 31. Powerful incident management tool **Rating:** 5.0/5.0 stars **Reviewed by:** Igor Z. | Incident Engineer, Mid-Market (51-1000 emp.) **Reviewed Date:** January 16, 2023 **What do you like best about Rootly?** Very scalable to the size of organisation, with lots of automation possibilities from straightforward to complex conditions and lots of exceptions. Great use for several teams with different approach, size and other criteria . Seamless integration with Slack, Jira, Pagerduty. Easy to create/resolve incidents with least manual work expected. Advanced automation is very time saving on manual processes and checklists. UI made as easy and understandable as possible, so continuous improvements and flawless changes into configuration are made smoothly. Quick response team for any sorts of questions, from configuration to new feature request. **What do you dislike about Rootly?** By digging in deep into configurations there is a need to remember several dependencies created, which is probably the case for every complex tool. Learning all sorts of possibilities takes some time. After initial configuration is set, it grows on the go once new possibilities are discovered. The nice part about setting it up is amount of documentation for connecting various tools. **What problems is Rootly solving and how is that benefiting you?** Pretty straight-forward in terms of handling incidents, saves lots of hours of trainings for 500+ people. Giving more transparency in the company and providing clear view on areas need to improve and measure end results ### 32. Rootly - excellent incident management system **Rating:** 4.0/5.0 stars **Reviewed by:** Raymond S. | Enterprise (> 1000 emp.) **Reviewed Date:** February 05, 2023 **What do you like best about Rootly?** Rootly has significantly simplified and streamlined our incident management process. It's enabled us to automate a lot of manuaal tasks and ensure consistent incidents management. It allows us to easily build out our workflows and provide automations to our response team. It's also very helpful post incident, helping automate the post incident review process, building timelines and open action items. **What do you dislike about Rootly?** Currently limited to 1 channel per incident. Occasionally we need multiple channels per incident. Aside from that's it been fantastic. **What problems is Rootly solving and how is that benefiting you?** Ensuring consistent incident management process and automating response tasks and note taking. This has significantly reduced the amount of manual workload creating channels and following tasks lists. ### 33. Versatile and highly configurable incident management automation **Rating:** 5.0/5.0 stars **Reviewed by:** Jac D. | Security Engineer, Enterprise (> 1000 emp.) **Reviewed Date:** January 19, 2023 **What do you like best about Rootly?** Rootly has been a great asset in reducing the manual overhead of managing security incidents. It's extensive list of integrations means that we're quickly able to write automations for nearly all our existing internal tool suite, managing the entire lifetime of our incidents. These automations have saved us huge amounts of time, allowing us to focus on investigation and case quality rather than updating Jira tickets and managing Slack channels. The Rootly API has been fantastic to deal with - it's allowed us to further integrate with our existing systems, allowing us to orchestrate changes in Rootly incidents. In our unusual use-case, being able to customise Rootly to our requirements and externally trigger changes has further minimised the manual incident management that must be done. The Rootly team has been very receptive to our feature requests and is always willing to help improve our experience with our unusual use case. They've been very fast in developing and shipping changes to meet our project requirements and always make time to help us out as quickly as possible. **What do you dislike about Rootly?** Nothing to really call out here - the product was intended mainly for Site Reliability Engineering, however the Rootly team have been very open to feedback and willing to implement changes to fit our security incident management requirements. **What problems is Rootly solving and how is that benefiting you?** Rootly removes all the manual incident management that goes into running our security incidents. Not having to worry about things like inviting on-call engineers and sending out messages to leadership when high severity cases occur allow our Incident Response teams to focus on the response rather than the platform and people management aspects of running incidents. Since integrating fully with Rootly, our incident handling and documentation quality have increased significantly. ### 34. Rootly makes running incidents in Slack so easy **Rating:** 5.0/5.0 stars **Reviewed by:** Cory A. | Mid-Market (51-1000 emp.) **Reviewed Date:** February 06, 2023 **What do you like best about Rootly?** Rootly makes running incidents in slack easy so you can concentrate on fixing the incident. Rootly has been a critical help and responsive in helping to create and manage incidents through slack. **What do you dislike about Rootly?** I love everything about Rootly. Rootly has been a great partner to work with from the beginning. Rooltly has always listened to our feedback and has provided fixes when necessary. **What problems is Rootly solving and how is that benefiting you?** Rootly is a highly customizable solution for incident management. Rootly has helped us get the people working on the incidents so we can get the incidents solved. ### 35. Fast ROI and easy to get started! **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Retail | Mid-Market (51-1000 emp.) **Reviewed Date:** January 12, 2023 **What do you like best about Rootly?** I've looked at the competition Rootly stood out from the rest. They help us drive consistency in the incident response process and are used universally by the company, not just by engineers. Everyone raves about it. They plugged seamlessly into our process. They worked with the integrations that were central to how we worked. They help drive focus and speed when it comes to incidents. As a result, we've seen our MTTR significantly drop. The team acts more as reliability advisor than just a vendor. I haven't seen this before and is refreshing. **What do you dislike about Rootly?** Rootly is truly critical infrastructure for us. It has at the foundation of how we provide reliable services to our customers. Not that we would but because of how engrained Rootly is throughout the whole organization it would be very difficult to move off. **What problems is Rootly solving and how is that benefiting you?** We needed something that could work any responder through an incident step-by-step that was tailored for us in a scalable way. Relying on just "remembering what to do next" wasn't enough. For our business, time is money. Reducing downtime and shortening the length of incidents and repeats was critical. Rootly helps us achieve all of that. ### 36. Incident management using Rootly **Rating:** 5.0/5.0 stars **Reviewed by:** Payam N. | Site Reliability Engineering Manager, Mid-Market (51-1000 emp.) **Reviewed Date:** August 25, 2022 **What do you like best about Rootly?** Easy to use, Configurable, Automation. nothing else **What do you dislike about Rootly?** Coaching people to use it, nothing else t **What problems is Rootly solving and how is that benefiting you?** The biggest problem that Rootly resolved for us is automating communications during the life cycle of an incident. When our engineers are busy trying to resolve an incident it is difficult to remember to communicate the status of the incident and update the appropriate teams when the status has changed. Rootly has provided us with easy-to-use automation that does this for us. Since onboarding Rootly we have had seamless communications around the lifecycle of an incident allowing our account executives, support engineers, and customers to rest assured that their interruption in service is being prioritized. Rootly is highly flexible and configurable to fit our process and we did not have to change our process to fit Rootly functionality. Their support team responds very quickly any time we have a question and we are able to input improvement ideas to them and are confident that those ideas have a solution quickly. ### 37. A powerful Slack-based Incident Management tool **Rating:** 4.5/5.0 stars **Reviewed by:** Chris I. | Director of Engineering, Enterprise (> 1000 emp.) **Reviewed Date:** August 24, 2022 **What do you like best about Rootly?** The flexibility of Rootly's workflows has allowed us to create a handful of solutions for problems that are unique to our company. We have been able to use Rootly to design solutions that fit the needs of our internal teams, reducing cognitive overhead and increasing consistency in how we manage incidents. The number of integrations that Rootly provides with other software vendors increases every week, and this helps to create automation around tasks we perform during incidents. **What do you dislike about Rootly?** Many of the user interfaces within the Rootly web admin are overwhelming and confusing. I do hope that the Rootly product will improve its UIs over time, with more consistency and usability. **What problems is Rootly solving and how is that benefiting you?** Rootly is constantly adding new features and integrations to their product and they do so with blazing speed. The Rootly team is very receptive to feedback and suggestions and they have been very responsive to our inquiries when needed. ### 38. Excellent Service **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Financial Services | Mid-Market (51-1000 emp.) **Reviewed Date:** January 23, 2023 **What do you like best about Rootly?** I greatly appreciate the responsiveness of the Rootly team. We were replicating an existing process in Rootly, so often when we identified an issue, it would end up being a blocker for us. Rootly was very attentive and quick to help us through each step and added functionality to address our rather specific needs. It can't be understated how helpful it is that those blockers are addressed so quickly to keep us moving. **What do you dislike about Rootly?** There are still some outstanding issues in Rootly, but based on prior experience, I expect they'll be fixed soon. One problem we seem to hit occasionally is that race conditions can exist in Rootly. This causes some pain and we have to be very careful to watch out for them. **What problems is Rootly solving and how is that benefiting you?** We are currently using Rootly primarly for its workflow capabilities. When an incident is reported, Rootly sets up the rooms and meetings we need. ### 39. Consistent incident response ready out of the box **Rating:** 5.0/5.0 stars **Reviewed by:** Icelyn J. | Senior Site Reliability Engineer, Enterprise (> 1000 emp.) **Reviewed Date:** August 25, 2022 **What do you like best about Rootly?** A few things stood out about Rootly. Adopting the solution was made easy by the product and team behind it. Took us days instead of weeks when we looked at other potential options. Rootly's product development speed is extremely fast and have been able to turn around custom requests in a matter of hours. We've been able to truly view them as a partner, and that was important as our incident management program continues to evolve. **What do you dislike about Rootly?** Not much to dislike, I wish they had a bit more documentation around some features but they are extremely responsive whenever we have questions. **What problems is Rootly solving and how is that benefiting you?** By implementing Rootly, we've been able to empower everyone in our organization to run incidents regardless of their tenure. It has automated manual work such as communications so they can focus on what is actually important. ### 40. Rootly - A Great Journey so far. **Rating:** 4.0/5.0 stars **Reviewed by:** Wayne M. | Cloud Reliability Engineer, Enterprise (> 1000 emp.) **Reviewed Date:** August 24, 2022 **What do you like best about Rootly?** Using the Web UI of this tool is very easy to use. Also, we love the fact that this tool integrates easily with other tools such as Slack(for example) especially since we utilize a lot of the tools that can also integrate with Rootly to make our day-to-day operations go a lot smoother. Also, it helps that we can use this tool as almost the central command center for all of the other tools that we utilize in our organization. **What do you dislike about Rootly?** Currently, configuring this tool as code with Terraform is a challenge. There isn't an easy way to find the correlation between the teams/services/workflows that they utilize. This aspect can frustrate engineers to where it may be better to configure a team's alert/incident workflow configuration via the Web UI. **What problems is Rootly solving and how is that benefiting you?** It's easier to gather the correct folks for an incident that was triggered and to keep records of the important things discussed in the incident and store the information needed via Rootly tool itself. ### 41. Rootly's solid API makes it a good tool for power users **Rating:** 4.0/5.0 stars **Reviewed by:** Verified User in Financial Services | Mid-Market (51-1000 emp.) **Reviewed Date:** January 19, 2023 **What do you like best about Rootly?** Rootly imposes structure on the incident response process, but is flexible enough to allow us to develop our own styles of workflows. The well-thought-out API allows us to integrate it with other automations. Full disclosure: I was offered a $100 gift card to provide this review. However, that's only enough to motivate me to do it; not enough to color my opinions. **What do you dislike about Rootly?** Rootly is not very good at handling statefulness. It's virtually impossible to store, modify or retrieve custom information or variables related to an incident. It is also rather difficult to manage your workflows. If you have a lot of them doing complex tasks, suddenly a small change could require you to edit dozens. **What problems is Rootly solving and how is that benefiting you?** Before Rootly, incident response could sometimes descend into chaos, with different responders handling the incident in idiosyncratic ways, storing evidence in the wrong location, etc. Rootly allows us to keep IR organized and reduce confusion, which is particularly valuable when time is of the essence. ### 42. Incredible turn-key incident management tool! **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Financial Services | Small-Business (50 or fewer emp.) **Reviewed Date:** September 20, 2022 **What do you like best about Rootly?** I've worked at companies with best-in-class incident infrastructure, and this parallels the incredible tools at these industry-leading businesses (BRB at Stripe, specifically). The slack commands are simple and easy to use, the integrations are broad and super useful, and we save so much time (which is super valuable for a lean team) monthly [I'm thinking on the scale of hours to days] by having such robust central incident coordination at our fingertips. Not only was Rootly incredibly easy to set up, but the team really took the time to understand our needs and has continued to be actively engaged in building out functionality that our team has articulated as useful new features for our usecases. We looked into a number of other incident tooling providers, but Rootly stood out as the only tool that would be broadly accessible to the organization (the integration with Slack has really helped us democratize incident creation), AND we have been able to provision the full organization with access to the tool at a reasonable price point. Beyond functionality and accessibility to both technical and operational teams alike, the folks at Rootly are just a joy to work with. **What do you dislike about Rootly?** The tooling is just too smooth. When we actually encountered issues with integration or other functionality, the team was fast to help resolve. No complaints here! **What problems is Rootly solving and how is that benefiting you?** We needed a central coordination space to navigate complex and urgent issues that arise at this (and any) startup. Rootly has provided us the tooling to allow us to respond quickly, hold the organization accountable to remediation, and save time in trying to coordinate in a single-use/single-team slack channel. ### 43. Rootly simplifies our incident management **Rating:** 5.0/5.0 stars **Reviewed by:** Sean F. | Chief Information Officer, Mid-Market (51-1000 emp.) **Reviewed Date:** February 02, 2023 **What do you like best about Rootly?** Rootly makes incident management easier with it's Slack integration and they get the needs of a Saas platform incident management system. **What do you dislike about Rootly?** We've been loving it so far and haven't come across any issues yet. **What problems is Rootly solving and how is that benefiting you?** We do most of our comms and incident management on Slack anyway. Having Rootly deeply integrated with Slack meant that there was seamless communication between the teams during an incident and more focus can be put onto the resolution of the event rather than trying to update all stakeholders. ### 44. Fastest shipping SaaS team we buy from **Rating:** 5.0/5.0 stars **Reviewed by:** Scott K. | Engineer, Mid-Market (51-1000 emp.) **Reviewed Date:** August 31, 2022 **What do you like best about Rootly?** Rootly integrates naturally with all our tools: Slack, PagerDuty, Asana We actually had a homegrown bot that this replaced so changing was seamless. The single most impressive thing about Rootly is how fast they ship. At times we've reported a bug or feature request only to have it fixed live within 10-15 minutes. Sometimes it's the company's CEO pushing the fix. Love it! These are our kind of people. **What do you dislike about Rootly?** Nothing bad to say. They can keep upping the Asana integration to make our lives easier. **What problems is Rootly solving and how is that benefiting you?** We need to effectively run incident management. Doing this in Slack is totally natural for our team. They also have tools to help us manage follow-up processes like post-mortem reviews and action items. ### 45. A fantastic team making a great tool **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Financial Services | Mid-Market (51-1000 emp.) **Reviewed Date:** September 07, 2022 **What do you like best about Rootly?** Their responsive support and developer speed are unparalleled. And the comprehensive list of integrations makes Rootly a powerful enterprise tool. We regularly say to ourselves "it would be great if we could do X." Then pass along the feedback to the Rootly team - and much to our delight - we see our suggestion implemented within a few weeks! We are not seeing that level of responsiveness from most SaaS tools we've engaged. **What do you dislike about Rootly?** The workflow engine is powerful - almost too powerful. We have to make sure our workflows don't clash with each other and we have to do all that with sort of engineering principles or mental gymnastics. **What problems is Rootly solving and how is that benefiting you?** Originally we had 1 Slack workspace and a few integrations/workflows needed. That was handled by a competitor... adequately. Our business grew - the requirements and toolsets evolved and were no longer being met. Luckily, we had a great relationship with Rootly so we started the PoC up and found not only did Rootly meet all our tooling needs, but they had evolved well beyond one of the leaders in the space. Ultimately we needed a way for our company to create an Incident channel from any Slack workspace, spawn Jira tickets and run workflows during an incident, as well as engage any engineering on-calls needed at the moment. ### 46. Rootly - Incident Management **Rating:** 5.0/5.0 stars **Reviewed by:** Verified User in Apparel & Fashion | Mid-Market (51-1000 emp.) **Reviewed Date:** January 25, 2023 **What do you like best about Rootly?** Easy Incident Management from Slack Integrations with the latest tools in the market. Workflows are really flexible and useful to automate manual tasks with integrations. Faster Response from the Rootly team for any questions. Periodic product updates from the team **What do you dislike about Rootly?** Rootly can launch training modules/ videos to cover all the functionalities in their documentation Rootly Web UI can be better **What problems is Rootly solving and how is that benefiting you?** Easy for Oncall Engineers to collaborate with the team during the entire Incident lifecycle ### 47. Last mile logistics for incidents **Rating:** 5.0/5.0 stars **Reviewed by:** Zachary N. | Software Engineering Manager, Global Cloud Reliability, Observability, & FinOps, Enterprise (> 1000 emp.) **Reviewed Date:** September 07, 2022 **What do you like best about Rootly?** Rootly's integrations are great and the customization of automation via Workflows enables elite flexibility and cooperation once mobilized **What do you dislike about Rootly?** A bit more separation in the UI between types of automations would be useful. Once you have lots of Workflows, it can be a bit tricky to find a specific one. **What problems is Rootly solving and how is that benefiting you?** Rootly is a last mile logistical solution for us. Once an on call engineer is mobilized, rootly is used to drive collaboration and bring in various supporting roles into the incident. Automated postmortems save time and custom status pages help communicate the most appropriate info to internal stakeholders without overloading them with needless detail. ### 48. Highly configurable and shipping new feature requests all the time **Rating:** 5.0/5.0 stars **Reviewed by:** Joanne Ayesha H. | Group Engineering Lead (Reliability Platform), Enterprise (> 1000 emp.) **Reviewed Date:** April 12, 2022 **What do you like best about Rootly?** Rootly have been a pleasure to partner with since our initial point of contact. They were extremely supportive in our evaluation of the product, as well as throughout the migration from our in-house solution. Rootly's biggest advantage is probably that the product is highly configurable to fit your incident response process, and integrates with most existing tools. We didn't find this kind of flexibility with many of the other products we evaluated - they often required us to change our processes to fit their product. We've been using Rootly now for over 6 months, and I've been impressed with their responsiveness to all of our feature requests, often shipping them within a day or two. Whenever there were incidents or questions, we got a response very quickly. I've already recommended Rootly to another tech company, and they are also having a positive experience. **What do you dislike about Rootly?** There were a few bugs and clunky flows in the early days that needed to be ironed out. That said, Rootly promptly fixed them after being given the feedback. **What problems is Rootly solving and how is that benefiting you?** Rootly allows our engineers to focus on resolving incidents, rather than battling with tooling/process. It also means we no longer need to have engineers maintaining an in-house solution - we could never catch up to the number of features Rootly was shipping, and the ongoing operational load was significant. Rootly has features that support incident response best practices e.g. helping surface incident playbooks. We're now also moving incident data fields into Rootly instead of wrangling them from Jira, which has always been a huge pain. ### 49. Best-in-class for automation and flexibility **Rating:** 5.0/5.0 stars **Reviewed by:** Mathieu M. | Software Engineer - Reliability, Enterprise (> 1000 emp.) **Reviewed Date:** April 13, 2022 **What do you like best about Rootly?** Rootly provides best-in-class automation for manual admin work (e.g. creating Slack channels, tracking action items, postmortem timeline). It seamlessly integrates with our entire ecosystem of tools (Jira, Confluence, OpsGenie, Zoom...) making it very easy for us to plug into our workspace environment and onboard our staff. Rootly is also extremely flexible. Pretty much everything is configurable! That was one of the decisive factors when assessing multiple vendors: the incident response tool is fitting our internal processes and not the way around. Any changes to our internal response process can be easily & quickly implemented in a couple of clicks. Forget vendor lock-in, use the best tool for each task: postmortem in Confluence or Google Doc, Zoom for the war room... Rootly offers us flexibility unmatched on the market. Finally, Rootly team is responsive around the clock, any issue is quickly fixed, no question goes unanswered, and are collaborative in brainstorming solutions. Every time that we come up with ideas or feedback from our users, the team helps us to better define our request and come up with an elegant solution to solve our problem, either by leveraging existing features on the platform or by opening a new feature request (which never takes long to get rolled out!). Thanks to the team for listening to us and providing us advice on best practices and delivering improvements on a regular basis! As Site Reliability Engineer in charge of the incident response, there's no better way to start the day than seeing a notification for Rootly latest changelog. **What do you dislike about Rootly?** None that I can think of, the product is heading in the right direction and we are pleased to be using Rootly on a daily basis. **Recommendations to others considering Rootly:** Take the time to fully explore the product and make the most out of it. **What problems is Rootly solving and how is that benefiting you?** Rootly let us streamline our incident response process. Exit in-house solutions, welcome to the most flexible and open solution on the market, built and ran by a team of world-class experts. Incident Management just got a lot simpler. For example, our incidents now get immediate attention, the right persons are involved and we are finally able to track and reduce our MTTx metrics. ### 50. Incident management on auto-pilot **Rating:** 4.5/5.0 stars **Reviewed by:** Oliver W. | Head of Platform, Mid-Market (51-1000 emp.) **Reviewed Date:** April 12, 2022 **What do you like best about Rootly?** Rootly helps us automate all the manual work we had during incidents and anyone in the company regardless of experience can tackle critical incidents. For us it was essential that raising an incident was painless and the seamless Slack integration has made this possible. We weren’t looking at just another tool, we were looking for a true partner in this space and that is what we got. This was important because our incident management program was nascent and we needed a partner that can grow with us. The team at Rootly has been incredible as we’ve delivered a bunch of features. They were also the only solution on the market that supports Slack Enterprise Grid and had the security posture our regulated industry requires. **What do you dislike about Rootly?** While Rootly built the foundation for a great incident management process that works with all of our existing tools (Slack, PagerDuty, Jira, Zoom, etc) and helps us rapidly bring users up to speed, you still need a process in place like with any tool to teach users initially what incident management is. Rootly has a lot of features designed specifically for educating users i.e. tutorials, test incidents, etc. **Recommendations to others considering Rootly:** A great tool that is now heavily integrated into our platform and 'raising a rootly' is part of our lingo. Definitely worthy of consideration **What problems is Rootly solving and how is that benefiting you?** Before Rootly our incident management process was a checklist process responders relied on as they tackled incidents. Now, all of that is automated in a way that fits our process. Overall by having a consistent incident response process in place, we’ve managed to cut our avg resolution time and the tool has been adopted by > 90% of the organization. This has given us much better visibility into the true number of incidents, especially in areas that were previously more hidden ## Rootly Discussions - [What is Rootly - Manage Incidents on Slack used for?](https://www.g2.com/discussions/what-is-rootly-manage-incidents-on-slack-used-for) - [View Rootly pricing details and edition comparison](https://www.g2.com/products/rootly/reviews?section=pricing&secure%5Bexpires_at%5D=2026-05-13+09%3A28%3A32+-0500&secure%5Bsession_id%5D=f8417f68-5d02-4fbc-a804-23171db94228&secure%5Btoken%5D=aaba0fbb161b365714c1114605d10564685cc68412fb17a5f5ecba0863b9c93f&format=llm_user) ## Rootly Integrations - [Coda](https://www.g2.com/products/superhuman-coda/reviews) - [Datadog](https://www.g2.com/products/datadog/reviews) - [GitHub](https://www.g2.com/products/github/reviews) - [Grafana Labs](https://www.g2.com/products/grafana-labs/reviews) - [Jira](https://www.g2.com/products/jira/reviews) - [New Relic](https://www.g2.com/products/new-relic/reviews) - [Sentry](https://www.g2.com/products/sentry/reviews) - [Slack](https://www.g2.com/products/slack/reviews) - [Zoom Workplace](https://www.g2.com/products/zoom-workplace/reviews) ## Rootly Features **Monitoring** - Constant Monitoring - Timely Alerts - TIcket Accuracy - AI Monitoring **Management** - Configuration Management - Access Control - Orchestration **Reliability Objectives & Service Operations - AI SRE Tools** - Intelligent On-Call Workflows - Error Budget Tracking - SLI & SLO Management - Service Health Modeling & Reporting **Management Tools** - Ticket Assignment - Standardization - Lifecycle Visualization **Functionality** - Automation - Integrations - Extensibility **AI Detection & Signal Quality - AI SRE Tools** - Cross-Telemetry Correlation - Change-Aware Detection - Adaptive Anomaly Detection - Alert Correlation & Noise Reduction **Processes** - Pipeline Control - Workflow Visualization - Continuous Deployment **Generative AI** - AI Text Generation - AI Text Summarization **Investigation & Root Cause Analysis - AI SRE Tools** - Guided Incident Investigation - Live Debugging in Production - AI Root Cause Analysis - Runtime-Verified Root Cause Analysis **Agentic AI - Incident Management** - Autonomous Task Execution - Multi-step Planning - Cross-system Integration - Adaptive Learning - Natural Language Interaction - Proactive Assistance - Decision Making **Automation & Platform Controls - AI SRE Tools** - Automated Runbook & Workflow Execution - Human-in-the-Loop Remediation - Integration, APIs & Secure Access Controls - AI-Assisted Code Fix Generation ## Top Rootly Alternatives - [incident.io](https://www.g2.com/products/incident-io/reviews) - 4.8/5.0 (179 reviews) - [FireHydrant](https://www.g2.com/products/firehydrant-firehydrant/reviews) - 4.5/5.0 (141 reviews) - [PagerDuty](https://www.g2.com/products/pagerduty/reviews) - 4.5/5.0 (903 reviews)