Rootly

What do you like best about the product?

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 the product?

We have no issues so far, Rootly just works with minimal admin.

What problems is the product solving and how is that benefiting you?

Rootly is currently being used for our on-call security incidents solution.

What do you like best about the product?

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 the product?

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 the product solving and how is that benefiting you?

Incident Management
On-Call Management
Paging
Alert routing
Incident Retrospectives / Post mortems

What do you like best about the product?

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 the product?

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 the product 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.

What do you like best about the product?

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 the product?

No major downsides—occasional minor UI improvements would be nice, but the team iterates quickly!

What problems is the product 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.

What do you like best about the product?

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 the product?

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 the product 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.