Rootly - AI Native OnCall and Incident Response Platform

My main use case for Rootly is on-call alerts. In my use case for on-call alerts, we plug into various applications using Rootly's out of the box plugins. If an alert triggers, Rootly is then responsible for alerting the engineer and it has all the paperwork as well that follows the incident.

Rootly has positively impacted my organization because before Rootly, we were missing alerts due to our legacy tool that was unable to call out engineers effectively. We occasionally missed alerts, but now we have achieved a 100% success rate of alert delivery, which is a massive step especially when trying to fix and identify these problems.

Regarding metrics or specific outcomes, we do not have noisy on-call alerts, but I would say we missed about three alerts a month previously, whereas now we miss zero.

The best feature that Rootly offers, which I really appreciated when we onboarded Rootly, is the shadowing feature. I evaluated quite a few tools but Rootly was the only one at the time that had this, and this allowed us to onboard new engineers into the on-call rota smoothly, which was a really cool feature.

Regarding how the shadowing feature helped with onboarding new engineers, rather than manually tweaking schedules to try to hack a way to shadow existing engineers, Rootly gave us a shadow feature which allowed us to say person X, please shadow person Y, using these times and these days, very customizable, and it allowed us to onboard people in a much more graceful manner.

The team at Rootly seems to always be adapting and looking at what the market is doing and adding new features, so for us, Rootly currently fits the bill. If there was something we needed, we could reach out to the team at Rootly and they would add it to their roadmap. I do not think there are any improvements needed for Rootly that I haven't already mentioned; overall, I am really happy with the product.

I have used Rootly for about two years.

Rootly is stable, and I have had no issues.

Rootly's scalability is fine; we are easily able to add new alerts. We manage our configuration by Terraform, which is a big touchpoint for us. If we ever need to add a new alert, we just put it into the code, run the pipeline, and we are done. The same applies for adding people; it is very easy.

Rootly's customer support is great; every time we have had to use it, they have gotten in touch with us really quickly and connected us to the relevant teams to fix our problems or potentially suggest a feature for the future. I would rate Rootly's customer support a 10, as there are no issues whatsoever.

We previously used Jira, the Atlassian suite. We switched because if we wanted the phone feature, we would have had to upgrade the whole organization's license to a premium license and that became very costly.

I am not certain about specific metrics, but we do not miss alerts anymore, so you could use that as a metric that it has effectively increased our reliability when handling incidents.

My experience with pricing, setup cost, and licensing was really easy. Rootly scheduled a call with us and was very quick to give us a POC license to trial out the full product. They were not pushy and we were able to have calls as and when needed, which was really good and we were able to onboard the tool quite efficiently.

Before choosing Rootly, we evaluated other options, including PagerDuty and Atlassian's premium version, along with Rootly.

I would rate Rootly a nine on a scale of one to ten. I give it a nine because nothing is perfect and there are always improvements that can be added. We have not used Rootly's AI capabilities yet. My advice to others looking into using Rootly would be to get in contact with them and try to get a POC set up because it speaks for itself; it is a brilliant tool. I am providing an overall review rating of nine for Rootly.