ESPHome
ESPHome opens the 2026.11 beta days after its second October patch.
A side-by-side editorial comparison of Dragonfly and GoCD — release velocity, themes, recent moves, and the top alternatives to consider.
Dragonfly opens a 2.1 line with metrics that explain why replicas drop.
Dragonfly tagged v2.1.0 on November 4, exporting snapshot counters, a save-in-progress gauge and replica disconnects labeled closed, error or timeout. Before, a replica dropped for stalling was indistinguishable from one whose connection simply closed. The 1.40 and 2.0 lines keep getting small cluster-mode fixes, including faster GetSlotInfo and slot migration that no longer drops writes.
GoCD's changelog is one maintainer keeping a 2010s CI server running on current runtimes.
The visible work is almost entirely platform upkeep, and nearly all of it is authored by a single contributor. The baseline has been walked forward repeatedly — Java 17 minimum, then building and packaging on Java 21, then Java 21 as the hard minimum with macOS x64 support dropped — while container images moved from Alpine and CentOS Stream to Wolfi and Chainguard, Rails went from 6.1 through 7.1, and Hamcrest was replaced by AssertJ across the test suite. 26.1.0 is the exception in substance: it carries security fixes described as affecting all prior GoCD versions, with an explicit recommendation to upgrade as soon as possible.
Dragonfly tagged v2.1.0 on November 4, exporting snapshot counters, a save-in-progress gauge and replica disconnects labeled closed, error or timeout. Before, a replica dropped for stalling was indistinguishable from one whose connection simply closed. The 1.40 and 2.0 lines keep getting small cluster-mode fixes, including faster GetSlotInfo and slot migration that no longer drops writes.
Dragonfly is maturing for production operations: the 2.0 line fixed cluster correctness, and 2.1 starts by making replication and persistence observable from Prometheus. The project says it prefers small incremental features, so 2.1 will likely grow the same way.
More metrics and cluster-mode fixes on 2.1, with 1.40 and 2.0 still getting backports for a while.
The visible work is almost entirely platform upkeep, and nearly all of it is authored by a single contributor. The baseline has been walked forward repeatedly — Java 17 minimum, then building and packaging on Java 21, then Java 21 as the hard minimum with macOS x64 support dropped — while container images moved from Alpine and CentOS Stream to Wolfi and Chainguard, Rails went from 6.1 through 7.1, and Hamcrest was replaced by AssertJ across the test suite. 26.1.0 is the exception in substance: it carries security fixes described as affecting all prior GoCD versions, with an explicit recommendation to upgrade as soon as possible.
This is a mature product in custodial maintenance rather than development. The pattern across releases is dependency deduplication, dead code removal, deprecation cleanup and base image swaps — the work that keeps a large Rails and Java codebase installable and patchable on current operating systems. Feature entries are rare enough that their absence, rather than any particular change, is the signal.
Given the security advisory in 26.1.0 covers all earlier versions and the release notes point offsite for detail, the practical next step for operators is that upgrade. The entries show no queued feature work to project from.
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 Dragonfly or GoCD.
ESPHome opens the 2026.11 beta days after its second October patch.
Apideck rebuilds its SD Worx connector after the old login method is switched off.
Currents lists itself in the Claude and ChatGPT/Codex plugin directories.
Jackett ships a daily build to keep hundreds of torrent indexers working as sites move and close.
Hatchet adds magic-link login and publishes its CLI on npm.
Redocly forks Markdoc and points Open in Claude at the desktop app.
See all Dragonfly alternatives → · See all GoCD alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Dragonfly and GoCD are shipping at a similar cadence (velocity 5.0 vs 5.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. Dragonfly and GoCD are shipping at a similar cadence (velocity 5.0 vs 5.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 Dragonfly alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Dragonfly alternatives" section above for the current picks, or visit /alternatives/dragonfly for the full list with editorial commentary on each.
Top GoCD alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "GoCD alternatives" section above for the current picks, or visit /alternatives/gocd for the full list with editorial commentary on each.