Rootly
RootlyReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
54 reviews
from
External reviews are not included in the AWS star rating for the product.
Rootly's solid API makes it a good tool for power users
What do you like best about the product?
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.
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 the product?
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.
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 the product 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.
Rootly allows us to keep IR organized and reduce confusion, which is particularly valuable when time is of the essence.
Versatile and highly configurable incident management automation
What do you like best about the product?
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.
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 the product?
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 the product 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.
Incident Management tool for everyone!
What do you like best about the product?
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!
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 the product?
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 the product 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.
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.
Powerful incident management tool
What do you like best about the product?
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.
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 the product?
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.
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 the product 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
Giving more transparency in the company and providing clear view on areas need to improve and measure end results
Fast ROI and easy to get started!
What do you like best about the product?
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.
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 the product?
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 the product 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.
Incredible turn-key incident management tool!
What do you like best about the product?
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.
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 the product?
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 the product 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.
Incident management
What do you like best about the product?
Ease of use - ability to quickly configure, setup, and onboard your teams. Speed of adoption and was easy for anyone to get started.
Measurable results - quantifiable improvements to resolution time, repeat incidents, engineering hours spent, etc.
Configurability and flexibility - could use existing stack and tools in place already, integrations met all needs, and customizable Workflows helped fit our exact incident process.
Measurable results - quantifiable improvements to resolution time, repeat incidents, engineering hours spent, etc.
Configurability and flexibility - could use existing stack and tools in place already, integrations met all needs, and customizable Workflows helped fit our exact incident process.
What do you dislike about the product?
Rootly solves our basic need of incidents, it would be great to continue influence their roadmap as our need grows in the future.
What problems is the product solving and how is that benefiting you?
Manual admin work (e.g. creating Slack channels, tracking action items, postmortem timeline) is now automated. It saves our team time so they can focus on the work that actually moves the needle for our business
Easily the best solution out there
What do you like best about the product?
Rootly is incredibly easy to use. We love the integration with Slack and intuitive UI / UX especially.
We've tried a bunch of other solutions but none came close - others had clunky UX or forced us to work in another tool rather than the ones were already in day to day.
In a world in which an incident can be incredibly costly, both from a revenue and reputational perspective , it brings our team a lot of peace of mind to be able to rely on Rootly.
We've tried a bunch of other solutions but none came close - others had clunky UX or forced us to work in another tool rather than the ones were already in day to day.
In a world in which an incident can be incredibly costly, both from a revenue and reputational perspective , it brings our team a lot of peace of mind to be able to rely on Rootly.
What do you dislike about the product?
Nothing yet! We've had some constructive feedback and the team addressed it right away - awesome customer support.
What problems is the product solving and how is that benefiting you?
Helping us lresolve incidents faster and avoid them going forward
Last mile logistics for incidents
What do you like best about the product?
Rootly's integrations are great and the customization of automation via Workflows enables elite flexibility and cooperation once mobilized
What do you dislike about the product?
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 the product 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.
A fantastic team making a great tool
What do you like best about the product?
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 the product?
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 the product 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.
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.
showing 21 - 30