Verdaccio
Verdaccio's v9 pre-release counter reaches 41, and the notes still say nothing
A side-by-side editorial comparison of Lima and Payload CMS — release velocity, themes, recent moves, and the top alternatives to consider.
Lima 2.3 nears release, with a Windows path that drops QEMU and a new TUI
Lima v2.3.0-rc.0 is out with an experimental HCS driver that removes the QEMU dependency on Windows hosts, block device attachment for VZ guests on macOS, and experimental shared, host and bridged networks on Linux hosts. limactl menu adds a menu-based interface, which now opens when limactl runs on a terminal without arguments. The default Ubuntu template moves to 26.10.
Payload's v4 beta ships every few days, and most of the risk sits in the breaking-change notes
Payload is working through a v4 beta line, with six betas tagged between October 13 and October 29. Each carries fixes plus a short list of breaking changes: stable TanStack Start and nodemailer 10 in beta.2, React Flight for TanStack RSC responses in beta.3, a changed uploadReference contract in beta.5, and Lexical 0.53 in beta.6. The other steady thread is accessibility, with audit findings closed across several betas.
Lima v2.3.0-rc.0 is out with an experimental HCS driver that removes the QEMU dependency on Windows hosts, block device attachment for VZ guests on macOS, and experimental shared, host and bridged networks on Linux hosts. limactl menu adds a menu-based interface, which now opens when limactl runs on a terminal without arguments. The default Ubuntu template moves to 26.10.
The any-guest, any-host direction now reaches all three desktop platforms in one release, and each host gets a feature suited to its own virtualization stack. The menu interface is a different kind of addition: it aims at people who do not want to memorize the CLI. LFX mentees and outside contributors continue to carry much of this work, and the project's experimental-first labeling still applies to the biggest items.
A 2.3.0 final is the next step after rc.0. The HCS driver and Linux network modes should stay experimental there, following the pattern earlier platform additions took.
Payload is working through a v4 beta line, with six betas tagged between October 13 and October 29. Each carries fixes plus a short list of breaking changes: stable TanStack Start and nodemailer 10 in beta.2, React Flight for TanStack RSC responses in beta.3, a changed uploadReference contract in beta.5, and Lexical 0.53 in beta.6. The other steady thread is accessibility, with audit findings closed across several betas.
The betas are widening where Payload runs rather than adding headline features: TanStack Start is treated as a real target alongside Next.js, and cache components arrived in beta.3. Accessibility and restore behaviour keep taking fixes, which reads as hardening of the admin UI before a stable cut. The breaking-change lists have stayed short and mostly hit integrators, such as custom transports, Lexical users and third-party upload adapters.
More betas on the same two-to-five-day spacing are the likely next step. The entries give no stable date, so the v4.0.0 timing is unclear.
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 Payload CMS.
Verdaccio's v9 pre-release counter reaches 41, and the notes still say nothing
Snort 3.12.4 pairs a long memory-safety pass with detection speed work
Nineteen patches into 3.2, HAProxy's ingress controller is mostly bumping dependencies
Honeycomb is working on the first ten minutes, not just the incident
Talos 1.15's alpha keeps moving: a silent containerd config trap and declarative CPU control
Pinot 1.6 adds SQL DDL and vector backends, and now needs Java 25 to run its services.
See all Lima alternatives → · See all Payload CMS alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Lima and Payload CMS are shipping at a similar cadence (velocity 5.0 vs 5.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. Lima and Payload CMS are shipping at a similar cadence (velocity 5.0 vs 5.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 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 Payload CMS alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Payload CMS alternatives" section above for the current picks, or visit /alternatives/payload for the full list with editorial commentary on each.