Oh Dear
Oh Dear's weekly changelogs have carried a security section five weeks running.
A side-by-side editorial comparison of BorgBackup and FireHydrant — release velocity, themes, recent moves, and the top alternatives to consider.
Borg 2.0 beta 25 breaks repositories to swap its hash and repository format.
BorgBackup's 2.0 beta line is still making breaking format changes. Beta 25 requires new repositories: it moves store object names to blake3, replaces several repository objects with an ini-style config, removes the none-sha256 and none-blake3 modes in favor of authenticated ones, and protects lock, index and cache objects with the repository key. The stable 1.4 line remains the production track.
FireHydrant stops paging people at night for alerts that can wait until morning.
Support hours now do something during off-hours. Alerts arriving outside a team's window and at or below a new Off-hours Priority Threshold are snoozed, then re-enter the escalation policy from the top when the next window opens. Higher-priority alerts still notify immediately, and a Slack, Teams or webhook destination can report what is queued. The change is opt-in per team until January 2027, when remaining teams are moved over.
BorgBackup's 2.0 beta line is still making breaking format changes. Beta 25 requires new repositories: it moves store object names to blake3, replaces several repository objects with an ini-style config, removes the none-sha256 and none-blake3 modes in favor of authenticated ones, and protects lock, index and cache objects with the repository key. The stable 1.4 line remains the production track.
Twenty-five betas in, the format is not settled, but this beta is decisive: it removes old modes and object types, which narrows what 2.0 has to support. Treating lock and cache objects as keyed data also extends the security model beyond archive contents.
Further betas are likely to keep requiring new repositories until the format freezes, so a release candidate should not be assumed soon. The 1.4 line stays the safe choice until then.
Support hours now do something during off-hours. Alerts arriving outside a team's window and at or below a new Off-hours Priority Threshold are snoozed, then re-enter the escalation policy from the top when the next window opens. Higher-priority alerts still notify immediately, and a Slack, Teams or webhook destination can report what is queued. The change is opt-in per team until January 2027, when remaining teams are moved over.
The year's table-stakes work for switchers is giving way to on-call quality of life. Schedule overrides made changes safe, and snoozing now reduces unnecessary pages, with visibility built in through a Snoozed filter and alert timelines. The January date makes this the default for everyone, and FireHydrant says it waited until after the holidays so the change does not land in customers' busiest weeks.
Expect guidance and prompts pushing teams to set thresholds before the January 2027 switch. API and Terraform coverage for these settings is plausible, but the entry does not mention it.
Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either BorgBackup or FireHydrant.
Oh Dear's weekly changelogs have carried a security section five weeks running.
ShenYu's AI gateway plugins are back in motion, with 2.7.2 candidate tags in October.
TestingBot's autumn work is plumbing: a rebuilt tunnel and another bug-tracker link.
KubeArmor ships fixes as release-candidate tags, and its feed misses the finals.
All Quiet moves from enterprise integrations to the on-call engineer's own day.
Robusta's recent releases patch its runner image rather than add features.
See all BorgBackup alternatives → · See all FireHydrant alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. BorgBackup and FireHydrant are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. BorgBackup and FireHydrant are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top BorgBackup alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "BorgBackup alternatives" section above for the current picks, or visit /alternatives/borgbackup for the full list with editorial commentary on each.
Top FireHydrant alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "FireHydrant alternatives" section above for the current picks, or visit /alternatives/firehydrant for the full list with editorial commentary on each.