ClouDNS
ClouDNS widens its SSL catalog and adds maintenance windows to monitoring
A side-by-side editorial comparison of Home Assistant and k0s — release velocity, themes, recent moves, and the top alternatives to consider.
Home Assistant keeps pulling hidden power-user features into the UI, now trigger IDs.
Home Assistant ships one release a month, each built around a friction point that used to need YAML or a buried menu. 2026.10 gives trigger IDs a proper UI, so one automation can branch on several triggers without hand-written IDs, and replaces the map with a vector OpenStreetMap after the old provider started requiring an API key. It also adds a Modbus connections panel, one-click AI connection and 15 new integrations.
k0s opens its 1.37 line while security fixes ride the older branches.
k0s published v1.37.1 alongside 1.36.5, 1.35.9 and 1.34.12 on the same morning, so four branches are now live. The older branches took Kubernetes patch bumps, etcd 3.6.15 and deferred manifest directory creation, and 1.36 also scoped the worker autopilot to its own Node. In September, 1.36.4+k0s.1 and 1.35.8+k0s.1 shipped a fix for GHSA-qjgc-wmg7-3jc3, with csr-approver hardening on the 1.35 branch.
Home Assistant ships one release a month, each built around a friction point that used to need YAML or a buried menu. 2026.10 gives trigger IDs a proper UI, so one automation can branch on several triggers without hand-written IDs, and replaces the map with a vector OpenStreetMap after the old provider started requiring an API key. It also adds a Modbus connections panel, one-click AI connection and 15 new integrations.
The 2026 run reads as a single program: infrared in April, radio frequency in May, purpose-specific triggers by default in July, shared Modbus connections in September, trigger IDs in October. Each release takes something experts already had and makes it findable. Nabu Casa is also renaming Home Assistant Cloud to Home Assistant Link, planned for the December release.
The Cloud-to-Link rename is scheduled for the December release, so expect it there; the November release will most likely take on another automation or dashboard feature that still needs YAML.
k0s published v1.37.1 alongside 1.36.5, 1.35.9 and 1.34.12 on the same morning, so four branches are now live. The older branches took Kubernetes patch bumps, etcd 3.6.15 and deferred manifest directory creation, and 1.36 also scoped the worker autopilot to its own Node. In September, 1.36.4+k0s.1 and 1.35.8+k0s.1 shipped a fix for GHSA-qjgc-wmg7-3jc3, with csr-approver hardening on the 1.35 branch.
The branch-parallel pattern is holding and now has a new top line. Lifecycle safety stays the core work: reset steps wired to contexts, autopilot retries and discovery refreshes, and autopilot scope limited to its own node. The 1.37 notes read as a long development log rather than a curated release, which fits a project that lets upstream Kubernetes carry the feature story.
Expect the next Kubernetes patch round to reach all four branches within hours of each other, and the oldest of them to drop off now that 1.37 is out, though these notes do not state a support window.
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 Home Assistant or k0s.
ClouDNS widens its SSL catalog and adds maintenance windows to monitoring
fossa-cli's feed jumps from 3.17 to 3.20, with clearer container scan errors.
Gloo Gateway's October batch fixes proxies that silently kept stale endpoints.
Traefik v3.8 rc.1 is a Gateway API release; v2.11 keeps getting security patches.
Render's autumn changelog is plan tuning and runtime defaults while Workflows fills out.
Alertmanager 0.34.2 turns off CORS by default, breaking cross-origin API calls.
See all Home Assistant alternatives → · See all k0s alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. k0s is currently shipping more aggressively (velocity 5.0 vs 2.5), 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. k0s is currently shipping more aggressively (velocity 5.0 vs 2.5), 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 Home Assistant alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Home Assistant alternatives" section above for the current picks, or visit /alternatives/home-assistant for the full list with editorial commentary on each.
Top k0s alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "k0s alternatives" section above for the current picks, or visit /alternatives/k0s for the full list with editorial commentary on each.