GravityKit
GravityKit folds every GravityView extension into one Pro plugin.
A side-by-side editorial comparison of Hatchet and Pacemaker — release velocity, themes, recent moves, and the top alternatives to consider.
Hatchet chases DAG crash loops through three engine patches in a day.
Hatchet added sandboxes, Labs switches and cloud MFA in early November. The week since has been engine reliability: v0.120.3 batches DAG step triggers, v0.120.4 fixes stranded match rows and prunes database partitions before locking, and v0.120.5 removes another cause of DAG crash loops. Python SDK 1.46.0 makes it easier to unit-test tasks and passes failures to cleanup dependencies.
Pacemaker is putting TLS and X509 auth between its cluster nodes, then hardening the wire code.
Two branches ship in parallel: the 3.0.x line carrying new work and 2.1.x taking backported fixes. The 3.0 series added TLS for Pacemaker Remote nodes, X509 authentication, TLS certificates for remote CIB operations, and then PSK authentication for those same operations, alongside large-IPC and multipart message support. The most recent releases on both branches are the same security train, fixing CVE-2026-10649 and a set of integer overflows and size checks in the remote message code.
Hatchet added sandboxes, Labs switches and cloud MFA in early November. The week since has been engine reliability: v0.120.3 batches DAG step triggers, v0.120.4 fixes stranded match rows and prunes database partitions before locking, and v0.120.5 removes another cause of DAG crash loops. Python SDK 1.46.0 makes it easier to unit-test tasks and passes failures to cleanup dependencies.
After a burst of features, Hatchet is tuning the engine under load: fewer locks, batched triggers and crash-loop fixes. The SDKs are getting testing and correctness work to match.
Expect more v0.120.x patches on DAG handling, then a sandbox package out of release candidate.
Two branches ship in parallel: the 3.0.x line carrying new work and 2.1.x taking backported fixes. The 3.0 series added TLS for Pacemaker Remote nodes, X509 authentication, TLS certificates for remote CIB operations, and then PSK authentication for those same operations, alongside large-IPC and multipart message support. The most recent releases on both branches are the same security train, fixing CVE-2026-10649 and a set of integer overflows and size checks in the remote message code.
The cluster's internal transport is being rebuilt on the assumption that the network between nodes is not trusted. Authentication and encryption arrived first, and the fixes that followed, overflow guards and a maximum remote message size, are the hardening pass on the same code paths. Release discipline is heavy and visible: each version ships a release candidate with an identical commit set days earlier, and every 3.0 release documents the regressions it introduced and where they were fixed.
Remote CIB operations now support both X509 certificates and PSK, and the recent fixes all sit in message framing and size limits; further work is most likely to continue in that message-handling code rather than adding another authentication mechanism.
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 Hatchet or Pacemaker.
GravityKit folds every GravityView extension into one Pro plugin.
Payload's v4 beta.9 keeps every past image crop and raises the Node floor again.
Nautobot 3.3 alpha 2 adds test helpers and a cable location filter after 3.2.9's token-leak fix.
Clair 4.10 RC can read SBOMs to match Java vulnerabilities.
Shuffle tags builds almost daily, but the notes are empty.
KrakenD's community edition is shipping only dependency bumps.
See all Hatchet alternatives → · See all Pacemaker alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Hatchet and Pacemaker are shipping at a similar cadence (velocity 6.3 vs 6.3, 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. Hatchet and Pacemaker are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top Hatchet alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Hatchet alternatives" section above for the current picks, or visit /alternatives/hatchet for the full list with editorial commentary on each.
Top Pacemaker alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Pacemaker alternatives" section above for the current picks, or visit /alternatives/pacemaker for the full list with editorial commentary on each.