What would be the main difference between kgateway and Envoy Gateway?

[romelBen]

I am looking to begin my deep-dive in K8s Gateway API. I have used Cilium and Istio. Istio is a beast but once setup it is amazing. Cilium is also good as well but did not fit my needs. This is where kgateway and Envoy Gateway caught my attention.

Both of these tools look great but I have several questions on these 2:

1. Since kgateway is supported by gloo.io, will there be features behind a paywall? This is one of the main reasons when I talk to companies that they want a fully OSS tool to use. This is where Envoy Gateway comes into focus.
2. Is kgateway tailored more towards AI than Envoy Gateway? Or does kgateway just have more features and what are they?
3. I heavily leaning towards Envoy Gateway but I can be swayed on using kgateway instead. If I am to begin mentioning to clients the use of kgateway, will it be ready for production use where availability and performance would trump Envoy Gateway.
4. And just simply, what really is the differences in features between kgateway and Envoy Gateway?
5. Is kgateway cloud-agnostic for use in Azure, GCP, and AWS?