NetBird
NetBird's second v0.82 candidate keeps the MySQL removal and deprecates Rosenpass.
A side-by-side editorial comparison of Hatchet and Terragrunt — release velocity, themes, recent moves, and the top alternatives to consider.
Hatchet takes durable tasks serverless, with handlers for Cloudflare Workers, Vercel and Node.
Hatchet's new @hatchet-dev/serverless 0.1.0 runs tasks on Cloudflare Workers, Vercel and Node. An in-engine operator delivers them by signed POST or by an invocation websocket that also carries durable sleeps, waits and child runs. Around it, the engine shipped three patches in a day: DAG replays no longer take an advisory lock, worker shutdown now waits for durable tasks, and status queries use partition pruning. The API now declares 429 with Retry-After on every authenticated call.
Terragrunt graduated six experiments at once and has spent three candidates stabilising them
Terragrunt is running the v1.1.0 release-candidate cycle, now at rc3. The first candidate completed six experiments simultaneously — stack-dependencies, a content-addressable store, a catalog redesign, mark-many-as-read, opt-out-auth and DAG queue display. The two candidates since have added only bug fixes for those features plus improvements to how releases are published and verified.
Hatchet's new @hatchet-dev/serverless 0.1.0 runs tasks on Cloudflare Workers, Vercel and Node. An in-engine operator delivers them by signed POST or by an invocation websocket that also carries durable sleeps, waits and child runs. Around it, the engine shipped three patches in a day: DAG replays no longer take an advisory lock, worker shutdown now waits for durable tasks, and status queries use partition pruning. The API now declares 429 with Retry-After on every authenticated call.
Until now, running Hatchet meant running long-lived workers. The serverless package removes that requirement, so durable execution can run where JavaScript teams already deploy. The engine work points the same way: rate limits declared in the spec, safer worker acks, cheaper status queries. Patch cadence is still very high, often several engine tags a day, and much of it fixes durable-task edge cases.
Expect quick 0.1.x serverless releases as early users hit edge cases on each platform, and possibly matching Python handlers. More engine patches on durable-task shutdown and replay are likely.
Terragrunt is running the v1.1.0 release-candidate cycle, now at rc3. The first candidate completed six experiments simultaneously — stack-dependencies, a content-addressable store, a catalog redesign, mark-many-as-read, opt-out-auth and DAG queue display. The two candidates since have added only bug fixes for those features plus improvements to how releases are published and verified.
The experiment-graduation model is doing what it is supposed to: features developed behind flags land together in one minor, and the candidate cycle is purely stabilisation. The release-publishing and verification work appearing in rc2 suggests supply-chain provenance is being treated as release-blocking rather than as a follow-up.
With three candidates carrying identical feature lists, v1.1.0 final is the likely next release, followed by a fresh batch of experiments opening for v1.2.
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 Terragrunt.
NetBird's second v0.82 candidate keeps the MySQL removal and deprecates Rosenpass.
At Universe, GitHub folds Copilot into Enterprise seats and lets Copilot Fusion pick the model.
incident.io's agent now runs your team's own tools, with a human approval before any change.
Airflow 3.4 reaches its first release candidate, a week after the 10-20 provider wave.
Redocly's reunite.agent gets per-duty cron schedules, rules and source repos.
Jackett ships a daily build to keep hundreds of torrent indexers working as sites move and close.
See all Hatchet alternatives → · See all Terragrunt alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Hatchet is currently shipping more aggressively (velocity 6.3 vs 0.0), 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. Hatchet is currently shipping more aggressively (velocity 6.3 vs 0.0), 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 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 Terragrunt alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Terragrunt alternatives" section above for the current picks, or visit /alternatives/terragrunt for the full list with editorial commentary on each.