Dashy
The self-hosted dashboard finally let you drag things around instead of editing YAML.
A side-by-side editorial comparison of Jackett and Sonarr — release velocity, themes, recent moves, and the top alternatives to consider.
A daily-shipping indexer proxy whose entire product is a scraper definition file that never stops rotting.
Jackett ships a tagged release essentially every day, and every one of them is the same shape: tracker selectors updated, domains bumped, categories added, dead sites removed. The release notes are auto-generated commit lists with no prose. The C# application itself is stable; what changes is the YAML definition corpus that keeps a few hundred torrent trackers reachable through a single Torznab endpoint.
Sonarr's release feed is a two-month run of one-line fixes, most of them about qBittorrent auth.
Ten releases in this window, several cut hours apart, and almost every one carries a single change. The dominant thread is download-client authentication: basic auth for qBittorrent, reusing authentication cookies across qBittorrent calls, and backporting both to the v4 line — the same two fixes appearing repeatedly as they propagate across branches. The rest is a Jellyfin and Emby connection test with a new Jellyfin auth header, a language-handling correction, and dependency bumps for MailKit and FFprobe.
Jackett ships a tagged release essentially every day, and every one of them is the same shape: tracker selectors updated, domains bumped, categories added, dead sites removed. The release notes are auto-generated commit lists with no prose. The C# application itself is stable; what changes is the YAML definition corpus that keeps a few hundred torrent trackers reachable through a single Torznab endpoint.
This is maintenance-as-product, and the cadence is a symptom rather than a sign of momentum: trackers move domains, add anti-bot checks, and change markup, so the definitions decay continuously and the fix rate has to match. The visible trend across these releases is attrition — torr9, rockbox, rain, runtheframes, torrentleech-pl and elitetorrent-wf all removed in a single fortnight — partially offset by category expansion on the trackers that survive.
Expect the daily definition-churn cadence to continue unchanged, with the removal list growing faster than the addition list. Nothing in these entries indicates work on the application core.
Ten releases in this window, several cut hours apart, and almost every one carries a single change. The dominant thread is download-client authentication: basic auth for qBittorrent, reusing authentication cookies across qBittorrent calls, and backporting both to the v4 line — the same two fixes appearing repeatedly as they propagate across branches. The rest is a Jellyfin and Emby connection test with a new Jellyfin auth header, a language-handling correction, and dependency bumps for MailKit and FFprobe.
This is mature-product maintenance, and the failure surface is entirely at the integration boundary — the download clients and media servers Sonarr talks to change their auth behaviour, and Sonarr chases them. Releases are cut per-fix rather than batched, which produces a high tag count from a low volume of actual change. Nothing in this window touches Sonarr's own capability surface.
Expect the same pattern to continue: small single-change releases tracking download-client and media-server API shifts, with no visible feature work on the 4.0 line.
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 Jackett or Sonarr.
The self-hosted dashboard finally let you drag things around instead of editing YAML.
The web's duct-tape RSS layer, now quiet for a year after flipping every bridge on by default.
k0s ships one fix four times a day — the cost of keeping four Kubernetes branches current.
Microcks is quietly wiring LLM example generation into an API mocking tool built for Kubernetes.
Borg's long-running 2.0 beta finally landed packs — and warned it dropped back to alpha quality.
JuiceFS is spending its v1.4 cycle on metadata-engine efficiency, one transaction at a time.
See all Jackett alternatives → · See all Sonarr alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Jackett 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Jackett 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.
Top Jackett alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Jackett alternatives" section above for the current picks, or visit /alternatives/jackett for the full list with editorial commentary on each.
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.