kOps
kOps is tightening cluster defaults and dropping the platforms it no longer wants to carry.
Comparison · Infra & APIs
Apache ShenYu vs Pacemaker
A side-by-side editorial comparison of Apache ShenYu and Pacemaker — release velocity, themes, recent moves, and the top alternatives to consider.
Apache ShenYu vs Pacemaker: at a glance
What is Apache ShenYu?
An API gateway that has quietly grown an LLM plugin family — and then stopped shipping.
Apache ShenYu's tracked releases run through the 2.7.0.x patch line and stop in November 2025. The consistent thread across those releases is a set of AI plugins accumulating alongside the traditional gateway ones: an AI proxy, an AI token limiter, an AI request transformer, and an MCP server plugin that shows up in the most recent entry through timeout and request-size fixes. The rest of each release is bug fixing and test coverage, with configuration synchronization through Nacos accounting for a recurring share of the defects.
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.
Apache ShenYu vs Pacemaker: editorial side-by-side
Apache ShenYu
0.0INFRA · APIS
An API gateway that has quietly grown an LLM plugin family — and then stopped shipping.
◆ Current state
Apache ShenYu's tracked releases run through the 2.7.0.x patch line and stop in November 2025. The consistent thread across those releases is a set of AI plugins accumulating alongside the traditional gateway ones: an AI proxy, an AI token limiter, an AI request transformer, and an MCP server plugin that shows up in the most recent entry through timeout and request-size fixes. The rest of each release is bug fixing and test coverage, with configuration synchronization through Nacos accounting for a recurring share of the defects.
◆ Where it's heading
ShenYu is positioning as a gateway for model traffic as well as service traffic, and the pattern is telling — the AI plugins appear first as features and then, one release later, as bug reports, which is what real usage looks like. Rate limiting by token rather than by request is the specific piece that matters, since it is the unit LLM providers actually bill on. Against that, the release notes are undifferentiated pull-request lists and nothing has shipped in the tracked feed for over eight months.
◆ Prediction
Expect further hardening of the MCP server plugin, which is the newest and least settled of the AI additions. The gap since 2.7.0.3 should be checked against the project's actual activity before drawing conclusions from it.
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.
Alternatives to Apache ShenYu 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 Apache ShenYu or Pacemaker.
Headlamp
Headlamp's feed is mostly chart bumps; the plugin toolchain is where the actual work shows.
Kubeshark
Kubeshark rebuilt its backend for V2 and is redrawing the free tier around it.
Certbot
Certbot is rebuilding its API around identifiers so certificates aren't only for domain names.
electerm
electerm now ships its own free AI backend, turning a terminal client into an assistant surface.
Apptainer
Apptainer 1.5 adds CDI device support and builds SIF images straight from Dockerfiles.
See all Apache ShenYu alternatives → · See all Pacemaker alternatives →
Recent activity from Apache ShenYu and Pacemaker
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 12d agoPacemaker3.0.3: CVE-2026-10649 and remote message overflow fixes
- 29d agoPacemaker3.0.2: PSK auth for remote CIB operations
- 29d agoPacemaker3.0.1: TLS and X509 authentication for Pacemaker Remote ⚡
- 29d 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
- 8mo agoApache ShenYuMCP server plugin fixes and Nacos sync cache corrections
- 11mo agoApache ShenYuAI request transformer plugin joins the proxy and token limiter
- 1y agoApache ShenYuJWT SPI extension and Dubbo method configuration land
Frequently asked questions
What is the difference between Apache ShenYu and Pacemaker?
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 Apache ShenYu 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 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 Apache ShenYu?
Top Apache ShenYu alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Apache ShenYu alternatives" section above for the current picks, or visit /alternatives/shenyu 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.