Hatchet
Hatchet takes durable tasks serverless, with handlers for Cloudflare Workers, Vercel and Node.
A side-by-side editorial comparison of ESPHome and Payload CMS — release velocity, themes, recent moves, and the top alternatives to consider.
ESPHome 2026.10.1 follows the .0 by six days with OTA, MQTT and codegen fixes.
ESPHome shipped 2026.10.1 on Oct 27, six days after 2026.10.0. The patch keeps the OTA watchdog timeout on ESP32 hosted coprocessors, resends a fan's MQTT state when the first publish fails, fixes generated C++ for infinite floats, and handles version-less library dependencies the way PlatformIO does. 2026.10.0 itself rolled up six betas of ESP-IDF 6.1 groundwork, audio tuning and RAM savings.
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.
ESPHome shipped 2026.10.1 on Oct 27, six days after 2026.10.0. The patch keeps the OTA watchdog timeout on ESP32 hosted coprocessors, resends a fan's MQTT state when the first publish fails, fixes generated C++ for infinite floats, and handles version-less library dependencies the way PlatformIO does. 2026.10.0 itself rolled up six betas of ESP-IDF 6.1 groundwork, audio tuning and RAM savings.
The monthly train is predictable: about three weeks of betas, a .0, then a .1 patch within two weeks. The focus this cycle was memory footprint on constrained chips and preparing for ESP-IDF 6.1, and the .1 is cleanup of codegen and build edge cases.
Expect the 2026.11 betas to start in early November, likely carrying more ESP-IDF 6.1 migration, and possibly a 2026.10.2 if more regressions surface.
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 ESPHome 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 ESPHome 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 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 ESPHome alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "ESPHome alternatives" section above for the current picks, or visit /alternatives/esphome 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.