An open-source, next-generation Web Application Firewall (WAF) that integrates as a reverse proxy to make web services secure by default.
BunkerWeb is an open-source, next-generation Web Application Firewall (WAF) and web server based on NGINX. It protects web services by acting as a reverse proxy, integrating seamlessly into existing environments like Docker, Kubernetes, and Linux. It aims to simplify cybersecurity by providing robust, configurable security features out of the box, adhering to a 'security by default' philosophy.
System administrators, DevOps engineers, and security professionals who need to secure web applications in containerized, cloud, or traditional server environments. It is particularly suited for teams managing multiple web services across diverse deployment platforms.
Developers choose BunkerWeb for its seamless integration into existing infrastructures without requiring major architectural changes, its comprehensive 'security by default' feature set including ModSecurity WAF and Let's Encrypt automation, and its flexibility through a plugin system and optional web UI for management without CLI dependency.
🛡️ Open-source and cloud-native Web Application Firewall (WAF)
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Officially supports deployment across Linux, Docker, Kubernetes, Swarm, and Azure via documented integrations, allowing protection of diverse environments without architectural overhauls.
Includes ModSecurity WAF with OWASP Core Rule Set, automatic Let's Encrypt HTTPS, and bot challenges out of the box, ensuring immediate protection with minimal setup.
Offers official plugins for antivirus scanning (ClamAV), alternative WAF engines (Coraza), and notifications (Discord/Slack), enabling tailored security enhancements beyond core features.
Provides an optional graphical interface to manage settings, view logs, and monitor attacks, reducing CLI dependency for teams preferring visual configuration tools.
Requires managing a scheduler service and backend database (SQLite, MariaDB, etc.) for configuration state, adding operational complexity compared to simpler, standalone WAFs.
Enhanced security and monitoring capabilities are gated behind the PRO version, as noted by crown icons in docs, pushing users toward paid upgrades for advanced needs.
In multisite mode, settings must be prefixed with server names (e.g., www.example.com_USE_ANTIBOT), making configuration cumbersome for environments with many services.