Jackett
A daily indexer-repair treadmill: Jackett patches tracker definitions as fast as trackers change.
A side-by-side editorial comparison of Lima and Pacemaker — 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.
Pacemaker is putting TLS and X509 auth between its cluster nodes, then hardening the wire code.
Two branches ship in parallel: the 3.0.x line carrying new work and 2.1.x taking backported fixes. The 3.0 series added TLS for Pacemaker Remote nodes, X509 authentication, TLS certificates for remote CIB operations, and then PSK authentication for those same operations, alongside large-IPC and multipart message support. The most recent releases on both branches are the same security train, fixing CVE-2026-10649 and a set of integer overflows and size checks in the remote message code.
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.
Two branches ship in parallel: the 3.0.x line carrying new work and 2.1.x taking backported fixes. The 3.0 series added TLS for Pacemaker Remote nodes, X509 authentication, TLS certificates for remote CIB operations, and then PSK authentication for those same operations, alongside large-IPC and multipart message support. The most recent releases on both branches are the same security train, fixing CVE-2026-10649 and a set of integer overflows and size checks in the remote message code.
The cluster's internal transport is being rebuilt on the assumption that the network between nodes is not trusted. Authentication and encryption arrived first, and the fixes that followed, overflow guards and a maximum remote message size, are the hardening pass on the same code paths. Release discipline is heavy and visible: each version ships a release candidate with an identical commit set days earlier, and every 3.0 release documents the regressions it introduced and where they were fixed.
Remote CIB operations now support both X509 certificates and PSK, and the recent fixes all sit in message framing and size limits; further work is most likely to continue in that message-handling code rather than adding another authentication mechanism.
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 Pacemaker.
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 Lima alternatives → · See all Pacemaker alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Pacemaker is currently shipping more aggressively (velocity 6.3 vs 2.5), with 1 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. Pacemaker is currently shipping more aggressively (velocity 6.3 vs 2.5), with 1 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 Pacemaker alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Pacemaker alternatives" section above for the current picks, or visit /alternatives/pacemaker for the full list with editorial commentary on each.