DNSControl
DNSControl v5 is feature-frozen with a ship date, and rc9 is pure provider cleanup
A side-by-side editorial comparison of chromote and ESPHome — release velocity, themes, recent moves, and the top alternatives to consider.
chromote turned the browser itself into a pinned, downloadable dependency.
chromote drives headless Chrome from R over the DevTools Protocol and underpins the R screenshot and app-testing stack. The visible history is shaped almost entirely by Chrome's own changes: old headless mode removed, DevTools URLs moved, viewport APIs deprecated. Version 0.5.0 answered that by letting chromote fetch and pin specific Chrome builds itself.
ESPHome ships on a calendar, and the August beta train is now five builds deep
The 2026.8.0 beta line has reached its fifth build in six days. Every one of them is a version-bump merge commit with no release notes — b5 is 70 characters, and that is the entire record. The last entries with readable content are the 2026.7 patch releases, which is where per-component fixes and contributor work actually become visible.
chromote drives headless Chrome from R over the DevTools Protocol and underpins the R screenshot and app-testing stack. The visible history is shaped almost entirely by Chrome's own changes: old headless mode removed, DevTools URLs moved, viewport APIs deprecated. Version 0.5.0 answered that by letting chromote fetch and pin specific Chrome builds itself.
The package has moved from reacting to Chrome upgrades to controlling them. The 0.3.0 and 0.4.0 pair tracked the headless-mode transition by first adding an option and then flipping the default; 0.5.0 removed the need to track it at all by managing versioned binaries through Chrome for Testing. Alongside that, the session API keeps accumulating helpers that collapse multi-step DevTools call sequences, such as $go_to() and $set_viewport_size().
The version-management features shipped marked experimental, so the likely next step is stabilizing that API and extending the session helpers that wrap common DevTools sequences.
The 2026.8.0 beta line has reached its fifth build in six days. Every one of them is a version-bump merge commit with no release notes — b5 is 70 characters, and that is the entire record. The last entries with readable content are the 2026.7 patch releases, which is where per-component fixes and contributor work actually become visible.
The cadence is the product. Betas arrive every day or two as bump merges carrying no notes, the final release points at a changelog URL, and the real detail lands in the patch releases that follow it. Five betas in this cycle against four in the last suggests a slightly longer stabilization, but the feed gives no way to tell what is being stabilized. Anyone tracking ESPHome from this feed learns the release rhythm and nothing about the releases.
Expect 2026.8.0 final within days, followed by the 2026.8.x patch releases that will carry the first readable account of what the August cycle actually changed.
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 chromote or ESPHome.
DNSControl v5 is feature-frozen with a ship date, and rc9 is pure provider cleanup
Casdoor is spending its release cadence moving auth checks from the client to the server
Strimzi's 1.2.0 candidate closes with a logging fix and nothing else
Prowler's assistant decides what to do with findings; the patches keep the scanner honest
NetBox adds a cooling data model — the first new infrastructure domain since power
Two parallel trains, and the 'maintenance' label is now hiding real feature work
See all chromote alternatives → · See all ESPHome alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. ESPHome is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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. ESPHome is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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 chromote alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "chromote alternatives" section above for the current picks, or visit /alternatives/chromote for the full list with editorial commentary on each.
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.