Operations | Monitoring | ITSM | DevOps | Cloud

When you’re up and running with FireHydrant, there’s no better incident management experience out there. We built it that way — fast, intuitive, reliable when it matters most. Now, the first five minutes are just as streamlined and enjoyable as the rest. We rebuilt our onboarding flow from the ground up and cut setup time by over 90% in the process. With the new onboarding experience, you get a guided experience to connect your tools and get the most out of FireHydrant.

Signals is FireHydrant’s modern on-call product that is a replacement for legacy tools such as PagerDuty or Opsgenie. When we began planning Signals, we not only wanted to build a kickass on-call alternative, but also to reset the standard on how much on-call should cost.

Atlassian is retiring Opsgenie, and if you're one of the teams relying on it to manage on-call and incidents, you're facing a tough question: Do you make the forced migration to Jira Service Management or Compass, scramble for a lookalike tool — or use this moment to upgrade your entire approach to incident response? If you’re facing that decision, we get it. Changing tools midstream isn’t ideal (to say the least). But it’s also a rare opportunity to take a meaningful step forward.

Let's face it – not all notifications are created equal. That paper cut of a CSS bug probably doesn't need the same response as your production database doing its best impression of a black hole. Today, we're thrilled to announce Priority-Based Escalation Policies, a powerful new way to ensure your team's response matches the notification severity.

Getting started with any new platform can feel like a lot. We get it. That’s why we built The Fire Academy — our new Customer Learning Platform that makes getting started on FireHydrant as seamless as possible. Our goal is simple: we want you to feel confident customizing and configuring FireHydrant to fit your needs without having to dig for answers or wait for support. Everything you need is at your fingertips, so you can work at your own pace and get the most out of the platform.

When incidents strike, clear communication is crucial — but one size doesn't fit all. Customer support needs to know what users are experiencing and possible workarounds, execs need business impact updates and timelines, and engineers need deep technical details. Manually juggling these different communication needs is time-consuming, error-prone, and frustrating when every minute counts.

When something goes wrong, the first question is always: what changed? Whether it’s an unexpected change to your on-call schedule, a broken automation, or a modified Runbook that just seems off, understanding the issue starts with knowing who made what change, when it happened, and what exactly changed. But in an organization with many users, keeping track of every action can feel impossible.

A year ago, we launched Signals with a simple but powerful idea: on-call shouldn’t be a painful juggling act. Too often, teams had to bounce between separate alerting and incident response tools, slowing everything down when speed mattered most. And traditional on-call tools? They were built around services, not the people responding to them.

A great retrospective isn’t just about documenting what happened — it’s about bringing your team together to uncover the insights that lead to real improvements in your process, roles, and technology. But to make that happen, retrospectives need to be structured enough to be effective, flexible enough to fit your team, and easy to collaborate on. That’s exactly what we set out to build.

We built FireHydrant to be the kind of platform we’d want to use as developers, giving you the same tools and flexibility we rely on every day. With over 350 publicly accessible API endpoints, we’ve always believed in giving developers the power to customize and extend our platform to meet their exact needs.