Hatchet
Hatchet takes durable tasks serverless, with handlers for Cloudflare Workers, Vercel and Node.
A side-by-side editorial comparison of Payload CMS and Userback — release velocity, themes, recent moves, and the top alternatives to consider.
Payload 4.0 beta 5 is a fix release with one adapter-facing breaking change.
Payload v4.0.0-beta.5 is a short fix list: password validation on reset, hidden fields excluded from GraphQL mutation inputs, plugins able to override other plugins' options, and signed upload receipts. Its one breaking change moves extra upload fields into clientData for adapters running without receipts, which no first-party adapter does. Beta releases now ship per-package SBOMs.
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.
Payload v4.0.0-beta.5 is a short fix list: password validation on reset, hidden fields excluded from GraphQL mutation inputs, plugins able to override other plugins' options, and signed upload receipts. Its one breaking change moves extra upload fields into clientData for adapters running without receipts, which no first-party adapter does. Beta releases now ship per-package SBOMs.
The 4.0 beta lands every three to five days, and each one is smaller than the last. beta.0 shipped the admin redesign, TanStack support and the new MCP. Later betas covered adapters, Next.js cache components and accessibility, and beta.5 is mostly correctness and supply-chain hygiene, which suggests a release candidate is close.
Expect one or two more fix-only betas, then a 4.0 release candidate. The SBOM addition suggests supply-chain artifacts will carry over to stable releases.
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.
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.
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.
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 Payload CMS or Userback.
Hatchet takes durable tasks serverless, with handlers for Cloudflare Workers, Vercel and Node.
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.
See all Payload CMS alternatives → · See all Userback alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Payload CMS 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Payload CMS 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.
Top Payload CMS alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Payload CMS alternatives" section above for the current picks, or visit /alternatives/payload-cms for the full list with editorial commentary on each.
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.