FireHydrant

Manhattan, NY, USA
2017
Jun 29, 2022   |  By Robert Ross
The first few minutes of an incident are often the hardest. Tension and adrenaline levels are high, and if you don’t have a well-documented incident management plan in place, mistakes are inevitable. It was actually the years I spent managing incidents without the right tools in those high-tension moments that inspired me to build FireHydrant. I built the tool I wished I’d had when I was trying to move fast at the start of incidents.
Jun 27, 2022   |  By Dylan Nielsen
It’s been a busy month at FireHydrant. We’ve had our heads down shipping loads of improvements across the platform, and I want to take you on a quick tour of the changes. At the core of all these updates is a common theme: things are now a heck of a lot more intuitive. There’s a lot to digest here; read the full roundup of June releases below or follow us on Twitter for a bite-size demo each day this week.
Jun 24, 2022   |  By Robert Ross
I recently published a couple of blog posts about what happens when you invest in a thoughtful incident management strategy and three first steps to take to do so. What I’m getting at in these posts is that we need a shift toward proactivity in the software operators community. I’d wager most of the world is responding to incidents as they happen, and nothing more.
Jun 21, 2022   |  By Ryan McDonald
There are a number of lessons I learned guiding weeks-long backcountry leadership courses for teens that I carried with me into my roles in incident management. In this blog post, I’ll share three that stand out.
Jun 9, 2022   |  By Robert Ross
Too many of us are still playing whack-a-mole when it comes to incidents: an incident is declared, the on-call engineer is paged, the incident is resolved and then forgotten — until next time. It’s time to start thinking in terms of proactive incident management, not just reactive incident response.
May 25, 2022   |  By Malcolm Preston
At a going away party from a job I was leaving a few years back, my VP of engineering told a story I didn’t even remember but that I know subconsciously shaped how I viewed my role on that team: Toward the end of my very first day at the company, there was some internal system issue, and with pretty much zero context, I pulled out my laptop, figured out what was going on, and helped fix the issue.
May 18, 2022   |  By Robert Ross
Inflation is running rampant, the world stage is unpredictable, and what’s happening in the U.S. markets has been dubbed the “tech wreck.” A common theme I’m hearing come up in conversations across industries right now is value — we’re all looking to maximize every dollar spent, every hire made, every hour logged. For a lot of companies, this means looking at processes and tools with a critical eye for not only cost savings but also cost avoidance.
May 17, 2022   |  By Michelle Peot
Previously, FireHydrant supported video collaboration tool integrations for Zoom and Google Meet. In response to customer asks, today we are pleased to introduce our new Cisco Webex Meetings integration for all paid plans. With the new integration, teams can automate Webex bridge creation as part of incident response.
May 10, 2022   |  By Robert Ross
True reliability takes into account all of the services that exist in your software environment — which is why it can get so complicated. An ecommerce site, for example, might have services that update current inventory in near real time, process payments in the shopping cart, trigger email receipts to send, kick off fulfillment orders, etc. And if one of these services isn’t operating at its best, that can mean money — and in some cases, customers — lost for the company.
Apr 27, 2022   |  By Michelle Peot
When FireHydrant originally launched our Jira Cloud and Jira Server integrations, we did not support custom fields. This prevented customers who rely on Jira epic ticket types or other custom required fields from getting full value from our Jira integrations. That has changed with the launch of Jira custom field support. We now support the most common type of Jira epic tickets and field-level mapping of Jira custom fields with FireHydrant incident data.
Jan 22, 2022   |  By FireHydrant
In this demo we'll look at how FireHydrant can solve the pains of quickly declaring and managing an incident, all from Slack.
Sep 26, 2021   |  By FireHydrant
See how FireHydrant can help you achieve better reliability, get to resolution, and back to bed quicker.
Aug 11, 2021   |  By FireHydrant
FireHydrant is the only comprehensive reliability platform that allows teams to achieve reliability at scale by creating speed and consistency across the entire incident response lifecycle.
May 12, 2021   |  By FireHydrant
Our friends Felicia Day, Steve Wozniak, and Brian Baumgartner help us explain what the heck incident management is. FireHydrant is the only comprehensive incident management platform that allows you to create consistency for the entire incident response lifecycle to focus on fighting fires faster. From alert to retrospective, tracking, communicating, and reporting on results: FireHydrant will automate the process so you can focus on resolution. Visit firehydrant.io to learn how you can manage the mayhem.
Mar 10, 2021   |  By FireHydrant
In this video, FireHydrant CEO and Co-Founder, Robert Ross, shares his thoughts and experience on why putting your APIs first can be a game-changer for your business and how it can pay dividends in the long haul.
Jan 5, 2021   |  By FireHydrant
We’re pretty sure using a real incident to test a new response process is not the best idea. So, how do you test your process ahead of time? In this video, FireHydrant CEO, Robert Ross, will share how FireHydrant customers leverage best practices to break, mitigate, resolve, and fireproof incident processes. We’ll show you how to use chaos engineering philosophies to stress test 3 critical parts of a great process.
Dec 7, 2020   |  By FireHydrant
FireHydrant is the incident management platform that allows you to resolve, learn, and mitigate incidents faster. Learn more at firehydrant.io
Oct 15, 2020   |  By FireHydrant
We’re pretty sure using a real incident to test a new response process is not the best idea. So, how do you test your process ahead of time? In this video, FireHydrant CEO, Robert Ross, will share how FireHydrant customers leverage best practices to break, mitigate, resolve, and fireproof incident processes. We’ll show you how to use chaos engineering philosophies to stress test 3 critical parts of a great process.
Oct 13, 2020   |  By FireHydrant
You can use chaos engineering to test processes as much as you can test how systems fail.
Sep 29, 2020   |  By FireHydrant
FireHydrant CEO, Robert Ross, demos the FireHydrant platform during Chaos Conf 2020.

Utilize SRE best practices using FireHydrant’s incident response platform to organize, investigate, and remedy faster.

FireHydrant helps teams respond to service disruptions easily and effectively. By allowing teams to “rally the troops” with only a few clicks and assign incident roles to responders, responsibilities are quickly defined and allow people to focus on what matters: restoring service.

Organize, Investigate, Remedy and Prevent faster with FireHydrant:

  • Teams: Fill out your SRE roles and assign members to instantly delegate responsibility in an incident. Assign who owns what components to get the right people on the job.
  • Slack Integration: If you're using Slack, FireHydrant gets even better. Quickly open incidents, notify other channels, and assemble your team easily all without leaving Slack.
  • The Service Catalog: Keep a catalog of your environments and the things running in them with our service catalog feature. Make it easy to quickly find all of the gears of your product.
  • The Changelog: Fire's typically start when something changes. That's why we offer a one stop shop for you to log all of the change occuring in your stack.
  • Incident Logs: While you're fighting a fire, FireHydrant will transparently keep track of changes and Slack chat in your incident log automatically. You can easily filter notes and chat as well.
  • Post mortem: Easily access all prior incidents with fine grain filtering to help make actionable changes to keep your system robust.