LoginSign Up
← Back to all sparks
F

FireHydrant

INFRA · APIS
Velocity2.5

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

firehydrant.com ↗

On-call overrides now survive a schedule edit — and are the only way to change a shift.

on-call-schedulingincident-responseopsgenie-migrationreversibilityschedule-overrides
◆Current state
FireHydrant shipped a real override layer for on-call schedules. Overrides now survive schedule edits made from either the web UI or the API, always win against an overlapping generated shift, can be stacked, and can be cancelled to restore the original system-generated shift. Reassignment, coverage requests, and shift deletion no longer mutate the generated schedule at all — each creates an override instead, which is what makes every change cleanly undoable. The constraint is historical: restoring a shift requires knowing what it originally looked like, and that data has only been tracked since 24 July 2026, so older rotations need a one-time regeneration first.
◆Where it's heading
The last year reads as one project — making an incumbent-grade on-call product safe enough to switch to. Customizable retrospective exports, authenticated status pages, consolidated analytics, an EU instance, MS Teams support, then the Signals Migrator that automates the move off PagerDuty and Opsgenie. Overrides fit the same pattern: a feature teams assume already exists, previously broken badly enough that admins learned not to touch a schedule once coverage was arranged. The work is closing table-stakes gaps ahead of a migration window, not opening new surfaces.
◆Prediction
Expect the override model to be pushed out to the API and Terraform surfaces next, along with prompts to regenerate stale rotations before Opsgenie's April 2027 deletion date drives migration volume.

◆Recent moves

  1. 15d ago

    Introducing: Preserved OnCall Schedule Overrides

    Overrides now survive schedule edits and take precedence over generated shifts, with stacking, an explicit Gap type, and cancellation that restores the original shift. Because reassignment and coverage requests now route through overrides too, schedule changes became reversible rather than destructive. Rotations not regenerated since 24 July 2026 need a one-time regeneration before any of it applies, and pre-existing overrides do not carry over.

    View source ↗
  2. 2mo ago

    ICYMI: The New In-App Signals Migrator

    ⚡ SPARK

    The Signals Migrator is the sharpest statement of FireHydrant's current strategy: import teams, schedules, escalation policies, and support hours out of PagerDuty or Opsgenie into a staged state you review before activation, while the existing setup keeps running. The scheduling work since then, overrides included, is about making the product teams land in trustworthy.

    View source ↗
  3. 3mo ago

    A Better View of Your Team, Right From the Start

    A clearer team on-call view from the first screen, part of the same effort to make the product legible to teams arriving from an incumbent tool.

    View source ↗
  4. 3mo ago

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

    The monthly recap format: deeper analytics and smarter on-call filters, incremental work spread across several surfaces rather than one headline change.

    View source ↗
  5. 4mo ago

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

    An EU instance and an MS Teams Scribe, removing two of the most common blockers — data residency and chat platform — for prospective switchers.

    View source ↗
  6. 6mo ago

    Consolidated Analytics Pages and Copy Retrospective to Markdown

    Consolidated analytics pages and Markdown export for retrospectives — small workflow wins in the post-incident surface.

    View source ↗