← Back to home
Comparison · Infra & APIs

Hatchet vs Userback

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

Hatchet vs Userback: at a glance

FeatureHatchetUserback
SectorInfra & APIsInfra & APIs
Velocity score6.35.0
Sparks · 30d10
Top themesdurable execution, serverless, task queues, rate limitinguser-feedback, multi-site, agencies, integrations
Last editorial update9h ago14h 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 Userback?

Userback's Sites turn out to be a multi-site workspace, and the first follow-up targets agencies.

Userback has spent 2026 widening where feedback comes from (mobile SDK, Slack, mobile surveys) and adding an AI layer on top (Insights themes, video transcription, AI Context Search). The October 28 follow-up finally shows what Sites is: a per-site container with its own Site Key, settings, widget and feedback list. The new tools are prefixed readable feedback IDs that pass through to Jira, copying widget settings between Sites, open-feedback counts on the Sites page, and survey targeting by query string and hash.

Read the full Userback trajectory →

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

U
Userback
INFRA · APIS
5.0

Userback's Sites turn out to be a multi-site workspace, and the first follow-up targets agencies.

◆ Current state

Userback has spent 2026 widening where feedback comes from (mobile SDK, Slack, mobile surveys) and adding an AI layer on top (Insights themes, video transcription, AI Context Search). The October 28 follow-up finally shows what Sites is: a per-site container with its own Site Key, settings, widget and feedback list. The new tools are prefixed readable feedback IDs that pass through to Jira, copying widget settings between Sites, open-feedback counts on the Sites page, and survey targeting by query string and hash.

◆ Where it's heading

Sites moves Userback toward running many properties from one account. Copying widget settings and sorting Sites by open feedback are built for agencies with a Site per client. The readable IDs that travel into Jira and other integrations show the same push seen in the 'Sent to Integrations' filter: making Userback the traceable start of a ticket, not a separate inbox.

◆ Prediction

Expect more cross-Site tooling, such as copying integrations or templates between Sites, since the October 28 notes say integrations still have to be set up per Site.

Alternatives to Hatchet and Userback

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

See all Hatchet alternatives → · See all Userback alternatives →

Recent activity from Hatchet and Userback

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

  1. 13h agoHatchetPython SDK 1.43.2 parses 429 rate-limit errors
  2. 18h agoUserbackFeedback IDs, and more improvements for Sites
  3. 1d agoHatchetHatchet Serverless 0.1.0: durable tasks on Workers, Vercel, Node ⚡
  4. 1d agoHatchetEngine drops the advisory lock on DAG replays
  5. 1d agoHatchetv0.114.10: fix(ts): worker shutdown waiting for durable tasks correctly (#5346)
  6. 1d agoHatchetv0.114.9: fix(engine): partition pruning for task status update query (#5343)
  7. 1d agoHatchetRuby SDK 0.11.2 fixes Slack OAuth after 429 spec change
  8. 23d agoUserbackIntroducing Sites
  9. 2mo agoUserbackUserback Mobile SDK: Now With Surveys
  10. 3mo agoUserbackNew Feature: Notification History
  11. 3mo agoUserbackMerging Duplicate Feedback Just Got a Lot Faster
  12. 5mo agoUserbackNew Feature: Video Transcription

Frequently asked questions

What is the difference between Hatchet and Userback?

They serve adjacent needs but don't currently overlap on shipped themes. Hatchet is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 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 Userback?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Hatchet is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 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 Userback?

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