Jackett
A daily indexer-repair treadmill: Jackett patches tracker definitions as fast as trackers change.
A side-by-side editorial comparison of Cloudflare Tunnel and Contour — release velocity, themes, recent moves, and the top alternatives to consider.
Ships on a calendar cadence and tells you nothing about what changed.
cloudflared tags releases on a date-based scheme — 2026.6.0 through 2026.7.3 — at roughly one to three per month. The release notes contain nothing but SHA256 checksums for the build matrix. There is no change description, no fixed-issue list, and no feature note in any entry in the visible window.
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.
cloudflared tags releases on a date-based scheme — 2026.6.0 through 2026.7.3 — at roughly one to three per month. The release notes contain nothing but SHA256 checksums for the build matrix. There is no change description, no fixed-issue list, and no feature note in any entry in the visible window.
What the checksums do reveal is the shape of the distribution: packages for macOS as pkg and tgz on both architectures, Linux across 386, amd64 and arm64 as raw binaries, deb and rpm, and a separate FIPS-validated Linux build line. That FIPS variant shipping in every release points at regulated and government deployments as a supported constituency. Beyond packaging breadth, this feed does not support conclusions about product direction.
The date-based tags will keep arriving on the same monthly rhythm. What goes into them is not something this changelog reveals — readers who need that have to go to the repository's commit history instead.
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 Cloudflare Tunnel 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 Cloudflare Tunnel 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. Cloudflare Tunnel is currently shipping more aggressively (velocity 5.0 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. Cloudflare Tunnel is currently shipping more aggressively (velocity 5.0 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 Cloudflare Tunnel alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Cloudflare Tunnel alternatives" section above for the current picks, or visit /alternatives/cloudflared 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.