Jackett
A daily indexer-repair treadmill: Jackett patches tracker definitions as fast as trackers change.
A side-by-side editorial comparison of Lima and Contour — release velocity, themes, recent moves, and the top alternatives to consider.
Lima keeps adding guest operating systems, and a flag to stop AI agents wrecking the host.
Lima's release stream is a steady widening of what it can boot. The 2.1 line added experimental macOS and FreeBSD guests and a limactl shell --sync flag intended to keep AI agents from breaking host files; the 2.2 betas add experimental Windows Server 2025 and Windows 11 guests, TPM emulation under QEMU, a limactl screenshot command, and an option to turn off password-less sudo. Between those, the tags are CLI fixes and template maintenance.
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.
Lima's release stream is a steady widening of what it can boot. The 2.1 line added experimental macOS and FreeBSD guests and a limactl shell --sync flag intended to keep AI agents from breaking host files; the 2.2 betas add experimental Windows Server 2025 and Windows 11 guests, TPM emulation under QEMU, a limactl screenshot command, and an option to turn off password-less sudo. Between those, the tags are CLI fixes and template maintenance.
A tool that began as Linux VMs on macOS is becoming a general local virtualization front end, with macOS, FreeBSD, and Windows guests all arriving inside two release lines and much of it contributed through mentorship programs. A second thread is tightening the host boundary, with the sync flag, the sudo opt-out, and TPM emulation all narrowing what a guest can assume or reach. Everything guest-related is still marked experimental.
Each guest platform has arrived experimental and then accumulated follow-up pull requests; Windows support is at that stage now, so the next releases most likely stabilize it rather than add another operating system.
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 Lima 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 Lima 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. Lima is currently shipping more aggressively (velocity 2.5 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. Lima is currently shipping more aggressively (velocity 2.5 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 Lima alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Lima alternatives" section above for the current picks, or visit /alternatives/lima 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.