Skip to content
SPECIFICTION
Get listed

Contour vs NGINX Gateway Fabric

Contour

projectcontour.io

NGINX Gateway Fabric

docs.nginx.com

Side by side

FigureContourNGINX Gateway Fabric
Price fromFreeFree
Free planYesYes
Free trial——
Open source——
Linux—Yes
Self-hostedYesYes
Plans published11
Spec score · Kubernetes Ingress Controllers7.7 (#12)7.4 (#16)
DeploymentContour can be deployed as a Kubernetes deployment or daemonset.NGINX Gateway Fabric can be installed with Helm from an OCI registry or from source, and Gateway API resources must be installed before deployment.
IntegrationsContour documentation includes guides for cert-manager, Gatekeeper, AWS Network Load Balancer, and Prometheus metrics.The documentation describes monitoring with Prometheus and Grafana and tracing with OpenTelemetry collectors, including Jaeger examples.
PurposeContour is an open source Kubernetes ingress controller that provides the control plane for the Envoy edge and service proxy.NGINX Gateway Fabric implements the Kubernetes Gateway API using NGINX as the data plane for load balancing, reverse proxying, and API gateway use cases.
Security featuresThe documentation lists TLS termination and delegation, client authorization, rate limiting, JWT verification, and IP filtering features.The documentation covers HTTPS with cert-manager, mutual TLS, basic authentication, OpenID Connect, external authentication, and JWT authentication.
SupportThe project provides community support through its GitHub project page and invites users to file issues or ask questions there.The support page directs users to GitHub issues and the NGINX Community Forum, and says users can contact F5 Sales for dedicated support or NGINX Plus features.

Plans

Contour

  • ContourFree

Contour pricing →

NGINX Gateway Fabric

  • NGINX Gateway Fabric (NGINX Open Source data plane)Free

NGINX Gateway Fabric pricing →

In their own words

Contour

Contour is a free, self-hosted, open-source Kubernetes ingress controller that provides the control plane for the Envoy edge and service proxy. It supports Kubernetes Ingress v1, its HTTPProxy custom resource and Gateway API. Contour updates ingress configuration dynamically with minimal dropped connections and supports multiple configuration types in clusters used by multiple teams. It can run as a Kubernetes deployment or daemonset, and administrators can delegate access to wildcard certificates. Documented security features include TLS termination, client authorization, rate limiting, JWT verification and IP filtering. Contour and Envoy expose metrics that Prometheus can scrape, and documentation includes guides for cert-manager, Gatekeeper and AWS Network Load Balancer. The project is tested with Kubernetes 1.21 and later and is intended for both cluster administrators and application developers. Community support is available through the project's GitHub page, where users can report issues or ask questions. Contour is a Cloud Native Computing Foundation incubating project; its documentation includes a threat model, a security reporting process and a security fix checklist.

Visit projectcontour.io

NGINX Gateway Fabric

NGINX Gateway Fabric is a self-hosted Kubernetes implementation of the Gateway API, using NGINX as its data plane for load balancing, reverse proxying, and API gateway use cases. Its control plane translates Gateway API resources into NGINX configuration. Supported resource coverage includes GatewayClass, Gateway, HTTPRoute, GRPCRoute, ReferenceGrant, TLSRoute, TCPRoute, UDPRoute, and BackendTLSPolicy, though the support level varies by resource. Traffic features include HTTP and TLS routing, redirects, rewrites, request mirroring, session persistence, and rate limiting. Security documentation covers HTTPS with cert-manager, mutual TLS, basic authentication, OpenID Connect, external authentication, and JWT authentication. Monitoring examples use Prometheus and Grafana; tracing uses OpenTelemetry collectors, including Jaeger examples. The free NGINX Open Source data-plane plan costs nothing. Installation is available through Helm from an OCI registry or from source, with Gateway API resources installed beforehand. Version 2.7.2 requires Kubernetes 1.32 or later; documented images are available for amd64 and arm64. Support is directed to GitHub issues and the NGINX Community Forum.

Visit docs.nginx.com