Kgateway

What it is

Kgateway is an Envoy-based API gateway built specifically around the Kubernetes Gateway API spec. It's a control plane that configures Envoy proxies declaratively via Kubernetes CRDs (Gateway, HTTPRoute, TCPRoute, etc.) rather than relying on a proprietary configuration model. It's meant to handle north-south traffic (ingress, egress, API management) across cloud, hybrid, and on-prem clusters, with the Gateway API as the portable, vendor-neutral interface on top.

If you've used Envoy Gateway, Istio's gateway implementation, or Contour, this occupies the same slot: Kubernetes-native L7 traffic management, but with Gateway API as a first-class citizen rather than a bolt-on.

Who builds it and why

Kgateway (formerly Gloo Edge, from solo.io) was contributed to CNCF and is now a sandbox project. Solo.io remains the primary commercial backer and majority contributor, which is the typical pattern for CNCF sandbox projects with a corporate origin — the company monetizes an enterprise version and support, and open-sources the core. 271 contributors is a healthy number for a sandbox-stage project and suggests broader adoption beyond a single vendor's payroll, but you should assume solo.io drives roadmap and release cadence.

Founding date is not publicly available in the data provided, but the project has prior history under the Gloo Edge name before rebranding and CNCF contribution.

Production readiness signal

• CNCF stage: Sandbox — the earliest CNCF maturity level. This means CNCF has done minimal vetting; it does not mean the software is immature, but it does mean you should treat CNCF status as a low signal here and do your own diligence.
• Release cadence: v2.3.5 latest — a patch-level release number suggests active maintenance and a stable v2.x line rather than pre-1.0 churn.
• Community activity: 5,589 GitHub stars and recent commits (as of your check) indicate the project is alive and maintained, not abandoned.
• Contributor count: 271 is solid, but check the actual commit distribution — many CNCF sandbox projects show 80%+ of commits from one company. Verify this yourself before assuming broad community governance.

Bottom line: technically mature enough to run in production (Gloo Edge's lineage predates the Kgateway rebrand), but CNCF maturity label alone tells you it hasn't gone through incubation-level governance and adoption review.

Who should use this

• Teams already standardizing on Kubernetes Gateway API who want a conformant implementation instead of provider-specific ingress annotations.
• Platform teams running multi-cloud or hybrid clusters who need one gateway config model across environments.
• Organizations wanting Envoy's data plane maturity without hand-rolling Envoy xDS config themselves.
• Teams that want a migration path from Gloo Edge and already trust solo.io's engineering.

Who should NOT use this

• Teams wanting CNCF-graduated maturity guarantees for compliance or procurement reasons — use Istio or Envoy Gateway (also sandbox, but check current status) or a graduated project instead.
• Small teams with basic ingress needs — plain NGINX Ingress Controller or Traefik is far less operational overhead if you don't need advanced traffic policy.
• Teams already deep in Istio service mesh — running a separate gateway control plane alongside Istio's own Gateway API implementation adds redundant complexity; use Istio's gateway instead.
• Shops averse to vendor-driven open source — if solo.io's commercial priorities conflict with your roadmap needs, or you need multi-vendor governance guarantees, look elsewhere.

Alternatives

• Envoy Gateway — CNCF project, also Gateway API-native, backed by a broader vendor consortium (Tetrate, VMware, Red Hat) rather than a single company.
• Istio Gateway — if you already run Istio mesh, use its built-in Gateway API support instead of adding a separate control plane.
• Contour — mature, CNCF (graduated), Envoy-based ingress controller with longer production track record, though less focused on Gateway API purity.

Pricing

Kgateway itself is fully open source under Apache-2.0 — no license fees, no feature gating in the core project. Solo.io sells a commercial enterprise distribution (Gloo Platform/Gloo Gateway) with added support, enterprise auth integrations, and SLAs on top of the open-source core. Expect the usual open-core dynamic: core functionality free, enterprise support and advanced features paid.