Jackett
A daily indexer-repair treadmill: Jackett patches tracker definitions as fast as trackers change.
A side-by-side editorial comparison of Cobbler and Dashy — release velocity, themes, recent moves, and the top alternatives to consider.
A backport branch kept alive for downstreams, with the main line nowhere in sight.
Every release in Cobbler's visible history describes itself the same way: backports from main to make Cobbler more stable for the community. The 3.3.x line has absorbed real work under that framing — collection indices, lazy loading, new XML-RPC endpoints — but none of it originates here. The most recent item is a 3.2.3 build carrying the CVE-2024-47533 fix to an older branch, with its Fixed and Added sections left as literal TBD placeholders.
After 4.5.0's drag-and-drop release, the version number is outrunning the product.
Dashy shipped 4.5.0 in late July with drag-and-drop editing and a new widget, and everything since has been patch work. Across the six most recent releases, three are automated dependency bumps, one adds missing German translations, one fixes an out-of-memory crash, and one adds an OIDC post-logout redirect. Releases land every one to three days, each cut from a single pull request. Maintenance is visibly split between the project owner and a dependency bot.
Every release in Cobbler's visible history describes itself the same way: backports from main to make Cobbler more stable for the community. The 3.3.x line has absorbed real work under that framing — collection indices, lazy loading, new XML-RPC endpoints — but none of it originates here. The most recent item is a 3.2.3 build carrying the CVE-2024-47533 fix to an older branch, with its Fixed and Added sections left as literal TBD placeholders.
This is a stabilization branch serving downstream packagers rather than a product advancing on its own. The work that does land splits cleanly into three buckets: distribution coverage (Ubuntu 22.04, Debian 12, AlmaLinux, RHEL9, openSUSE and SLE signatures), API surface for integrators, and security backports. 3.3.3 flagged dump_vars as the replacement for get_blended_data as of 3.4.0 — a version that has not appeared in any release since.
Expect continued single-purpose backports to 3.3.x and older branches as CVEs surface; the entries give no indication of when or whether the 3.4.0 work these releases keep deferring to will ship.
Dashy shipped 4.5.0 in late July with drag-and-drop editing and a new widget, and everything since has been patch work. Across the six most recent releases, three are automated dependency bumps, one adds missing German translations, one fixes an out-of-memory crash, and one adds an OIDC post-logout redirect. Releases land every one to three days, each cut from a single pull request. Maintenance is visibly split between the project owner and a dependency bot.
The cadence follows a repeating shape: a feature release, then a long tail of single-PR patches, and 4.5 is deep into that tail. The human-authored work skews toward self-hosting operations - authentication flows and crash fixes - rather than the dashboard surface itself. That fits a project whose users run their own instance and care most about it staying up between restarts.
Expect the 4.5.x train to keep releasing roughly per merged pull request until a 4.6.0 gathers the next batch of user-facing features; on this evidence the intervening entries will be dependency bumps with occasional auth and stability fixes.
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 Cobbler or Dashy.
A daily indexer-repair treadmill: Jackett patches tracker definitions as fast as trackers change.
Ten days of bulk operations, then the AI assistant got the keys to multi-site access control.
A v5 release candidate train carrying a database migrator that has to work on the first try.
The syslog daemon is quietly becoming an OpenTelemetry-era pipeline, YAML config and all.
Three supported branches, patched in lockstep within the same minute.
The changelog is a raw commit log, and its severity tags tell you more than the prose would.
See all Cobbler alternatives → · See all Dashy alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Dashy is currently shipping more aggressively (velocity 6.3 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. Dashy is currently shipping more aggressively (velocity 6.3 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 Cobbler alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Cobbler alternatives" section above for the current picks, or visit /alternatives/cobbler for the full list with editorial commentary on each.
Top Dashy alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Dashy alternatives" section above for the current picks, or visit /alternatives/dashy for the full list with editorial commentary on each.