ESPHome
ESPHome 2026.9.0 ships template climate component, OTA encryption with API key, and ESP-NOW for ESP32-P4
A side-by-side editorial comparison of DNSControl and Skipper — release velocity, themes, recent moves, and the top alternatives to consider.
DNSControl v5 is feature-frozen with a ship date, and rc9 is pure provider cleanup
DNSControl has locked v5.0.0 to bugfixes only with a stated ship date of 25 August 2026. rc9 carries no new capability: punycode decoding before IDNA validation in ALIDNS, a SVCB fix in POWERDNS, NAPTR and trailing-dot fixes in DYNU, a dnssort edge case, and internal refactors replacing pkg/diff and standardising on models.Records. The release notes read as a call for provider testing more than an announcement.
Skipper adds Redis as a distributed L2 cache backend amid a high-frequency patch cadence.
Skipper is running in a maintenance-heavy patch cycle, shipping multiple versions per week focused on stability, test infrastructure, and minor performance work. The architectural addition this period is v0.27.92's Redis L2 storage for the cache() filter, which extends caching from node-local to cluster-shared. v0.27.95's parsed filter and predicate caching across RouteGroups is a performance improvement but stays within the current architecture.
DNSControl has locked v5.0.0 to bugfixes only with a stated ship date of 25 August 2026. rc9 carries no new capability: punycode decoding before IDNA validation in ALIDNS, a SVCB fix in POWERDNS, NAPTR and trailing-dot fixes in DYNU, a dnssort edge case, and internal refactors replacing pkg/diff and standardising on models.Records. The release notes read as a call for provider testing more than an announcement.
The v5 arc has run its course in public: rc1 laid out the dnsv2.RDATA refactor, rc3 finished converting every provider to it, rc4 completed the move to the Codeberg-hosted miekg/dns, and rc8 declared feature completeness. What is left is per-provider correctness on record types that only a handful of users exercise, which is why the maintainer is publishing a list of which providers most need testing rather than shipping.
Expect one or two more release candidates of provider fixes before the 25 August date, with the risk concentrated in providers nobody volunteers to test - the notes already flag PACKETFRAME as unmaintained and EXOSCALE as not supporting PTR.
Skipper is running in a maintenance-heavy patch cycle, shipping multiple versions per week focused on stability, test infrastructure, and minor performance work. The architectural addition this period is v0.27.92's Redis L2 storage for the cache() filter, which extends caching from node-local to cluster-shared. v0.27.95's parsed filter and predicate caching across RouteGroups is a performance improvement but stays within the current architecture.
The Redis L2 integration suggests the Skipper team is addressing the multi-replica cache coherence problem that large deployments encounter. If this pattern continues, distributed-state options—persistent rate limiting, distributed circuit breakers using the same Redis client abstraction—are the natural follow-ons. The high patch cadence signals active production deployment rather than feature-driven development.
The Redis client abstraction introduced in v0.27.92 will be extended to other stateful filters, particularly rate limiting, given that distributed rate limiting is the most common request for API gateways running at multi-replica scale.
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 DNSControl or Skipper.
ESPHome 2026.9.0 ships template climate component, OTA encryption with API key, and ESP-NOW for ESP32-P4
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
Kubernetes v1.37 matures its memory management and scheduling stack for AI/ML workloads.
GitHub Copilot gets cost-aware inference tiers as enterprise AI tooling tightens across the platform.
See all DNSControl alternatives → · See all Skipper alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Skipper is currently shipping more aggressively (velocity 7.5 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. Skipper is currently shipping more aggressively (velocity 7.5 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 DNSControl alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "DNSControl alternatives" section above for the current picks, or visit /alternatives/dnscontrol for the full list with editorial commentary on each.
Top Skipper alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Skipper alternatives" section above for the current picks, or visit /alternatives/skipper for the full list with editorial commentary on each.