← Back to home
Comparison · Infra & APIs

Lima vs Pacemaker

A side-by-side editorial comparison of Lima and Pacemaker — release velocity, themes, recent moves, and the top alternatives to consider.

Lima vs Pacemaker: at a glance

FeatureLimaPacemaker
SectorInfra & APIsInfra & APIs
Velocity score2.56.3
Sparks · 30d01
Top themeslocal virtualization, guest os support, windows guests, agent sandboxinghigh availability, cluster security, tls authentication, dual branch releases
Last editorial update3h ago3h ago
WebsiteVisit →Visit →

What is Lima?

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.

Read the full Lima trajectory →

What is Pacemaker?

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.

Read the full Pacemaker trajectory →

Lima vs Pacemaker: editorial side-by-side

L
Lima
INFRA · APIS
2.5

Lima keeps adding guest operating systems, and a flag to stop AI agents wrecking the host.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

P
Pacemaker
INFRA · APIS
6.3

Pacemaker is putting TLS and X509 auth between its cluster nodes, then hardening the wire code.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

Alternatives to Lima and Pacemaker

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.

See all Lima alternatives → · See all Pacemaker alternatives →

Recent activity from Lima and Pacemaker

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 11d agoPacemaker3.0.3: CVE-2026-10649 and remote message overflow fixes
  2. 23d agoLima2.2.0-rc.0: Windows 11 guests and a sudo opt-out
  3. 28d agoPacemaker3.0.2: PSK auth for remote CIB operations
  4. 28d agoPacemaker3.0.1: TLS and X509 authentication for Pacemaker Remote
  5. 28d agoPacemaker3.0.3-rc1: release candidate for the CVE fix set
  6. 1mo agoLima2.2.0-beta.0: Windows Server 2025 guests and TPM emulation
  7. 1mo agoPacemaker2.1.11: CVE-2026-10649 backported to the maintenance branch
  8. 1mo agoPacemaker2.1.11-rc1: release candidate for the 2.1 CVE backport
  9. 3mo agoLima2.1.2-beta.0: CLI mount and rsync path fixes
  10. 4mo agoLima2.1.0-rc.1: macOS and FreeBSD guests, plus an agent sync guard

Frequently asked questions

What is the difference between Lima and Pacemaker?

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.

Is Lima better than Pacemaker?

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.

What are the best alternatives to Lima?

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.

What are the best alternatives to Pacemaker?

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.