A Modern Alternative to Apigee
Kgateway is an open source, Kubernetes-native alternative to the Apigee API gateway, built on Envoy and the Kubernetes Gateway API instead of a Google Cloud-centric management platform. Compare it with Apigee before you choose.
Capability comparison
Kgateway leads in 7 of 7 categories
Why Teams Choose Us
“Apigee ties our API gateway to Google Cloud, and we need something that runs anywhere.”
Kgateway runs on any Kubernetes cluster, in any cloud or on-prem, so your API gateway isn’t tied to a single cloud provider’s platform.
“Apigee’s full API management suite is more than we need, and the licensing reflects it.”
Kgateway is open source and CNCF-hosted at its core, with enterprise support and policy on top only where you need it, instead of paying for a full API management suite up front.
“We want an API gateway architecture built for Kubernetes, not adapted to it.”
Kgateway is built from the ground up on Envoy and the Kubernetes Gateway API standard, so Kubernetes-native routing and policy aren’t an afterthought.
Customer proof
"Solo.io helps Grainger keep the world working by powering innovation at scale."
4,000+ releases/year
Trust & compliance
SOC 2
Certification supports security and procurement review for regulated Kubernetes environments
OSS roots
Build on Envoy, Istio, Cilium, and Gateway API foundations for open source service mesh adoption.
CNCF maintainer status
keeps Solo.io engineers close to the projects shaping cloud native mesh standards.
FIPS builds
provide FIPS 140-2 validated options for service mesh security requirements.
Published SLAs
Define support expectations for enterprise service mesh operations.
Customer references
include production outcomes from teams running large-scale Kubernetes networking.
Frequently Asked Questions
How is kgateway different from the Apigee API gateway?
How is kgateway different from the Apigee API gateway?
Apigee is a full API management platform built around Google Cloud, with its own proxy model and licensing. Kgateway is built from the ground up on Envoy and the Kubernetes Gateway API standard, open source at its core, and runs on any Kubernetes cluster in any cloud or on-prem.
Can I run kgateway on-premise, like Apigee's on-premise option?
Can I run kgateway on-premise, like Apigee's on-premise option?
Yes. Kgateway runs anywhere Kubernetes runs, on-premise, in any cloud, or across a hybrid environment, without a separate on-premise product tier or licensing model.
Is there an open source alternative to Apigee?
Is there an open source alternative to Apigee?
Yes. Kgateway is open source and CNCF-hosted, free to run on your own, with enterprise support and advanced policy available on top when you need production SLAs.
How does kgateway's architecture compare to Apigee's?
How does kgateway's architecture compare to Apigee's?
Kgateway is Kubernetes-native by design, built on Envoy and the Kubernetes Gateway API rather than adapting a cloud API management platform to Kubernetes workloads. See the full category-by-category comparison above.
We're already using Apigee for API documentation and lifecycle management. Can kgateway replace it?
We're already using Apigee for API documentation and lifecycle management. Can kgateway replace it?
Kgateway focuses on the gateway layer itself, routing, security, and traffic policy, rather than the full API lifecycle and documentation tooling Apigee bundles. Many teams run kgateway as their Kubernetes-native gateway while keeping lighter-weight tooling for documentation.
See How Kgateway Compares to Apigee
Request a demo to see kgateway scoped to your environment, or compare it with Apigee and other API gateway companies in the Buyer's Guide first.
