Gloo Edge, now presented by Solo.io as Gloo Gateway, is a Kubernetes-native ingress controller and API gateway built on the Envoy proxy. It handles request routing, rate limiting, circuit breaking, retries, caching, transformation and external authentication and authorisation, and can route to REST and OpenAPI services, SOAP, gRPC, serverless functions and message queues such as NATS and AMQP. It is self-managed software that platform teams run in their own Kubernetes clusters. The open-source project is also the origin of kgateway, a CNCF sandbox project, and Solo.io offers a commercial enterprise edition with support.
Solo.io is headquartered in Cambridge, Massachusetts, in the United States, so the vendor falls under US jurisdiction, including the CLOUD Act. Because the gateway runs in your own clusters, traffic and data stay where you deploy it, which can be in the EU. The Gloo OSS repository states that Gloo OSS reaches end of life on 31 December 2026, with no further releases or security patches afterwards, and recommends migrating to kgateway. Organisations should factor this timeline into their planning.