Manhattan, NY, USA
Sep 14, 2021   |  By Julia Tran
Quickly and efficiently manage your incidents with FireHydrant and Backstage!
Sep 14, 2021   |  By Christine Yi
We’re proud to announce that our front end FireHydrant plug in has been open-sourced as part of Backstage, an open platform for infrastructure tooling, services, and documentation created at Spotify. We introduce FireHydrant’s incident management and analytics in Backstage, where you can quickly and efficiently manage your incidents.
Sep 2, 2021   |  By Max Tilka
Coming to this article you may be in two learning mindsets. You’re curious about building a service catalog and want to know some of the basics. Or you’re curious about FireHydrant’s philosophy around this growing space.
Sep 2, 2021   |  By Julia Tran
We've had a jam-packed year and it's only September. Here are some of the product releases we’ve had to date, from new features to updates for incidents, integrations, Runbooks, and more. Keep reading to see what’s new and improved with FireHydrant and what you can leverage for your team.
Aug 16, 2021   |  By Robert Ross
Site Reliability Engineer (SRE) is one of the fastest growing jobs in tech, with Linkedin reporting 34% growth YoY in 2020 and over 9000 openings in their Emerging Jobs Report. If you’re new to SRE and exploring it as a career path, understand that it can be a challenging but rewarding experience. Here are some quick tips on how you can get started with SRE and jump-start a rewarding career.
Aug 10, 2021   |  By Robert Ross
At FireHydrant, we envision a world where all software is reliable, and we’re on a mission to help every company that builds or operates software get closer to 100% reliability. Today, we’re thrilled to announce that we’ve raised $23 million to help us further our goal.
Jul 15, 2021   |  By Robert Ross
In my past experience as an SRE I’ve learned some valuable lessons about how to respond and learn from incidents. Declare and run retros for the small incidents. It's less stressful, and action items become much more actionable. Decrease the time it takes to analyze an incident. You'll remember more, and will learn more from the incident. Alert on pain felt by people — not computers. The only reason we declare incidents at all is because of the people on the other side of them.
Jun 10, 2021   |  By Robert Ross
“Mean time to X” is a common term used to describe how long, on average, a particular milestone takes to achieve in incident response. There’s mean time to detect, acknowledge, mitigate, etc. And then there’s the elusive “mean time to recover,” also known as “MTTR.” MTTR, a hotly debated acronym and concept, measures how long it takes to resolve an incident on average. The problem with MTTR, though, is that it doesn’t matter.
May 27, 2021   |  By Julia Tran
With 50% of the US adult population vaccinated, there’s a lot to look forward to this summer, life no longer feels like it’s on hold, and we’re fully embracing that. Get your fire hoses ready, 'cause extinguishing incidents just got easier. We’re rolling out a summer full of new integrations, product releases, events, and more.
May 26, 2021   |  By Daniel Condomitti
When you’re feeling the stress and pain around incidents, making the decision to find an incident management tool is a no-brainer. But how do you choose the one that will work for you, your team, and your business? You might be asking yourself: Where do I start? What do I need to know? What questions do I ask? What are the options? How can I be sure we’re choosing the right tool?
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.
Sep 29, 2020   |  By FireHydrant
FireHydrant CEO, Robert Ross, demos the FireHydrant platform during Chaos Conf 2020.
Jun 25, 2020   |  By FireHydrant
How to declare an incident on FireHydrant using our Slack integration.
Jun 25, 2020   |  By FireHydrant
A tutorial on setting up Incident Runbooks within FireHydrant.
Jun 25, 2020   |  By FireHydrant
Apr 29, 2020   |  By FireHydrant
Take a quick tour of our product with me. We'll create an incident, see our SEV1 runbook kick off, and triage and eventually create a retrospective report.
Jan 29, 2020   |  By FireHydrant

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.