Ross ROSS = Recommend OSS · open-source software intelligence for agents

kgateway-dev/kgateway

The Cloud-Native API Gateway and AI Gateway observed · 2026-08-28

github.com/kgateway-dev/kgateway · homepage · Go · Apache-2.0 (permissive) observed · 2026-08-28

Health v2 · maintenance only

95/100

  • Activity 99
  • Release rhythm 86
  • Longevity 100
How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.

  • gap_med: 3
  • age_days: 3145
  • days_rel: 13
  • days_push: 7
  • n_releases_24m: 72

Full methodology

Adoption not part of the score

5670 stars · 800 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded

kgateway is a Kubernetes-native API gateway and ingress controller that implements the Kubernetes Gateway API as a control plane for Envoy Proxy. It centralizes traffic routing, authentication, authorization, and rate limiting for microservices, serverless, and legacy backends, scaling from lightweight microgateways to gateways handling billions of API calls.

Use cases

  • expose kubernetes services to the internet with an ingress controller
  • manage api authentication and rate limiting in one gateway
  • migrate from ingress nginx to the gateway api
  • route traffic to microservices, serverless functions, and legacy apps
  • run a gateway api-native envoy control plane in kubernetes
  • apply retries, timeouts, and circuit breaking to api traffic
  • secure and govern llm and ai agent traffic at the gateway

When to choose

  • you run workloads on Kubernetes and want a standards-based Gateway API controller
  • you need a battle-tested Envoy-based gateway for high-scale API traffic
  • you are migrating off Ingress NGINX and want automated conversion tooling
  • you need hybrid routing across microservices, serverless, and legacy apps
  • you want centralized auth, rate limiting, and traffic policies at the edge

When to avoid

  • you need a simple non-Kubernetes reverse proxy for a single app
  • your stack is VM-based with no container orchestration
  • you want a lightweight edge proxy without a Kubernetes control plane
  • you need deep AI/agent/MCP-specific gateway features, which live in the separate agentgateway project

Facets

service · maturity stable

api-gateway routing middleware auth authorization rate-limiting http-server proxy websocket rpc apis microservices cloud-computing networking security backend large-language-models cloud self-hosted go windows envoy-proxy gateway-api kubernetes-ingress traffic-management ingress-controller ai-gateway grpc service-mesh helm ingress-nginx-migration containers devops kubernetes docker linux macos

7 sources

Member repositories

RepositoryRoleHealth v2
kgateway-dev/kgatewaymain95

For agents

markdown · JSON · MCP: product_card(name="kgateway-dev/kgateway")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem