← Back to home
Comparison · Infra & APIs

Fission vs Hatchet

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

Shared themes:serverless

Fission vs Hatchet: at a glance

FeatureFissionHatchet
SectorInfra & APIsInfra & APIs
Velocity score0.06.3
Sparks · 30d00
Top themesserverless, kubernetes, faas, release-candidatesdurable execution, serverless, task queues, rate limiting
Last editorial update2mo ago15h ago
WebsiteVisit →Visit →

What is Fission?

Fission's release feed carries only RC tags, and none of them say what shipped

Every entry here is a release candidate — v1.22.0-rc1 and rc2, v1.23.0-rc1, v1.25.0-rc1 — with no final release appearing between them, and the version sequence skips 1.24 entirely. The bodies are whatever the tagging commit said, so what reaches this feed is a dependabot bump, a CLI tool-version refresh, a codegen sync explicitly labelled as having no functional change, and one entry that is nothing but links to an external release-highlights page. The actual release notes live on the project's documentation site, not here.

Read the full Fission trajectory →

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 →

Fission vs Hatchet: editorial side-by-side

F
Fission
INFRA · APIS
0.0

Fission's release feed carries only RC tags, and none of them say what shipped

◆ Current state

Every entry here is a release candidate — v1.22.0-rc1 and rc2, v1.23.0-rc1, v1.25.0-rc1 — with no final release appearing between them, and the version sequence skips 1.24 entirely. The bodies are whatever the tagging commit said, so what reaches this feed is a dependabot bump, a CLI tool-version refresh, a codegen sync explicitly labelled as having no functional change, and one entry that is nothing but links to an external release-highlights page. The actual release notes live on the project's documentation site, not here.

◆ Where it's heading

What can be read from these tags is infrastructure maintenance rather than product direction: Go dependency updates, helm and kind and skaffold and cosign version refreshes, and regenerated swagger and applyconfiguration files kept in sync with CEL and webhook validation comments in the core API types. That last one is the only entry hinting at anything structural — CEL-based validation on the API types implies declarative validation moving into the CRDs — but the commit itself changes only generated output.

◆ Prediction

This feed does not carry enough to predict product direction; until final releases or their notes appear here rather than only candidate tags, any read of where Fission is heading would be guesswork.

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.

Alternatives to Fission and Hatchet

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 Fission or Hatchet.

See all Fission alternatives → · See all Hatchet alternatives →

Recent activity from Fission and Hatchet

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

  1. 21h agoHatchetHatchet v0.115.0: contributor list update, no product notes
  2. 22h 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. 4mo agoFissionFission 1.25.0-rc1 tag carries only regenerated codegen output
  8. 5mo agoFissionFission 1.23.0-rc1 tag carries a CI tool-version refresh
  9. 10mo agoFissionv1.22.0-rc2
  10. 0y agoFissionFission 1.22.0-rc1 tag carries a golang.org/x/net bump

Frequently asked questions

What is the difference between Fission and Hatchet?

Both compete on the same themes — serverless — within Infra & APIs. 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 Fission better than Hatchet?

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

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

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.