Jackett
A daily indexer-repair treadmill: Jackett patches tracker definitions as fast as trackers change.
Comparison · Infra & APIs
Pacemaker vs Contour
A side-by-side editorial comparison of Pacemaker and Contour — release velocity, themes, recent moves, and the top alternatives to consider.
Pacemaker vs Contour: at a glance
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.
What is Contour?
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.
Pacemaker vs Contour: editorial side-by-side
Pacemaker
6.3INFRA · APIS
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.
Contour
0.0INFRA · APIS
Three supported branches, patched in lockstep within the same minute.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to Pacemaker and Contour
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 Contour.
Pressable
Ten days of bulk operations, then the AI assistant got the keys to multi-site access control.
Dependency-Track
A v5 release candidate train carrying a database migrator that has to work on the first try.
rsyslog
The syslog daemon is quietly becoming an OpenTelemetry-era pipeline, YAML config and all.
HAProxy Kubernetes Ingress Controller
The changelog is a raw commit log, and its severity tags tell you more than the prose would.
Inspektor Gadget
The eBPF observability tool just started reaching for the GPU.
See all Pacemaker alternatives → · See all Contour alternatives →
Recent activity from Pacemaker and Contour
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 11d agoPacemaker3.0.3: CVE-2026-10649 and remote message overflow fixes
- 28d agoPacemaker3.0.2: PSK auth for remote CIB operations
- 28d agoPacemaker3.0.1: TLS and X509 authentication for Pacemaker Remote ⚡
- 28d agoPacemaker3.0.3-rc1: release candidate for the CVE fix set
- 1mo agoPacemaker2.1.11: CVE-2026-10649 backported to the maintenance branch
- 1mo agoPacemaker2.1.11-rc1: release candidate for the 2.1 CVE backport
- 4mo agoContourContour 1.33.3 bumps Envoy to 1.35.9 for security fixes
- 4mo agoContourContour 1.32.4 bumps Envoy to 1.34.13 for security fixes
- 4mo agoContourContour 1.31.5 bumps Envoy to 1.34.13 for security fixes
- 5mo agoContourContour 1.33.2 fixes HTTPProxy status updates and shutdown throttling
- 5mo agoContourContour 1.32.3 fixes the HTTPProxy status schema
- 5mo agoContourContour 1.31.4 fixes the HTTPProxy status schema
Frequently asked questions
What is the difference between Pacemaker and Contour?
They serve adjacent needs but don't currently overlap on shipped themes. Pacemaker is currently shipping more aggressively (velocity 6.3 vs 0.0), 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 Pacemaker better than Contour?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Pacemaker is currently shipping more aggressively (velocity 6.3 vs 0.0), 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 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 Contour?
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.