Hatchet
Hatchet takes durable tasks serverless, with handlers for Cloudflare Workers, Vercel and Node.
A side-by-side editorial comparison of Payload CMS and Rancher — 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.
The 2.15 branch takes its own second candidate — an RBAC reconcile fix on the replica path.
Every live branch is mid-patch-round and they are resolving at different speeds. The 2.12 and 2.11 branches promoted to final tags carrying only the automated Dashboard ref bump. The 2.14 and 2.13 branches each cut an rc2 for a token-sync correctness fix. The newest branch, 2.15, has now cut its own rc2 for a different problem: inherited namespaced rule Roles were not being reconciled on the replica.
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.
Every live branch is mid-patch-round and they are resolving at different speeds. The 2.12 and 2.11 branches promoted to final tags carrying only the automated Dashboard ref bump. The 2.14 and 2.13 branches each cut an rc2 for a token-sync correctness fix. The newest branch, 2.15, has now cut its own rc2 for a different problem: inherited namespaced rule Roles were not being reconciled on the replica.
The feed continues to publish the branch matrix rather than what shipped in it, because supported-branch notes live behind the Prime docs. What is readable is which branches needed a second pass and for what: the two newest lines each took a distinct correctness fix before promotion while the older lines shipped plumbing only. Entry bodies here are truncated commit subjects, so the fixes are nameable but not scopeable.
Expect v2.15.1 to promote to a final tag once this candidate clears, following 2.12 and 2.11. The 2.14 and 2.13 finals carrying the token-sync fix are still outstanding in this feed.
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 Rancher.
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 Rancher 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 Rancher alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Rancher alternatives" section above for the current picks, or visit /alternatives/rancher for the full list with editorial commentary on each.