Fission
Fission's release feed carries only RC tags, and none of them say what shipped
Comparison · Infra & APIs
DNSControl vs Sonarr
A side-by-side editorial comparison of DNSControl and Sonarr — release velocity, themes, recent moves, and the top alternatives to consider.
DNSControl vs Sonarr: at a glance
What is DNSControl?
DNSControl is rewriting its record internals in public, one release candidate at a time
DNSControl is mid-way through a v5 refactor being shipped as a visible candidate series — rc1 through rc4 in roughly two weeks, all of them explicitly promising zero user-facing change. The work replaces how DNS record fields are stored internally with a dnsv2.RDATA type, with legacy structs converted bidirectionally so existing providers keep working untouched. Two other threads run alongside: migrating the miekg/dns dependency from GitHub to Codeberg, now complete and no longer dual-imported, and removing old fields to cut memory use. The release notes read as direct appeals to users — naming nine providers nobody has tested and asking for volunteers, and inviting anyone to a monthly community call.
What is Sonarr?
Sonarr is in pure maintenance mode — six releases, not one feature.
Six point releases in this window and none of them carries a feature. The changes are an ordering fix so free space is not checked when another specification has already failed, unexpected database language values normalized to Unknown, basic auth repaired for qBittorrent, and a Jellyfin and Emby connection test with a new Jellyfin auth header. One release ships with no changelog entry at all.
DNSControl vs Sonarr: editorial side-by-side
DNSControl
5.0INFRA · APIS
DNSControl is rewriting its record internals in public, one release candidate at a time
◆ Current state
DNSControl is mid-way through a v5 refactor being shipped as a visible candidate series — rc1 through rc4 in roughly two weeks, all of them explicitly promising zero user-facing change. The work replaces how DNS record fields are stored internally with a dnsv2.RDATA type, with legacy structs converted bidirectionally so existing providers keep working untouched. Two other threads run alongside: migrating the miekg/dns dependency from GitHub to Codeberg, now complete and no longer dual-imported, and removing old fields to cut memory use. The release notes read as direct appeals to users — naming nine providers nobody has tested and asking for volunteers, and inviting anyone to a monthly community call.
◆ Where it's heading
The stated goals are about future velocity rather than present features: making new DNS record types faster to adopt and custom record types easier to implement. That is a bet that the bottleneck on supporting new record types was the internal representation, and it is being paid for with a long candidate series rather than a big-bang release. The provider conversion finished during this window — rc3 declares all providers converted with long-tail work remaining — so the refactor is past its riskiest stretch.
◆ Prediction
The maintainer states v5.x is on schedule to ship before September, and the untested-provider list is the visible blocker; expect further candidates focused on provider coverage rather than new goals.
Sonarr
5.0INFRA · APIS
Sonarr is in pure maintenance mode — six releases, not one feature.
◆ Current state
Six point releases in this window and none of them carries a feature. The changes are an ordering fix so free space is not checked when another specification has already failed, unexpected database language values normalized to Unknown, basic auth repaired for qBittorrent, and a Jellyfin and Emby connection test with a new Jellyfin auth header. One release ships with no changelog entry at all.
◆ Where it's heading
This is a mature application on a stable branch, and the work is reactive: download clients and media servers change upstream, integrations break, Sonarr repairs them. The qBittorrent basic auth fix appearing on both the 4.0.18 and 4.0.19 lines shows a project deliberately keeping a maintenance branch alive rather than pushing everyone forward.
◆ Prediction
Nothing in these entries points to a feature cycle. Expect the same pattern — small point releases tracking upstream changes in download clients and media servers — to continue.
Alternatives to DNSControl and Sonarr
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 Sonarr.
Kaniko
Kaniko's release feed stops dead in June 2024 after a patch that undid its own change
mod_auth_openidc
mod_auth_openidc audited itself, found eight holes, and broke every session on the way out
Antrea
Kubernetes CNI maintaining four release branches at once, mostly to carry CVE fixes back.
KeeWeb
KeePass-compatible password manager frozen mid-patch-run since 2021.
Nebula
Overlay network that rewrote its certificate format, then spent a year fixing what it exposed.
See all DNSControl alternatives → · See all Sonarr alternatives →
Recent activity from DNSControl and Sonarr
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 13h agoSonarrSkip free space check when an earlier specification fails
- 6d agoSonarrPoint release 4.0.19.2997 with no listed changes
- 8d agoDNSControlDNSControl v5 rc4 completes the move to Codeberg-hosted miekg/dns
- 9d agoDNSControlDNSControl v5 rc3 finishes converting every provider
- 15d agoSonarrJellyfin and Emby connection test, new Jellyfin auth header
- 16d agoSonarrUnexpected stored languages now treated as Unknown
- 19d agoDNSControlDNSControl v5 rc2 continues the internal rewrite
- 21d agoDNSControlDNSControl v5 rc1 lays out the dnsv2.RDATA refactor
- 1mo agoSonarrBasic auth fixed for qBittorrent
- 1mo agoSonarrqBittorrent basic auth fix backported to 4.0.18
Frequently asked questions
What is the difference between DNSControl and Sonarr?
They serve adjacent needs but don't currently overlap on shipped themes. DNSControl and Sonarr 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.
Is DNSControl better than Sonarr?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. DNSControl and Sonarr 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.
What are the best alternatives to DNSControl?
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.
What are the best alternatives to Sonarr?
Top Sonarr alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Sonarr alternatives" section above for the current picks, or visit /alternatives/sonarr for the full list with editorial commentary on each.