Rootly Reviews & Product Details

Rootly integrates seamlessly with many commonly used monitoring tools. We are currently having most of our alerts coming from Prometheus. Rootly helps us manage all those in quick and easy way, integrates seamlessly with Slack and enriches the alert with helpful info like Runbook links etc. for on call folks to triage quickly. The UI is feature rich yet easy to navigate. I, myself have exported over 10K alerts over last month for analytical purpose and the performance is on par. The AI features are cherry on top but we are yet to fully utilize those. Review collected by and hosted on G2.com.

Not an issue as such but I feel routing alerts to different Slack channels. services and escalation policies have steep learning curve of their own. There are multiple ways to route the same alert and it sometimes confuses me whether to use a routing rule using Prometheus labels, or to use service with default Slack channel set to route the alerts. Review collected by and hosted on G2.com.

Rootly Oncall escalation methods have changed the game when it comes to prioritizing incidents the right way. The alerts are also used by the respective teams in a self-serve manner. Engineering teams can update their workflows, and the on-call rotation is updated in the UI without difficulty in the alerting system based on the impacted product module. Integration with Datadog has been a game changer. Compared to couple of years back lot of performance has been changed in terms of analytics and usage. Support over slack has been always amazing with their swift responses. Their AI features have made our lives easier without spending hours on knowledge transfer. Review collected by and hosted on G2.com.

Reporting feature has less customization. I wouldn't say I don't like it, but it could be more better. Review collected by and hosted on G2.com.

Rootly’s On-call and Incident Response platform helped us consolidate several disparate platforms into one unified solution. Previously, we had to stitch an incident’s lifecycle across separate tools—one for alerting and paging, another for coordinating the response, and others for status updates and retrospectives. Now we can run that entire path end to end in a single, modern system.

Beyond the product itself, Rootly’s support has been exceptionally responsive. When we need help, we get quick, knowledgeable answers, which made rolling out features like Advanced Alert Routing feel much lower-risk. Review collected by and hosted on G2.com.

The main area with room to grow is the documentation. At times it has lagged behind the product, and I’ve had to confirm a detail directly in the API instead of finding it clearly written down. That said, it’s improving every day and the gaps are closing quickly, so it feels more like a fast-moving product than a genuine pain point. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

There are so many options that it can feel overwhelming at first, but the flexibility is worth it. Review collected by and hosted on G2.com.

Rootly stands out compared to other incident management vendors we evaluated thanks to how complete and polished the feature set is out of the box incident workflows, status pages, postmortems, and Slack-native incident channels all feel like they were designed together rather than bolted on. The UI is intuitive enough that engineers adopt it without much training, which isn't always true of similar tools.

Support has also been a highlight responsive, knowledgeable, and quick to help troubleshoot configuration issues or answer questions about best practices, rather than just pointing us to documentation.

Finally, the official Terraform provider makes it easy to manage our incident workflows, services, and configurations as code, which fits naturally into our existing infrastructure-as-code practices and makes changes auditable and repeatable across environments. Review collected by and hosted on G2.com.

Nothing in particular comes to mind, it's been a solid experience overall. Review collected by and hosted on G2.com.

The Slack-native workflow is the standout feature. Declaring an incident, paging the right people, and tracking the timeline all happen inside the channel we’re already working in, so there’s no context switching during a live incident. Before Rootly, our incident response was scattered across ad-hoc Slack threads, manual paging, and someone frantically trying to reconstruct a timeline after the fact for the postmortem. That led to lost context, slower coordination, and inconsistent follow-through on action items. Rootly addresses this by giving us a single, structured workflow for the entire incident lifecycle: it reduces the time it takes to get the right people engaged, maintains a reliable running record of what happened as it happens, and removes much of the manual burden of writing postmortems from scratch. Review collected by and hosted on G2.com.

The initial setup of workflows and integrations (on-call tooling, alerting, status pages) takes some upfront investment to get configured exactly the way our team wanted to Infrastructure as Code, and the sheer number of customization options can be a bit overwhelming at first. Review collected by and hosted on G2.com.

The best thing about Rootly is that it gives teams one place to manage the full incident lifecycle — on-call, incident response, retrospectives, and status pages — instead of juggling separate tools.

Why that’s valuable:

- It reduces context switching for responders.

- It creates a single source of truth for incident data.

- It uses automation and AI for things like investigations, summaries, timelines, and surfacing relevant docs.

- It integrates with tools teams already use, like Slack, Jira, Datadog, Microsoft Teams, and Zoom.

So, in short: Rootly’s biggest strength is making incident response faster, more coordinated, and less manual. Review collected by and hosted on G2.com.

Rootly is useful overall, but some workflows still feel transitional — for example, COE/postmortem work may still need to continue through Jira until the fuller Rootly process is rolled out. Review collected by and hosted on G2.com.

Rootly stays as my favourite Slack integration. It's easy to navigate and customization is limitless. I really like how easy it is to setup Rootly integration since a lot of settings have been moved behind feature flags (on/off toggles).

We are actively using Rootly On Call features and it's been integrated across our entire organization as the primary on-call system without any issues. Along with that is a very modern looking mobile app, which is very easy to use for Engineers as well as Incident Management Teams.

Rootly Support system has remained as something I'd like to highlight. Their response times are fast and customer satisfaction is a priority. I've only had pleasant experience with Rootly. Review collected by and hosted on G2.com.

Since my last review Rootly has gone through major improvements. I'm very pleased with how easy it is to navigate the workflow and various settings/automations etc. The big challenge for all Incident Management products and Rootly is to integrate more AI features and functionalities into their product. We've already seen multiple of these features come out and are eagerly waiting to try out more! Review collected by and hosted on G2.com.

The slackbot is slick, gives a simple overview to anyone joining and means most users never need to head into the WebUI. This means that users can focus on one communication stream to manage the event, and that stream works for all users (remote and office-based) equally. Review collected by and hosted on G2.com.

Not so much a downside, but there are features we don't use (yet) - we have so much alert noise, that we haven't dared to turn on "automatic incident creation". I'd also love to see a management summary that gets sent only to nominated users for the past month. Review collected by and hosted on G2.com.

What I like best about Rootly is that it has become the central platform for our entire incident management process. We rely on it for incident ticketing, on-call management, and incident coordination, making it our single source of truth during critical events. The platform is intuitive, highly reliable, and has consistently delivered excellent uptime, which is essential for a business-critical application.

Another standout feature is its reporting capabilities. I use Rootly's reports every month to provide incident metrics and insights to management, helping us track operational performance and identify trends.

The Rootly support team has also been exceptional. On the rare occasions we've encountered issues, they've been highly responsive, proactive, and collaborative in resolving them quickly. Their commitment to customer success gives us confidence that we're well supported.

Overall, Rootly has become an indispensable part of our operations, and I would highly recommend it to any organization looking for a reliable, full-featured incident management platform. Review collected by and hosted on G2.com.

At this point, I don't have any significant dislikes about Rootly. It has been a reliable platform that consistently meets our incident management needs. If I had to suggest an area for improvement, it would be continuing to enhance reporting and dashboard customization to provide even greater flexibility for different teams and management audiences. However, this is more of a nice-to-have than a limitation, and it has not impacted our overall experience with the platform. Review collected by and hosted on G2.com.