Rancher
The public feed carries tags and image manifests; the release notes live in Prime docs.
A side-by-side editorial comparison of ESPHome and Dokploy — release velocity, themes, recent moves, and the top alternatives to consider.
ESPHome's July line is all maintenance: bot bumps, build fixes, one breaking ethernet change.
ESPHome is four patches into the 2026.7 cycle, and the patch content is dominated by bundled esphome-device-builder bumps, dependabot updates, and toolchain fixes on the ESP-IDF and Zephyr build paths. The user-visible fixes are narrow and hardware-specific: sensor readings on emc2101, haier and as3935, epaper init defaults, and device adoption failing on first attempt because the git clone cache was unlocked. 2026.7.3 carried an explicitly flagged breaking change to ENC28J60 SPI chip-select hold time.
A self-hosted PaaS spending its releases on secrets, injection fixes and plan limits.
Dokploy cuts patch releases every one to two weeks, and the recent stream is dominated by hardening rather than features. v0.29.12 added AES-256-GCM encryption for environment variables at rest and made backups carry the full keyring; v0.29.13 closed an OS command injection in git clone across all providers. The newest tag says outright that it is bug fixes only. Alongside that, plan limits landed in v0.29.10.
ESPHome is four patches into the 2026.7 cycle, and the patch content is dominated by bundled esphome-device-builder bumps, dependabot updates, and toolchain fixes on the ESP-IDF and Zephyr build paths. The user-visible fixes are narrow and hardware-specific: sensor readings on emc2101, haier and as3935, epaper init defaults, and device adoption failing on first attempt because the git clone cache was unlocked. 2026.7.3 carried an explicitly flagged breaking change to ENC28J60 SPI chip-select hold time.
The July line is stabilisation rather than expansion — the feature content lives in the 2026.7.0 release the beta tags led up to, and everything since has been build-system and per-component correction. Automated bumps now make up a large share of each patch note, which makes the changelog a poor read on what actually changed for users. The through-line is a build toolchain ESPHome increasingly owns end to end, via the bundled device-builder it keeps rev-ing.
Expect the 2026.8.0 betas to open shortly and reset the cycle, with one or two more bump-heavy patches closing out the 2026.7 line first.
Dokploy cuts patch releases every one to two weeks, and the recent stream is dominated by hardening rather than features. v0.29.12 added AES-256-GCM encryption for environment variables at rest and made backups carry the full keyring; v0.29.13 closed an OS command injection in git clone across all providers. The newest tag says outright that it is bug fixes only. Alongside that, plan limits landed in v0.29.10.
The direction is a self-hosted platform trying to earn production trust: encrypted secrets, injection fixes, a pinned install script tied to each release, and Postgres query rewrites to stop hitting the 100-argument limit on rollbacks, schedules and backups. Plan limits point the other way — toward a commercial tier layered on the open-source core. Both arcs suggest the project is past feature-chasing and into making the platform defensible.
Expect the hardening thread to continue into the rest of the 0.29 line, with the plan-limits work being the seed of a paid tier that gets more definition before a 0.30 release.
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 Dokploy.
The public feed carries tags and image manifests; the release notes live in Prime docs.
Three release channels at once as werf 3 takes shape beside a still-shipping 2.75.
Volatility 3 caught up with Volatility 2, then started reorganising itself.
A small LDAP server that grew OpenTelemetry tracing, embedded plugins and RISC-V builds.
OctoPrint 2.0 turns serial into one connector among several, and breaks plugins doing it.
Patch tags land monthly with release notes that itemize nothing.
See all ESPHome alternatives → · See all Dokploy alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Dokploy 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. Dokploy 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 Dokploy alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Dokploy alternatives" section above for the current picks, or visit /alternatives/dokploy for the full list with editorial commentary on each.