Windmill
Windmill is dismantling the paywall between itself and the data stack
A side-by-side editorial comparison of ESPHome and rsconnect — release velocity, themes, recent moves, and the top alternatives to consider.
ESPHome's August beta opens while the July line keeps absorbing hardware fixes.
ESPHome runs a monthly train and this window covers the tail of 2026.7 plus the opening of the 2026.8 beta. The 2026.7 patches were dominated by field-reported hardware corrections — sensor readings on emc2101, haier and as3935, an ENC28J60 SPI chip-select hold time flagged as breaking, a locked git clone cache so device adoption stops failing on first attempt, and a double-free when the API overflow buffer drain is re-entered. Bundled device-builder and dependabot bumps make up most of the row count in every patch.
The deployment client is being rebuilt around credentials it never has to store.
rsconnect is the publishing client for Posit Connect and shinyapps.io, and the last year has changed both ends of it. The HTTP layer moved to httr2 and the Connect API to v1; Posit Cloud publishing was removed outright and Posit Connect Cloud added in its place; and authentication picked up identity federation from Posit Workbench, Snowflake-hosted Connect with browser-based auth, and Snowflake connection names read from connections.toml. The most recent release fixes a regression that broke deployment entirely in air-gapped environments.
ESPHome runs a monthly train and this window covers the tail of 2026.7 plus the opening of the 2026.8 beta. The 2026.7 patches were dominated by field-reported hardware corrections — sensor readings on emc2101, haier and as3935, an ENC28J60 SPI chip-select hold time flagged as breaking, a locked git clone cache so device adoption stops failing on first attempt, and a double-free when the API overflow buffer drain is re-entered. Bundled device-builder and dependabot bumps make up most of the row count in every patch.
The pattern is stable and worth reading as maturity rather than stagnation: a feature release lands, then three or four patch releases correct the hardware paths that only fail in the field, each one narrow and attributed to a specific board or component. Concurrency and shared-state bugs — the WiFi scan results shared with the captive portal task, the clone cache, the buffer drain — recur often enough to look like the project's current soft spot. The beta tags carry no notes of their own and point at the release changelog instead.
2026.8.0 should reach a stable tag within days given the beta cadence, followed by the usual run of patch releases correcting per-component regressions. What is in it is not visible from these entries, which link out rather than summarize.
rsconnect is the publishing client for Posit Connect and shinyapps.io, and the last year has changed both ends of it. The HTTP layer moved to httr2 and the Connect API to v1; Posit Cloud publishing was removed outright and Posit Connect Cloud added in its place; and authentication picked up identity federation from Posit Workbench, Snowflake-hosted Connect with browser-based auth, and Snowflake connection names read from connections.toml. The most recent release fixes a regression that broke deployment entirely in air-gapped environments.
Two threads run through this. The first is credential elimination — every recent auth change replaces a stored secret with a token the runtime can mint, whether that is Workbench identity federation or a Snowflake connection profile. The second is dependency capture getting stricter about what it actually needs: renv profiles outside the project root, pak-installed packages resolved against configured repositories, and Bioconductor contacted only when a Bioconductor package is genuinely present. Both are the problems you hit deploying inside a regulated network.
Expect the httr2 escape hatch option to be removed once the migration settles, and expect the mcp content category added in 1.10.1 to grow real configuration rather than staying an inferred default.
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 rsconnect.
Windmill is dismantling the paywall between itself and the data stack
Resend is wiring itself into every agent runtime it can reach, one standard at a time
vdiffr finished its job in 2021 and has been tracking compilers ever since.
A package whose release calendar is written by whoever ships the next Rtools.
DNSControl v5 is feature complete and counting down to an August ship date
highr is finished software: one-line releases every year or two
See all ESPHome alternatives → · See all rsconnect 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 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 rsconnect alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "rsconnect alternatives" section above for the current picks, or visit /alternatives/rsconnect for the full list with editorial commentary on each.