Before FireHydrant was built, incident response teams were stuck doing a lot of manual work and jumping around between various tools. They often didn't have a clear process for responding to, resolving, and learning from incidents.
FireHydrant integrates with your existing tools to automate manual tasks throughout the lifecycle of an incident and helps bring your entire team together to put out fires faster.
Why use FireHydrant?
- Automate manual tasks such as creating a Slack channel, Jira ticket, Zoom bridge or Google Meet
- Respond to and resolve incidents faster
- Orchestrate your entire team around a standard incident management process
- Learn valuable lessons from your incidents, and use that knowledge to improve your product
The star components
Runbooks are what make FireHydrant unique and powerful. Say goodbye to wikis and endless static docs. FireHydrant enables you to automate your Runbooks and quickly trigger them through a simple Slack command. With FireHydrant Runbooks, your team can stay focused on fighting fires instead of reading documentation.
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.
Other key 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.
FireHydrant 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.
FireHydrant lets you catalog your digital properties (functionalities, services, and environments) so that you know which properties are impacted by an incident, and who to involve in those incidents.
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 offers two 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 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.
The FireHydrant platform: Demo