Skipper
Skipper adds RFC 9421 HTTP Message Signatures and delivers 21% RouteGroup load time improvement
A side-by-side editorial comparison of Certbot and ESPHome — release velocity, themes, recent moves, and the top alternatives to consider.
Certbot is consolidating its plugin architecture and quietly expanding into IP address certificate support.
Certbot is in a steady maintenance and architectural consolidation phase. The nginx and apache plugins have been moved into the core certbot package as private modules (certbot-apache and certbot-nginx now exist primarily to register the plugin), the OCSP module is deprecated, and pyOpenSSL dependencies are being systematically removed in favor of the cryptography library. Version 5.8.0 bumped the cryptography floor to >=47.0.0 and fixed a bug where removed domains were omitted from renewal confirmation prompts — a correctness issue for users who remove SANs from existing certificates.
ESPHome 2026.9.0 ships template climate component, OTA encryption with API key, and ESP-NOW for ESP32-P4
ESPHome 2026.9.0 is out, capping a beta cycle that added a template climate component (a long-requested flexible HVAC control primitive), OTA encryption keyed to the device's API key (hardening the update path), and ESP-NOW over hosted shim for the ESP32-P4. The beta cycle also included a systematic RAM allocation safety pass across the codebase — heap exhaustion now returns an error instead of panicking. Monthly releases continue landing at a consistent pace.
Certbot is in a steady maintenance and architectural consolidation phase. The nginx and apache plugins have been moved into the core certbot package as private modules (certbot-apache and certbot-nginx now exist primarily to register the plugin), the OCSP module is deprecated, and pyOpenSSL dependencies are being systematically removed in favor of the cryptography library. Version 5.8.0 bumped the cryptography floor to >=47.0.0 and fixed a bug where removed domains were omitted from renewal confirmation prompts — a correctness issue for users who remove SANs from existing certificates.
The architectural direction is a leaner, more self-contained core with fewer external dependencies. The IP address issuance capability added across the 5.3-5.4 cycle reflects Let's Encrypt's expanding IP certificate program — Certbot is tracking the CA's capabilities rather than driving its own feature agenda. The pyOpenSSL removal, when complete, will eliminate a long-standing external dependency that complicated builds and tested certification paths.
pyOpenSSL removal will complete in a future major release. IP address certificate workflows will mature as Let's Encrypt's IP cert program broadens. The certbot-nginx/certbot-apache split (now thin wrappers over the core package) may eventually collapse entirely.
ESPHome 2026.9.0 is out, capping a beta cycle that added a template climate component (a long-requested flexible HVAC control primitive), OTA encryption keyed to the device's API key (hardening the update path), and ESP-NOW over hosted shim for the ESP32-P4. The beta cycle also included a systematic RAM allocation safety pass across the codebase — heap exhaustion now returns an error instead of panicking. Monthly releases continue landing at a consistent pace.
ESPHome is expanding in two directions simultaneously: broader hardware support (ESP32-P4, BK72xx BLE, new platform components) and more robust runtime behavior (RAMAllocator pattern, use-after-free fixes, better BLE-WiFi coexistence). The template climate component is the most user-visible addition — it brings custom HVAC logic into ESPHome's declarative model, reducing the need for external Home Assistant automations. Audio stack (i2s, resampler, mixer) reliability is also a consistent focus.
The 2026.10.0 cycle will likely continue the RAMAllocator pattern across remaining allocating code paths and add more ESP32-P4-specific features. Audio (voice assistants, speakers) will stay a top area given the ongoing i2s reliability work.
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 Certbot or ESPHome.
Skipper adds RFC 9421 HTTP Message Signatures and delivers 21% RouteGroup load time improvement
ToolJet bundles MCP, multi-LLM switching, and PATs in a single beta — shifting from app builder to AI development platform
GitHub Copilot tightens enterprise governance while AI security scanning drops its CodeQL prerequisite
Redocly ships a built-in MCP server page across its entire docs platform, with public and authenticated endpoints
Expo kills its AI agent, SDK 58 beta arrives as EAS observability stack hits GA
Jackett in pure tracker-maintenance mode, daily domain and category updates only
See all Certbot 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 6.3 vs 2.5), 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. ESPHome is currently shipping more aggressively (velocity 6.3 vs 2.5), 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 Certbot alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Certbot alternatives" section above for the current picks, or visit /alternatives/certbot 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.