← Back to home
Comparison · Infra & APIs

Gloo Gateway vs Contour

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

Shared themes:envoy

Gloo Gateway vs Contour: at a glance

FeatureGloo GatewayContour
SectorInfra & APIsInfra & APIs
Velocity score5.00.0
Sparks · 30d00
Top themesapi-gateway, kubernetes-gateway-api, multi-branch-backports, envoykubernetes-ingress, envoy, multi-branch-releases, cve-response
Last editorial update3h ago3h ago
WebsiteVisit →Visit →

What is Gloo Gateway?

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.

Read the full Gloo Gateway trajectory →

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.

Read the full Contour trajectory →

Gloo Gateway vs Contour: editorial side-by-side

G
Gloo Gateway
INFRA · APIS
5.0

One status-churn fix, shipped to four maintenance branches inside forty minutes.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

C
Contour
INFRA · APIS
0.0

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 Gloo Gateway 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 Gloo Gateway or Contour.

See all Gloo Gateway alternatives → · See all Contour alternatives →

Recent activity from Gloo Gateway and Contour

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

  1. 2d agoGloo GatewayGloo 1.20.22 stops no-op Kubernetes Gateway report churn
  2. 2d agoGloo GatewayGloo 1.21.13 adds hostRewriteLiteral, reverts admission validation
  3. 2d agoGloo GatewayGloo 1.18.41 backports the Gateway report-churn fix
  4. 2d agoGloo GatewayGloo 1.19.20 backports the Gateway report-churn fix
  5. 5d agoGloo GatewayGloo 1.22.0-beta12 adds hostRewriteLiteral to shadowing
  6. 7d agoGloo GatewayGloo 1.22.0-beta11 isolates delegated RouteOptions before merging
  7. 4mo agoContourContour 1.33.3 bumps Envoy to 1.35.9 for security fixes
  8. 4mo agoContourContour 1.32.4 bumps Envoy to 1.34.13 for security fixes
  9. 4mo agoContourContour 1.31.5 bumps Envoy to 1.34.13 for security fixes
  10. 5mo agoContourContour 1.33.2 fixes HTTPProxy status updates and shutdown throttling
  11. 5mo agoContourContour 1.32.3 fixes the HTTPProxy status schema
  12. 5mo agoContourContour 1.31.4 fixes the HTTPProxy status schema

Frequently asked questions

What is the difference between Gloo Gateway and Contour?

Both compete on the same themes — envoy — 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.

Is Gloo Gateway better than Contour?

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.

What are the best alternatives to Gloo Gateway?

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.

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.