Windmill
Windmill is dismantling the paywall between itself and the data stack
A side-by-side editorial comparison of DNSControl and k0s — release velocity, themes, recent moves, and the top alternatives to consider.
DNSControl v5 is feature complete and counting down to an August ship date
DNSControl is running a long release-candidate train toward v5.0.0. The refactor replaces the internal record representation with dnsv2.RDATA, converts every provider, and completes the migration of the miekg/dns dependency from GitHub to Codeberg. As of rc8 the branch is declared feature complete with only bug fixes until the stated 25 August 2026 ship date.
k0s keeps four Kubernetes branches patched in lockstep, one backport at a time.
The release feed is four maintenance branches — 1.33 through 1.36 — moving in near-formation, plus a 1.37 alpha collecting the unbackported work. Almost every entry is a list of bot-authored bumps: Kubernetes patch versions, etcd, containerd, Calico, Traefik, CoreDNS, kube-router, Alpine and Go. The few human-authored items are small operational fixes, such as keeping the konnectivity server count above zero, distinguishing pending from performed restarts in Autopilot, and omitting an anonymous-auth default when the authentication config already sets it.
DNSControl is running a long release-candidate train toward v5.0.0. The refactor replaces the internal record representation with dnsv2.RDATA, converts every provider, and completes the migration of the miekg/dns dependency from GitHub to Codeberg. As of rc8 the branch is declared feature complete with only bug fixes until the stated 25 August 2026 ship date.
The stated goal is zero user-visible change: existing dnsconfig.js files keep working while legacy structures are bidirectionally converted underneath. The payoff is meant to arrive afterwards — faster adoption of new DNS record types, easier custom record types, and lower memory use from removing old fields. The release notes lean heavily on volunteer testing for the least-used providers.
Expect v5.0.0 to ship on or near the announced date, with the record-type additions the refactor was built to enable following in the 5.x line.
The release feed is four maintenance branches — 1.33 through 1.36 — moving in near-formation, plus a 1.37 alpha collecting the unbackported work. Almost every entry is a list of bot-authored bumps: Kubernetes patch versions, etcd, containerd, Calico, Traefik, CoreDNS, kube-router, Alpine and Go. The few human-authored items are small operational fixes, such as keeping the konnectivity server count above zero, distinguishing pending from performed restarts in Autopilot, and omitting an anonymous-auth default when the authentication config already sets it.
This is a distribution whose product is currency and consistency: the same fix reaches every supported branch within days, and the component matrix stays close to upstream. Autopilot is the one area receiving actual behavior work rather than version bumps, which is where a self-managing cluster story would have to come from. The 1.37 alpha line is where riscv64 support and larger refactors are accumulating.
Expect the 1.37 line to move from alpha toward a release candidate with the riscv64 and etcd 3.7 work carried forward, while 1.33 through 1.36 continue their weekly bump cadence.
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 k0s.
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.
The deployment client is being rebuilt around credentials it never has to store.
A package whose release calendar is written by whoever ships the next Rtools.
highr is finished software: one-line releases every year or two
See all DNSControl 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. DNSControl and k0s are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). 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. DNSControl and k0s are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). 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 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.