← Back to home
Comparison · Infra & APIs

Hatchet vs Pacemaker

A side-by-side editorial comparison of Hatchet and Pacemaker — release velocity, themes, recent moves, and the top alternatives to consider.

Hatchet vs Pacemaker: at a glance

FeatureHatchetPacemaker
SectorInfra & APIsInfra & APIs
Velocity score6.36.3
Sparks · 30d00
Top themesdurable execution, serverless, task queues, rate limitinghigh availability, cluster security, tls authentication, dual branch releases
Last editorial update18h ago2mo ago
WebsiteVisit →Visit →

What is Hatchet?

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.

Read the full Hatchet trajectory →

What is Pacemaker?

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.

Read the full Pacemaker trajectory →

Hatchet vs Pacemaker: editorial side-by-side

H
Hatchet
INFRA · APIS
6.3

Hatchet takes durable tasks serverless, with handlers for Cloudflare Workers, Vercel and Node.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

P
Pacemaker
INFRA · APIS
6.3

Pacemaker is putting TLS and X509 auth between its cluster nodes, then hardening the wire code.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

Alternatives to Hatchet and Pacemaker

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.

See all Hatchet alternatives → · See all Pacemaker alternatives →

Recent activity from Hatchet and Pacemaker

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1d agoHatchetHatchet v0.115.0: contributor list update, no product notes
  2. 1d agoHatchetHatchet v0.114.15 fixes migration deadlocks
  3. 1d agoHatchetHatchet v0.114.14 builds its own continuous aggregates
  4. 1d agoHatchetHatchet v0.114.13 quiets noisy DAG operator errors
  5. 1d agoHatchetPython SDK 1.43.2 parses 429 rate-limit errors
  6. 1d agoHatchetHatchet v0.114.12 adds a Concurrency dashboard page
  7. 3mo agoPacemaker3.0.3: CVE-2026-10649 and remote message overflow fixes
  8. 3mo agoPacemaker3.0.2: PSK auth for remote CIB operations
  9. 3mo agoPacemaker3.0.1: TLS and X509 authentication for Pacemaker Remote ⚡
  10. 3mo agoPacemaker3.0.3-rc1: release candidate for the CVE fix set
  11. 4mo agoPacemaker2.1.11: CVE-2026-10649 backported to the maintenance branch
  12. 4mo agoPacemaker2.1.11-rc1: release candidate for the 2.1 CVE backport

Frequently asked questions

What is the difference between Hatchet and Pacemaker?

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.

Is Hatchet better than Pacemaker?

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.

What are the best alternatives to Hatchet?

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.

What are the best alternatives to Pacemaker?

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.