Jackett
A daily indexer-repair treadmill: Jackett patches tracker definitions as fast as trackers change.
A side-by-side editorial comparison of Contour and Dashy — release velocity, themes, recent moves, and the top alternatives to consider.
Three supported branches, patched in lockstep within the same minute.
Contour maintains 1.31, 1.32 and 1.33 concurrently and releases them together — the February batch went out across three branches inside two minutes, and the March batch did the same. The content is almost entirely inherited: Envoy bumps to pick up security fixes, Go updates, and a gRPC update for a CVE that Contour explicitly notes it is not affected by.
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.
Contour maintains 1.31, 1.32 and 1.33 concurrently and releases them together — the February batch went out across three branches inside two minutes, and the March batch did the same. The content is almost entirely inherited: Envoy bumps to pick up security fixes, Go updates, and a gRPC update for a CVE that Contour explicitly notes it is not affected by.
This is a proxy whose release cadence is governed by its data plane rather than its own feature work. Envoy security releases set the schedule, and Contour's job is to bump, verify compatibility and ship across every supported branch simultaneously. The changes that do originate in Contour are operational sharp edges found in production: an HTTPProxy CRD schema wrongly marking a status error field as required, which broke load balancer status updates, and shutdown-manager being CPU-throttled at a 50m limit.
The next release will almost certainly be another simultaneous three-branch batch triggered by an Envoy security bump, since both batches in this window followed exactly that pattern.
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 Contour 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.
The changelog is a raw commit log, and its severity tags tell you more than the prose would.
The eBPF observability tool just started reaching for the GPU.
See all Contour 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 Contour alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Contour alternatives" section above for the current picks, or visit /alternatives/contour 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.