← Back to home
Comparison · Infra & APIs

Pacemaker vs Skipper

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

Pacemaker vs Skipper: at a glance

FeaturePacemakerSkipper
SectorInfra & APIsInfra & APIs
Velocity score6.36.3
Sparks · 30d00
Top themeshigh availability, cluster security, tls authentication, dual branch releasesapi-gateway, http-proxy, rfc9421, performance
Last editorial update1mo ago5m ago
WebsiteVisit →Visit →

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 →

What is Skipper?

Skipper adds RFC 9421 HTTP Message Signatures and delivers 21% RouteGroup load time improvement

Skipper v0.27 is shipping at a steady maintenance cadence with two functional additions of note: v0.27.96 adds native RFC 9421 HTTP Message Signatures filter support — a 2023 IETF standard for request signing gaining traction in financial services and regulated APIs. v0.27.95 delivers a shared parse cache across RouteGroups, producing a measured 21% load time reduction, 12% lower memory, and 26% fewer allocations on a 200-RouteGroup benchmark.

Read the full Skipper trajectory →

Pacemaker vs Skipper: editorial side-by-side

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.

S
Skipper
INFRA · APIS
6.3

Skipper adds RFC 9421 HTTP Message Signatures and delivers 21% RouteGroup load time improvement

◆ Current state

Skipper v0.27 is shipping at a steady maintenance cadence with two functional additions of note: v0.27.96 adds native RFC 9421 HTTP Message Signatures filter support — a 2023 IETF standard for request signing gaining traction in financial services and regulated APIs. v0.27.95 delivers a shared parse cache across RouteGroups, producing a measured 21% load time reduction, 12% lower memory, and 26% fewer allocations on a 200-RouteGroup benchmark.

◆ Where it's heading

Skipper is building out its security posture at the proxy layer: RFC 9421 request signing, Redis L2 cache (v0.27.92), and security header handling improvements (v0.27.88) suggest a consistent push toward production-grade security primitives without architectural breaks. The performance improvements in v0.27.95 address real-world Kubernetes clusters where large RouteGroup counts are common.

◆ Prediction

RFC 9421 support will likely get expanded configuration options — signing key rotation, policy enforcement modes, per-route key selection — as Zalando's internal adopters surface operational requirements for the filter.

Alternatives to Pacemaker and Skipper

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 Pacemaker or Skipper.

See all Pacemaker alternatives → · See all Skipper alternatives →

Recent activity from Pacemaker and Skipper

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

  1. 4h agoSkipperv0.27.97
  2. 6h agoSkipperSkipper adds native RFC 9421 HTTP Message Signatures filter
  3. 23h agoSkipperCross-RouteGroup parse cache cuts load time 21%, memory 12%
  4. 1d agoSkipperv0.27.94
  5. 1d agoSkipperv0.27.93
  6. 7d agoSkipperSkipper adds Redis as L2 cache storage alongside existing Valkey
  7. 1mo agoPacemaker3.0.3: CVE-2026-10649 and remote message overflow fixes
  8. 2mo agoPacemaker3.0.2: PSK auth for remote CIB operations
  9. 2mo agoPacemaker3.0.1: TLS and X509 authentication for Pacemaker Remote
  10. 2mo agoPacemaker3.0.3-rc1: release candidate for the CVE fix set
  11. 2mo agoPacemaker2.1.11: CVE-2026-10649 backported to the maintenance branch
  12. 2mo agoPacemaker2.1.11-rc1: release candidate for the 2.1 CVE backport

Frequently asked questions

What is the difference between Pacemaker and Skipper?

They serve adjacent needs but don't currently overlap on shipped themes. Pacemaker and Skipper are shipping at a similar cadence (velocity 6.3 vs 6.3, 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.

Is Pacemaker better than Skipper?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Pacemaker and Skipper are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.

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.

What are the best alternatives to Skipper?

Top Skipper alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Skipper alternatives" section above for the current picks, or visit /alternatives/skipper for the full list with editorial commentary on each.