Jackett
A daily indexer-repair treadmill: Jackett patches tracker definitions as fast as trackers change.
A side-by-side editorial comparison of Scrypted and Contour — release velocity, themes, recent moves, and the top alternatives to consider.
Scrypted spent a year making its camera server run as a cluster, then went quiet.
Scrypted publishes releases as raw commit dumps, so the arc has to be read from the commits themselves. Through 2025 they cluster around three things: cluster mode and the worker addressing needed to make it real, GPU inference plumbing for NVIDIA on Proxmox and Intel runtimes, and a steady stream of per-camera fixes for battery, sleeping, and NVR devices. The most recent tag in this feed is from November 2025, so the visible record stops there rather than continuing to the present.
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.
Scrypted publishes releases as raw commit dumps, so the arc has to be read from the commits themselves. Through 2025 they cluster around three things: cluster mode and the worker addressing needed to make it real, GPU inference plumbing for NVIDIA on Proxmox and Intel runtimes, and a steady stream of per-camera fixes for battery, sleeping, and NVR devices. The most recent tag in this feed is from November 2025, so the visible record stops there rather than continuing to the present.
The direction through the tracked window is a home camera server growing into distributed infrastructure: cluster mode, cluster-aware media management, worker addressing, and detection work moving onto custom models and fp16 math. Integration breadth continues alongside it, with HomeKit audio, ONVIF PTZ, text overlays, and PIR sensors. Because the feed has not produced a tag in months, any read on current direction should be treated as the state at the last release rather than today.
The entries do not support a confident prediction; the feed has been silent since November 2025, and a stale release stream is not evidence of what the project is doing now.
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.
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 Scrypted or Contour.
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 Scrypted alternatives → · See all Contour alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Scrypted and Contour are shipping at a similar cadence (velocity 0.0 vs 0.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. Scrypted and Contour are shipping at a similar cadence (velocity 0.0 vs 0.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 Scrypted alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Scrypted alternatives" section above for the current picks, or visit /alternatives/scrypted for the full list with editorial commentary on each.
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.