Reviews from AWS Marketplace
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
External reviews are not included in the AWS star rating for the product.
Incident.io has helped us get incidents under control. What more could you want?
What do you like best about the product?
The team are excellent - they're in the early stages of delivery, and so while not everything is perfect they are incredibly diligent at gathering, responding to and actioning feedback. Nothing better than a "hey, good idea, we've rolled that idea out onto production" an hour after you make a suggestion.
Beyond that, it's just a good tool. It's clearly well built, well thought out, the team have oodles of incident experience and so it helps us run incidents better - whether they're big incidents or just little incidents that need coordination.
Beyond that, it's just a good tool. It's clearly well built, well thought out, the team have oodles of incident experience and so it helps us run incidents better - whether they're big incidents or just little incidents that need coordination.
What do you dislike about the product?
The thing that I dislike I understand they're about to fix - which is that incidents are "one size fits all". I think it's a bit tricky to differentiate between incidents which are security incidents vs. human errors vs. pure engineering issues. A bit more delineation between those would be very helpful (but I understand they're building it anyway - so ask me again in a couple weeks!).
Aside from that, I think some of their product is evidently work in progress - but I refer above to the "what do I like best" part: they always respond, quickly, and always have good ideas. It might not be for everyone if you're looking for something where you know everything is going to be in the same place when you come back next week. That's ok for us, but it might not be for you.
Aside from that, I think some of their product is evidently work in progress - but I refer above to the "what do I like best" part: they always respond, quickly, and always have good ideas. It might not be for everyone if you're looking for something where you know everything is going to be in the same place when you come back next week. That's ok for us, but it might not be for you.
What problems is the product solving and how is that benefiting you?
When an issue or problem occurs, we need to get a team together to tackle it and solve the problem. Previously, we did this by jumping into Slack channels and relying on memory to invite certain people.
Since adding Incident.io we've had significantly _more_ incidents because it's now easy for people to create them, there's no burden to creating them, and they're a quick and easy way of coordinating a group of people to tackle a problem.
We started using this just in the engineering team, but tomorrow we're rolling out a company-wide incident management process and Incident.io will be part of it. If they can just replace the need for Pagerduty, I'll be even happier.
Since adding Incident.io we've had significantly _more_ incidents because it's now easy for people to create them, there's no burden to creating them, and they're a quick and easy way of coordinating a group of people to tackle a problem.
We started using this just in the engineering team, but tomorrow we're rolling out a company-wide incident management process and Incident.io will be part of it. If they can just replace the need for Pagerduty, I'll be even happier.
- Leave a Comment |
- Mark review as helpful
A terrific off-the-shelf solution for Slack-centric teams
What do you like best about the product?
Incident.io was critical in conceptualizing and launching our first formal incident response program. The tool aligns well with modern incident response management practices, providing enough flexibility within its framework for us to tune it to our own needs without needing any specialized technical support. The tool does what it says on the box and we've been very happy onboarding and training our teams to use it over the last year or so.
While the tool is great, it's worth noting that the team at Incident.io has been fantastic to work with. They've been open to feedback, implemented functionality we've requested, and are seemingly always available to help when needed.
While the tool is great, it's worth noting that the team at Incident.io has been fantastic to work with. They've been open to feedback, implemented functionality we've requested, and are seemingly always available to help when needed.
What do you dislike about the product?
Dependence on Slack for managing incidents is a bit of a burden when Slack breaks which hasn't been too big of an issue for us but one to consider. Some data and reporting functionality needs improvement but given the roadmap and opportunities it's understandable. There has been nothing show stopping for us using Incident, mostly nits and picks.
What problems is the product solving and how is that benefiting you?
Managing and executing on service and product outages, communicating internally and externally, providing visibility and aligning teams on the problem, solution path, and timeline to resolution.
incident.io is incredibly helpful for taking hassles out of our incident response
What do you like best about the product?
incident.io has enabled some robust workflows for us as we manage incidents; I think the moment it clicked for me was when I received a page while walking my dog and was able to spin up an incident, co-ordinate folks internally, and manage comms on our StatusPage all from my phone before I could even get back inside.
What do you dislike about the product?
There's not much to say here; we had a few missing features early on that we were able to work around but the team at incident.io has been receptive to feedback and works quickly to turn around changes.
What problems is the product solving and how is that benefiting you?
incident.io has helped us standardize our incident response process across teams with common workflows and practices; it's also helped us track followups effectively after incidents are remediated.
The best UX around
What do you like best about the product?
Incident.io have unmatched user experience. Their Slack integration is so intuitive that I didn't need to explain anything to my colleagues before they were full converts. I simply told them to use it and they did. We've only been using incident.io for a month and they are already so core to how we manage incidents that we wholly depend on them, and I ain't bothered by that.
What do you dislike about the product?
Their pricing model adds unnecessary friction. We have to restrict our use of the tool to prevent high bills for team members who only use the tool a few times a month. Please change this 🙏
What problems is the product solving and how is that benefiting you?
We now effortlessly manage incidents via a Slack-first approach. Beforehand all our incidents were managed ad-hoc in various Slack channels, which become unmanageable. Incident.io's tool has next to no friction which is important when everything's on fire at 2 in the morning!
Awesome incident.io features => my team focuses 100% on mitigating and introspecting on incidents
What do you like best about the product?
Continuously improving and evolving features that greatly reduce the cognitive load for our entire engineering team, whether in preparing for, managing, or introspecting on incidents.
What do you dislike about the product?
Users who don't regularly use the tool may not remember all the Slack features, and jumping between the slack UX and the web UX is a little clunky for infrequent users.
I use dark mode and the visibility of buttons with suggested actions is not too clear to me.
I use dark mode and the visibility of buttons with suggested actions is not too clear to me.
What problems is the product solving and how is that benefiting you?
Allowing any engineer to orchestrate incident response, because we set the roles, workflows and PagerDuty&Statuspage integrations in advance during fair weather.
This brings consistency in incident mitigation and keeps all informed. Post-incident introspection is also orders of magnitude easier since we have a record in Slack of the actions and observations of the team.
This brings consistency in incident mitigation and keeps all informed. Post-incident introspection is also orders of magnitude easier since we have a record in Slack of the actions and observations of the team.
Incident.io helps our team focus on solving the incident by streamlining coordination overhead
What do you like best about the product?
All hooks from Slack feed into the Incident platform. No need to change your communication behavior.
What do you dislike about the product?
I would love if Incident offered a Statuspage and Pagerduty alternative in one. I would instantly switch.
What problems is the product solving and how is that benefiting you?
We have been able to operationalize around incidents much faster. This has allowed us to reduce our mean time to remediation by at least half.
Excellent incident management for SaaS and SlackOps-centric organisations
What do you like best about the product?
Very smooth workflows that allows everyone to stay in the communication tool we use the most (Slack). Integrates well with some of our other SaaS tools.
What do you dislike about the product?
Not much. Functionality might not yet match what some larger competitors have yet, but they are releasing quality functionality at high a pace.
What problems is the product solving and how is that benefiting you?
An easy to use and collaborative incident management process. The team all instinctively know what to do.
showing 141 - 147