LoginSign Up
← Back to all sparks
F

FireHydrant

INFRA · APIS
Velocity6.3

Incident response and reliability platform with on-call and status pages

firehydrant.com ↗

FireHydrant turns Opsgenie's shutdown into a no-code land grab

incident-managementon-callopsgenie-migrationsignalsai-summaries
◆Current state
FireHydrant is executing on incident management end-to-end while aggressively courting migrations. The June headline is an in-app, no-code Signals Migrator that pulls teams, schedules, and escalation policies out of PagerDuty or Opsgenie and stages them for review before go-live. Around it the platform is maturing on all fronts — a redesigned Teams experience, deeper incident analytics, an EU instance, MS Teams transcription (Scribe), and a long tail of AI-summary and Terraform refinements.
◆Where it's heading
The strategy is clear: reduce switching cost to near zero and capture responders displaced by Atlassian's Opsgenie wind-down (data deletion set for April 2027). Everything else — EU data residency, MS Teams Scribe, configurable AI conference-bridge summaries — broadens the surface so a migrated team lands on a complete platform, not a thinner alternative. AI runs through the product as summaries and related-incident detection rather than as a standalone feature.
◆Prediction
With Opsgenie's clock ticking toward 2027, expect FireHydrant to keep hardening the migration path and marketing it hard, while closing feature gaps (Teams parity, EU coverage) a switching customer would notice.

◆Recent moves

  1. 1mo ago

    ICYMI: The New In-App Signals Migrator

    ⚡ SPARK

    A no-code, in-app migrator imports on-call setups from PagerDuty or Opsgenie into a staged review state before going live. It's the centerpiece of FireHydrant's push to absorb teams displaced by Opsgenie's shutdown, lowering switching cost to near zero.

    View source ↗
  2. 1mo ago

    A Better View of Your Team, Right From the Start

    A rebuilt Teams directory and detail page surface on-call, coverage, ownership, and readiness at a glance with a quickview drawer and fewer clicks. Purely additive polish that makes a migrated org's teams easier to operate — consistent with lowering the cost of landing on FireHydrant.

    View source ↗
  3. 2mo ago

    May Recap: Deeper Analytics, Smarter On-Call Filters & More

    Session-based incident-involvement analytics, smarter on-call schedule filtering, and AI notification controls (cooldowns, unlicensed-user summaries). Incremental depth across analytics and AI-summary governance — the kind of gap-closing a switching customer evaluates.

    View source ↗
  4. 3mo ago

    April Recap: EU Instance, MS Teams Scribe, and more!

    An EU instance (full lifecycle with data residency), MS Teams Incident Scribe transcription, CSV transcript export, and severity role restrictions. Regional and integration coverage that broadens the platform for enterprise and EU buyers.

    View source ↗
  5. 4mo ago

    Consolidated Analytics Pages and Copy Retrospective to Markdown

    Legacy analytics pages fold into a single MTTX dashboard, and retrospectives can be copied to markdown without a Docs or Confluence integration. Consolidation and export convenience over new capability.

    View source ↗
  6. 5mo ago

    Customize Retrospective Exports

    Per-type retrospective export templates, a redesigned incident header, and flexible incident-field configuration. Workflow-fit refinements across retros and the incident surface.

    View source ↗