kOps
kOps is tightening cluster defaults and dropping the platforms it no longer wants to carry.
A side-by-side editorial comparison of Apache ShenYu and Gloo Gateway — release velocity, themes, recent moves, and the top alternatives to consider.
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.
One status-churn fix, shipped to four maintenance branches inside forty minutes.
Gloo maintains four release lines at once — 1.18, 1.19, 1.20 and 1.21 — plus a 1.22 beta series, and fixes are fanned across all of them together. On 5 August, v1.18.41, v1.19.20, v1.20.22 and v1.21.13 were cut within forty-five minutes of each other carrying the same Kubernetes Gateway report-churn fix and the same Go, gRPC and kubectl dependency bumps.
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.
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.
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.
Gloo maintains four release lines at once — 1.18, 1.19, 1.20 and 1.21 — plus a 1.22 beta series, and fixes are fanned across all of them together. On 5 August, v1.18.41, v1.19.20, v1.20.22 and v1.21.13 were cut within forty-five minutes of each other carrying the same Kubernetes Gateway report-churn fix and the same Go, gRPC and kubectl dependency bumps.
The recurring theme is translation correctness under Kubernetes Gateway API — specifically, bugs where the translator's internal state does not behave the way its callers assume. The report-churn fix found equality checks comparing maps of pointer values, so identical output registered as changed on every recompute. The delegateOptions fix in beta11 found RouteOptions assigned by reference from the snapshot, so merging parent Virtual Service options mutated shared protos and contaminated every other route for the rest of the cycle. Both ship with the same instinct for caution: the second one is gated behind GLOO_ISOLATE_DELEGATE_ROUTE_OPTIONS so operators can revert.
The 1.22 beta line will keep collecting Gateway API translation fixes ahead of a stable release, and each one that matters will be backported across all four maintenance branches on the same day, as this window shows twice.
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 Gloo Gateway.
kOps is tightening cluster defaults and dropping the platforms it no longer wants to carry.
Headlamp's feed is mostly chart bumps; the plugin toolchain is where the actual work shows.
Kubeshark rebuilt its backend for V2 and is redrawing the free tier around it.
Certbot is rebuilding its API around identifiers so certificates aren't only for domain names.
electerm now ships its own free AI backend, turning a terminal client into an assistant surface.
Apptainer 1.5 adds CDI device support and builds SIF images straight from Dockerfiles.
See all Apache ShenYu alternatives → · See all Gloo Gateway alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — api-gateway — within Infra & APIs. Gloo Gateway is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Gloo Gateway is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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.
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.
Top Gloo Gateway alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Gloo Gateway alternatives" section above for the current picks, or visit /alternatives/gloo for the full list with editorial commentary on each.