ESPHome
ESPHome opens the 2026.11 beta days after its second October patch.
A side-by-side editorial comparison of Apideck and GoCD — release velocity, themes, recent moves, and the top alternatives to consider.
Apideck rebuilds its SD Worx connector after the old login method is switched off.
Apideck added an SD Worx web service connector on November 3 that uses certificate-based OIDC credentials, because SD Worx no longer activates the username and password access the SOAP connector relied on. Existing connections keep working, and the old connector now points to the new one as its migration target. It covers employees and daily time-off records, within SD Worx's limit of 1,000 employee-months per day.
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.
Apideck added an SD Worx web service connector on November 3 that uses certificate-based OIDC credentials, because SD Worx no longer activates the username and password access the SOAP connector relied on. Existing connections keep working, and the old connector now points to the new one as its migration target. It covers employees and daily time-off records, within SD Worx's limit of 1,000 employee-months per day.
After a summer of new European accounting and HRIS connectors, the newest entry is maintenance driven by a vendor's auth change. Apideck now handles migrations inside the catalog by marking legacy connectors with a target.
The entries show a six-week gap before this one, so the cadence of new connectors is unclear; expect more migrations as vendors retire password-based access.
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 Apideck or GoCD.
ESPHome opens the 2026.11 beta days after its second October patch.
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.
Dragonfly opens a 2.1 line with metrics that explain why replicas drop.
See all Apideck 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. GoCD is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 editorial sparks in the last 30 days against 0. 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. GoCD is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top Apideck alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Apideck alternatives" section above for the current picks, or visit /alternatives/apideck 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.