What is FireHydrant?

FireHydrant is an incident management platform that helps ensure consistent process and provides insights and traceability for incident data.  FireHydrant integrates with your existing tools to automate manual tasks throughout the lifecycle of an incident, and helps bring your entire organization together to put out fires faster.

Why use FireHydrant?

FireHydrant helps your teams:

  • Automate manual tasks such as creating a Slack channel, Jira ticket, Zoom bridge or Google Meet
  • Respond to and resolve incidents faster
  • Keep track of your apps, services, environments, and their relationships
  • Orchestrate around a standard incident management process
  • Maintain traceability of incident management data, communications, and action items
  • Learn valuable lessons from your incidents, and use that knowledge to improve your infrastructure and processes

Key components


Runbooks are what make FireHydrant unique and powerful. Say goodbye to wikis and endless static playbooks. FireHydrant enables you to automate your processes, including step execution with conditional logic. With FireHydrant Runbooks your team can stay focused on fighting fires instead of reading documentation.


FireHydrant incidents trigger your Runbooks to execute in FireHydrant. They can be created through the FireHydrant UI, through a Slack command, through our API, or through integrations. Incidents signify that something is wrong and must be addressed. You can have different types of incidents in FireHydrant, for example, security incidents, technical incidents, and legal incidents.


Once an incident is resolved, FireHydrant helps teams run better retrospectives. Retrospectives help incident response teams learn from their incidents, and improve their incident response process (and their product) in the future.

Service Catalog

FireHydrant lets you catalog your infrastructure (functionalities, services, and environments) so that you know which properties are impacted by an incident, their dependencies, and who to involve in those incidents.


FireHydrant supports a growing list of integrations, including Slack, PagerDuty, Zoom, Google Docs, Jira, Zendesk, Kubernetes, Okta, and more.


Other features


FireHydrant teams allow you to quickly assign a group of people to an incident from Slack or the UI. They're also a great way to see which groups own the services in your application stack.

Incident Roles

FireHydrant incident roles help your incident responders know exactly what their responsibilities are as soon as an incident starts. We include out-of-the-box roles like Commander, Ops Lead, and Communication... but you can create any role you need for your team.


FireHydrant reduces the stress of figuring out how severe an incident is by enabling you to configure a severity matrix. Now, your incident response team can create incidents and be confident that the correct severity is applied.

Change events ingestion

Many incidents are caused by deploys or configuration changes. With FireHydrant, you can easily view your deploy events associated with different pieces of infrastructure so you can more quickly track the cause of your incidents.  FireHydrant supports change event ingestion via the API as well as through our Kubernetes and AWS Cloudtrail integrations.

Status pages

FireHydrant offers two out-of-the-box status page functionalities: incident-specific status pages, and a global status page. Incident-specific status pages are status pages for a specific incident. These are private temporary status pages that expire after 48 hours of your incident being resolved. Global status pages can be public or private, and they are meant to show the status of your platform or application at any given time.  FireHydrant also offers an integration with Atlassian Statuspage.


FireHydrant gives you a quick view of your historical incidents and infrastructure health so you know where to focus your efforts and how you can improve your incident response process moving forward. Analytics include how healthy your infrastructure has been, incident response metrics including remediation time, and much more.

Last updated on 3/28/2023