NetBox
NetBox 4.7's patch run fixes a token leak and a broken restore path.
A side-by-side editorial comparison of Cobbler and FireHydrant — release velocity, themes, recent moves, and the top alternatives to consider.
Cobbler's 3.3 branch adds Kerberos single sign-on to the web UI.
Cobbler's public releases are all 3.3-branch backports. 3.3.10 adds Kerberos/GSSAPI single sign-on for the web UI through an Apache-terminated bridge and hardens the passthru authentication module against timing attacks. It follows the 3.3.8/3.3.9 pair, which brought openSUSE Leap 16 and Agama installer support, XCP-ng network installs and Python 3.13 support, and had to be re-cut after a CI publishing failure.
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.
Cobbler's public releases are all 3.3-branch backports. 3.3.10 adds Kerberos/GSSAPI single sign-on for the web UI through an Apache-terminated bridge and hardens the passthru authentication module against timing attacks. It follows the 3.3.8/3.3.9 pair, which brought openSUSE Leap 16 and Agama installer support, XCP-ng network installs and Python 3.13 support, and had to be re-cut after a CI publishing failure.
The branch is still gaining features aimed at enterprise data centres rather than winding down: new installer ecosystems in August, directory-backed single sign-on now. Authentication has been a recurring concern since the CVE-2024-47533 admin-API bypass. Releases continue to arrive as rollups from main.
Expect further 3.3.x rollups; whether the main line cuts a 3.4 is not visible from these entries.
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 Cobbler or FireHydrant.
NetBox 4.7's patch run fixes a token leak and a broken restore path.
Apptainer's CDI support needed a privilege-escalation fix four months after it shipped.
Coder now patches three release lines at once, and the fixes keep landing on agent access.
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.
See all Cobbler 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. Cobbler 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. Cobbler 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 Cobbler alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Cobbler alternatives" section above for the current picks, or visit /alternatives/cobbler 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.