Hatchet
Hatchet takes durable tasks serverless, with handlers for Cloudflare Workers, Vercel and Node.
A side-by-side editorial comparison of Contour and Payload CMS — release velocity, themes, recent moves, and the top alternatives to consider.
Three supported branches, patched in lockstep within the same minute.
Contour maintains 1.31, 1.32 and 1.33 concurrently and releases them together — the February batch went out across three branches inside two minutes, and the March batch did the same. The content is almost entirely inherited: Envoy bumps to pick up security fixes, Go updates, and a gRPC update for a CVE that Contour explicitly notes it is not affected by.
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.
Contour maintains 1.31, 1.32 and 1.33 concurrently and releases them together — the February batch went out across three branches inside two minutes, and the March batch did the same. The content is almost entirely inherited: Envoy bumps to pick up security fixes, Go updates, and a gRPC update for a CVE that Contour explicitly notes it is not affected by.
This is a proxy whose release cadence is governed by its data plane rather than its own feature work. Envoy security releases set the schedule, and Contour's job is to bump, verify compatibility and ship across every supported branch simultaneously. The changes that do originate in Contour are operational sharp edges found in production: an HTTPProxy CRD schema wrongly marking a status error field as required, which broke load balancer status updates, and shutdown-manager being CPU-throttled at a 50m limit.
The next release will almost certainly be another simultaneous three-branch batch triggered by an Envoy security bump, since both batches in this window followed exactly that pattern.
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.
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 Contour or Payload CMS.
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 Contour alternatives → · See all Payload CMS 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 0.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 0.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 Contour alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Contour alternatives" section above for the current picks, or visit /alternatives/contour for the full list with editorial commentary on each.
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.