At FireHydrant, we know that alert management is about more than just getting notifications to the right people — it’s about reducing stress and fatigue, balancing workloads, and empowering your team to respond with confidence. That’s why we’re excited to unveil Round Robin for Signals Escalation Policies, a feature designed to make alert escalations smarter, fairer, and more team-friendly by allowing you to automate the sequential assignment of new alerts.

When we launched our fully-featured Microsoft Teams integration in May, our goal was clear: to provide enterprise teams with the robust and comprehensive toolset they need to manage incidents faster and more effectively – right where they work. It’s all part of our commitment to building the leading enterprise incident management solution. Today, we’ve enhanced our Teams integration by adding the ability to automatically create Microsoft Teams group chats directly from your Runbooks.

Today, we’re excited to announce the release of our new ServiceNow integration in beta — designed to give engineers even more control to manage and automate incidents in FireHydrant while seamlessly keeping the rest of the organization aligned in ServiceNow.

At FireHydrant, we believe that what happens after incidents is just as important as what happens during – and that’s why Retrospectives have always been a cornerstone of our product. Today, we’re proud to introduce the most powerful, customizable, and collaborative retrospective experience you’ll find anywhere.

Milestones have been central to our platform since day one, helping users track incident progress and drive automation. We're excited to introduce our enhanced Milestone feature, offering unparalleled customization. Now, you can fine-tune your incident management process to perfectly align with your organization's specific policies and workflows.

Automated event payloads come in many shapes and sizes. These infinitely different event structures pose a problem for users who want to send them all to the same place to page on-call staff. Unless that on-call solution supports the schema directly, you’re out of luck. While we’re proud of the number of integrations we support today for event sources into on-call, we also think the best number that we should support is infinity.

Today, the entire world is feeling the pain of a major software outage. While we know a lot about these occurrences—our entire business is built on helping companies manage incidents and outages effectively—we’re not here to share our opinion on it. Instead, we’d like to help those unfamiliar with the incident lifecycle understand what happens when an outage like this occurs, who is responsible for what, and what companies ultimately do to get things working again.

We’ve gotten clear feedback from our customers that we’ve needed a strong Microsoft Teams integration. Responders want a full suite of incident management functionality, no matter what chat application their organization uses. We heard you. That’s why we’re proud to announce a brand new MS Teams integration with fully robust incident management lifecycle capabilities.

When we launched Signals to the world, we were excited to hear how our product resonated with many teams. But with that excitement came an understandable concern: how much time and effort will I have to put in to move from my existing provider to Signals? We hear you — that’s why we built the Signals Migrator tool. And we’re open sourcing it.