DNSControl
DNSControl is rewriting its record internals in public, one release candidate at a time
A side-by-side editorial comparison of Fission and Skipper — release velocity, themes, recent moves, and the top alternatives to consider.
Fission's release feed carries only RC tags, and none of them say what shipped
Every entry here is a release candidate — v1.22.0-rc1 and rc2, v1.23.0-rc1, v1.25.0-rc1 — with no final release appearing between them, and the version sequence skips 1.24 entirely. The bodies are whatever the tagging commit said, so what reaches this feed is a dependabot bump, a CLI tool-version refresh, a codegen sync explicitly labelled as having no functional change, and one entry that is nothing but links to an external release-highlights page. The actual release notes live on the project's documentation site, not here.
Skipper tags a release per commit — nine in eight days, and none of them change routing.
Skipper is Zalando's HTTP router and reverse proxy, cut as a GitHub tag on essentially every merged commit: v0.27.42 through v0.27.50 landed inside eight days. The content of that stream is maintenance — dependency group bumps, CI action upgrades, test corrections, and one internal refactor pulling the Valkey Del command and ratelimit ring client injection apart. The single change with user-visible effect in this window is a fix to the proxy listener binding on an insecure address.
Every entry here is a release candidate — v1.22.0-rc1 and rc2, v1.23.0-rc1, v1.25.0-rc1 — with no final release appearing between them, and the version sequence skips 1.24 entirely. The bodies are whatever the tagging commit said, so what reaches this feed is a dependabot bump, a CLI tool-version refresh, a codegen sync explicitly labelled as having no functional change, and one entry that is nothing but links to an external release-highlights page. The actual release notes live on the project's documentation site, not here.
What can be read from these tags is infrastructure maintenance rather than product direction: Go dependency updates, helm and kind and skaffold and cosign version refreshes, and regenerated swagger and applyconfiguration files kept in sync with CEL and webhook validation comments in the core API types. That last one is the only entry hinting at anything structural — CEL-based validation on the API types implies declarative validation moving into the CRDs — but the commit itself changes only generated output.
This feed does not carry enough to predict product direction; until final releases or their notes appear here rather than only candidate tags, any read of where Fission is heading would be guesswork.
Skipper is Zalando's HTTP router and reverse proxy, cut as a GitHub tag on essentially every merged commit: v0.27.42 through v0.27.50 landed inside eight days. The content of that stream is maintenance — dependency group bumps, CI action upgrades, test corrections, and one internal refactor pulling the Valkey Del command and ratelimit ring client injection apart. The single change with user-visible effect in this window is a fix to the proxy listener binding on an insecure address.
Nothing in these entries points to a direction change; the 0.27 line is in steady maintenance with supply-chain hygiene as the visible priority — oras-go pinned to a released version so osv-scanner stops flagging it, the CodeQL action upgraded, an OPA test hardened to deny requests with truncated bodies. The documentation change is the most revealing item: jwtValidation's behavior was unclear enough to prompt a proposed advisory, and the response was to clarify the docs rather than alter the code.
The tag stream will most likely continue at several releases a week with the same composition of dependency bumps and test fixes. These entries show no feature work in flight, so the next notable change is more likely another security-adjacent clarification than a new routing capability.
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 Fission or Skipper.
DNSControl is rewriting its record internals in public, one release candidate at a time
Kaniko's release feed stops dead in June 2024 after a patch that undid its own change
mod_auth_openidc audited itself, found eight holes, and broke every session on the way out
Kubernetes CNI maintaining four release branches at once, mostly to carry CVE fixes back.
KeePass-compatible password manager frozen mid-patch-run since 2021.
Overlay network that rewrote its certificate format, then spent a year fixing what it exposed.
See all Fission 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 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. Skipper 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 Fission alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Fission alternatives" section above for the current picks, or visit /alternatives/fission 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.