The Slack Integration is pretty great, we get timely notifications. Review collected by and hosted on G2.com.

Login service could be improved on, it's usually slow. Review collected by and hosted on G2.com.

It is capable of being integrated with multiple platforms, such as Slack and Jira. Review collected by and hosted on G2.com.

I do not have anything from my own, but some coworkers do not like the number of notifications, for instance, migrating a conversation from a regular channel to the Slack firehydrant incident channel. Review collected by and hosted on G2.com.

- configurable alert routing

- configurable how alert is displayed on your communication device/app.

- easy to create/manage incidents from alerts (all in one shop for incident management and alerting)

- Best customer support experience in whole IT industry, they listen to your bug/feature requests and deliver them at amazing speed. Review collected by and hosted on G2.com.

None. I can't think of any issues/problems with this product. Review collected by and hosted on G2.com.

Easy to use, Robust Solution and has integration with most popular Software tools, Firehydrant team is also very supportive. Review collected by and hosted on G2.com.

As teams grow and need advance features across the board, pricing can escalate quickly Review collected by and hosted on G2.com.

One stop shop for all incidents management needs. Review collected by and hosted on G2.com.

Lack of complete customization and flexibility Review collected by and hosted on G2.com.

-Runbook automation

-UI is easy to use

-Number of features Review collected by and hosted on G2.com.

Analytics can be improved. However, new features are being added consistently. Review collected by and hosted on G2.com.

At its core a solid Incident Management platform that now has great alerting capabilities. Review collected by and hosted on G2.com.

There are some features missing from the platform due to it being younger than other ones like Pager Duty. But the company is moving fast and new features are coming all the time. Review collected by and hosted on G2.com.

For context, I've built a Slack Bolt App which utilizes data from Blameless to keep both Engineering and Support in-sync during an incident. The triggers were easy enough to setup to kick off the app and seamlessly start pulling data from Blameless. Long story short; my app uses Blameless for everything.

The API documentation overall was pretty easy to read and integrate into my app and I feel like that's saying a lot since I've been coding for less than 6 months and am self taught.

Also, the support I received from the Blameless team (especially Kim!) was incredible. The response time from the team has been exceptional and the attention to detail was outstanding!

I also appreciate the fact that querying exists in Blameless. It has been helpful for the Support team to measure our time costs while managing incidents. Review collected by and hosted on G2.com.

While querying previous data for incidents is helpful for the Support team, I will say that the experience querying hasn't been the easiest. Moreso that using SQL querying isn't as straightforward about limitations and the documentation also seems a bit sparse.

I've been using ChatGPT to help build out some query statements, but most of the time Blameless isn't aware of the function so sometimes I feel like I have to take that data with a grain of salt if something is returned.

With that said, I still regularly utilize the Insights Dashboards I've created and we do consider them accurate. Review collected by and hosted on G2.com.

Firehydrant has filled nearly every gap that we experienced in the past with incident management. From day one transitioning to FireHydrant, they have proved to be a great investment and improvement over our previous product. Firehydrant has freed my team to spend time on improving processes rather than fighting the incident process itself. Review collected by and hosted on G2.com.

I wish Firehydrant had a better maintenance product. We have not moved our organization to Firehydrant for our maintenances because there is no way to plan and discuss in a dedicated channel prior to the start of the maintenance. This makes planning for such events much more difficult to the point where we still use an in-house built tool to run our maintenance. Review collected by and hosted on G2.com.

We've been using FireHydrant for a little over a year. Just recently, one of my teammates told me they couldn't imagine not having FireHydrant. This speaks to how impactful it has been in our organization. With our automation, we are able to collect incident response details in a single place (incident Slack channel), report updates to key stakeholders for compliance purposes, and, because the incident details are all in one place, it makes retrospectives much easier to perform. FireHydrant gets used regularly for responding to incidents and for retrospectives.

We are trying out Signals now and are excited about using an on-call rotation and scheduling product that's still being actively developed. Our current provider has not made significant updates in years and has settled into maintenance mode.

FireHydrant's Customer Support has been extremely helpful. Shoutout to Sydney who regularly fields questions we have and helps us accomplish some workflows that were complex. Review collected by and hosted on G2.com.

A lot of automation exists, but we still find ourselves limited by some of the constraints in what triggers an automation step. We are also working with our Business Intelligence team to pull data into our data warehouse so that we can analyze it better. The reporting in FireHydrant isn't as good as we needed, but at least they make it easy to get to the data. Review collected by and hosted on G2.com.