Gloo API Gateway Version 1.3 – Dev Portal, WebAssembly, Knative (opens in new tab)

I'd say a lot of our users are from big enterprises, especially financial services where security is paramount. Gloo has a decoupled control plane so it can be scaled and secured independently from the proxy/data plane. For example, Gloo requires zero privilege capabilities/service accounts, has a read-only file system, and the data plane has no access to the Kubernetes API when run in Kubernetes (not a requirement -- gloo can be run outside k8s as well). Additional security related functionality like WAF, OPA authz, and data loss prevention filters are crucial for our users.

see more here: https://docs.solo.io/gloo/latest/introduction/others/

HTH

https://docs.solo.io/gloo/latest/guides/integrations/knative...

RE AWS API Gateway... Gloo is more full featured and self hosted. Even wrt performance, in fact, we've seen anecdotal evidence of Gloo performing better than AWS API Gateway for things like calling Lambdas.

Disclaimer: I work for Solo.io

An API Gateway can do sophisticated edge security challenges (OIDC, Authz based on OPA, web app firewalling/WAF, etc) as well as things like message transformation, swagger/grpc detection, exposing APIs for self-service signup through a portal, etc. Gloo does all these things.

I've written in depth about this as well, specifically in terms of things like contour, Istio ingress gateway, consul's service mesh gateway, etc, etc

https://blog.christianposta.com/microservices/do-i-need-an-a...

Gloo resources: https://docs.solo.io/gloo/latest/guides/dev_portal/ https://docs.solo.io/gloo/latest/guides/security/waf/ https://docs.solo.io/gloo/latest/guides/security/auth/oauth/... https://docs.solo.io/gloo/latest/guides/security/opa/ https://docs.solo.io/gloo/latest/installation/advanced_confi... https://docs.solo.io/gloo/latest/guides/traffic_management/r...

Gloo has lots of other features, like WAF and Webassembly hooks for request flow.