← Back to home
Comparison · Infra & APIs

Hatchet vs Transmission

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

Hatchet vs Transmission: at a glance

FeatureHatchetTransmission
SectorInfra & APIsInfra & APIs
Velocity score6.30.0
Sparks · 30d00
Top themesdurable execution, serverless, task queues, rate limitingbittorrent, json-rpc, api-migration, beta-freeze
Last editorial update17h 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 Transmission?

Transmission rewrote its RPC API to JSON-RPC 2.0 — then the 4.1 beta train stalled.

The whole visible history is the 4.1.0 beta series, running from December 2024 to January 2026 and developed in parallel with the 4.0.x bug-fix line since 2023. Across those betas the client picked up sequential downloading, a selectable µTP-versus-TCP preferred transport, proxy support for web connections, IPv6 and dual-stack UDP trackers, native platform icons, and a JSON-RPC 2.0-compliant RPC API with snake_case unified across RPC and settings.json. Feature freeze was declared at beta.5 in January 2026, and nothing has shipped since.

Read the full Transmission trajectory →

Hatchet vs Transmission: 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.

T
Transmission
INFRA · APIS
0.0

Transmission rewrote its RPC API to JSON-RPC 2.0 — then the 4.1 beta train stalled.

◆ Current state

The whole visible history is the 4.1.0 beta series, running from December 2024 to January 2026 and developed in parallel with the 4.0.x bug-fix line since 2023. Across those betas the client picked up sequential downloading, a selectable µTP-versus-TCP preferred transport, proxy support for web connections, IPv6 and dual-stack UDP trackers, native platform icons, and a JSON-RPC 2.0-compliant RPC API with snake_case unified across RPC and settings.json. Feature freeze was declared at beta.5 in January 2026, and nothing has shipped since.

◆ Where it's heading

The interesting work is at the integration boundary, not in the download engine: the RPC surface has been standardised and renamed, and beta.5 was largely spent repairing what those changes broke, including backwards-incompatible keys accidentally written into settings files. That is the cost profile of an API migration in a project with a large ecosystem of third-party remotes. With feature freeze held for seven months and no 4.1.0 final, the release is late relative to its own stated plan.

◆ Prediction

The next release should be 4.1.0 final or a further beta rather than new features, since the branch is frozen — but the entries give no signal on what is holding it.

Alternatives to Hatchet and Transmission

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 Transmission.

See all Hatchet alternatives → · See all Transmission alternatives →

Recent activity from Hatchet and Transmission

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

  1. 23h 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. 9mo agoTransmission4.1.0-beta.5 enters feature freeze and repairs settings-file damage
  8. 10mo agoTransmission4.1.0-beta.4 replaces the RPC API with a JSON-RPC 2.0 one ⚡
  9. 11mo agoTransmission4.1.0-beta.3 adds proxy support and streaming-friendly sequential writes
  10. 1y agoTransmission4.1.0-beta.2 adds sequential downloading and BEP-7 tracker fallback
  11. 1y agoTransmission4.1.0-beta.1 opens a branch two years in development

Frequently asked questions

What is the difference between Hatchet and Transmission?

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.

Is Hatchet better than Transmission?

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.

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 Transmission?

Top Transmission alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Transmission alternatives" section above for the current picks, or visit /alternatives/transmission for the full list with editorial commentary on each.