NGINX Gateway Fabric
NGINX Gateway Fabric is an open-source controller that implements the Kubernetes Gateway API using NGINX as the data plane, giving cluster operators a…
Platform availability
Available on 1 of 10 platforms
- Unraid (not listed)
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
73/100 Good
- Maintained
- 100last commit 15 days ago
- Popular
- 621,191 GitHub stars
- Easy to install
- 251 install platform, install notes
- Light to run
- No data
- Security check
- 81no serious findings, 3 minor, CI, tests, OpenSSF Scorecard 7.9/10
Based on 4 of 5 factors.
Availability: platform listings confirmed today
- GitHub stars
- 1,191
- Open issues
- 88
- Last commit
- 2026-11-06
- Latest release
- v2.8.1
- License
- Apache-2.0
- Activity
- steady
Checked 14 days ago - source: GitHub (nginx/nginx-gateway-fabric)
Resources & Compatibility
Requirements not published yet.
First-install notes
- Put your Nginx template in a mounted folder Create a folder for your Nginx config templates, put a .conf.template file inside, and mount that folder to /etc/nginx/templates while setting any variables as environment values. If you skip this, Nginx starts with the default site and your domain or other variables will not be filled in. source
- Map the container's port 80 to a host port Run the container with a port mapping such as -p 8080:80, which connects your machine's port 8080 to Nginx's default port 80. If you forget this, browsers on your machine cannot reach the site. source
- Let Nginx tune workers to your CPU You can set NGINX_ENTRYPOINT_WORKER_PROCESSES_AUTOTUNE=true so Nginx chooses how many helper request-handling processes to start based on your CPU. This is optional, but it avoids manually guessing a worker count that could leave your machine too busy or too idle. source
Fetched 40 days ago - each note links to its source
Variants
Alternatives (10)
- Apache HTTP Server - Open-source HTTP server offering cross-platform support, modular architecture, secure configuration, robust content delivery, and extensive…
- BunkerWeb - BunkerWeb is a self-hosted, open-source web application firewall and NGINX-based web server that protects services with secure-by-default s…
- Caddy - Caddy is an extensible web server and reverse proxy that serves Transport Layer Security (TLS) by default, making it simple to secure and r…
- Corvus - Self-hosted reverse proxy and web application firewall with a web console; it provides domain forwarding, free SSL, live traffic monitoring…
- Haproxy - HAProxy is a TCP proxy and a HTTP reverse proxy.
- Microsoft IIS - Internet Information Services (IIS) for Windows® Server is a flexible, secure and easy-to-manage Web server for hosting anything on the Web.
- Træfik Proxy - The Cloud Native Application Proxy Simplify networking complexity while designing, deploying, and operating applications.
- Varnish - Varnish is an open-source HyperText Transfer Protocol (HTTP) accelerator for website operators that serves cached pages from memory in fron…
- lighttpd - Lighttpd is a secure, lightweight web server that uses memory and CPU more efficiently than comparable servers, with FastCGI, CGI, authenti…
- nginx-ui
Checked 52 days ago - source: AlternativeTo
Common questions
Which Gateway API resources is NGF intended to implement?
The project aims to implement Gateway, GatewayClass, HTTPRoute, GRPCRoute, TCPRoute, TLSRoute, and UDPRoute.
Do I need to run separate control-plane and data-plane components?
NGF separates control-plane and data-plane deployments while using NGINX as the data plane.
What areas should I check when troubleshooting NGF?
Common problem areas include the control plane, data plane, configuration errors, validation failures, and connectivity issues.
What information should I collect before asking for help?
The documentation says to collect important data points when investigating a problem or requesting help.
Answers sourced from community.nginx.org, deepwiki.com, docs.nginx.com, github.com
Community
- r/selfhosted on Reddit: Reverse proxy + wireguard tunnel from VPS to ... (reddit)
- About the NGINX Gateway Fabric category (other)
- Latest NGINX Gateway Fabric topics - NGINX Community Forum (other)
- Issue with k0s and nginx-fabric API Gateway : r/kubernetes - Reddit (reddit)
Collected 48 days ago - public community threads