NGINX Gateway Fabric review
A focused, self-hosted Kubernetes gateway for teams that want open-source NGINX routing.
Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026
NGINX Gateway Fabric is an open-source Kubernetes gateway implementation from F5, Inc. It uses NGINX as the data plane and implements Gateway API resources for routing HTTP, HTTPS, HTTP/2, gRPC, TCP, TLS, and UDP traffic. Teams can use it as a load balancer, reverse proxy, or API gateway for Kubernetes applications. Its fit is strongest for organizations that want a focused Gateway API implementation while keeping deployment self-hosted and centered on Kubernetes.
The feature set covers core traffic management needs without limiting the gateway to HTTP. It supports configurable local rate limiting, Basic authentication, JWT, OpenID Connect, external authentication, HTTP redirects, rewrites, request or response header modification, and request mirroring. Mutual TLS is available for frontend and backend traffic, while HTTP/2 upstream connections support applications that need that protocol. These capabilities make it suitable for Kubernetes teams handling mixed service traffic and requiring authentication or request processing at the gateway.
Its architecture separates control-plane and data-plane deployments, with the project dynamically provisioning NGINX deployments for Gateway resources. That separation can suit teams already operating Kubernetes control components, but it also places deployment and ongoing administration responsibilities on them. NGINX Gateway Fabric is free and open source, making it a practical choice for teams prioritizing an open implementation and direct control of their environment. Organizations seeking broader integrations or wider management features should choose a product with a broader operational scope instead.
NGINX Gateway Fabric pros and cons
- Where it wins
- Routes HTTP, gRPC, TCP, TLS, and UDP traffic
- Adds authentication, rate limiting, rewrites, and request mirroring
- Open source with a free plan and self-hosted deployment
- Where it doesn't
- Requires the Kubernetes team to manage self-hosted deployment
- Uses a separate control plane and NGINX data plane
- Broader integrations and management features are outside its scope
NGINX Gateway Fabric fact sheet, pricing and score →
Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.
Last updated · How we research and update