SWAG (Secure Web Application Gateway)

Nginx webserver and reverse proxy with PHP support, built-in Certbot (Let's Encrypt) client and fail2ban integration.

Steady · 65
65/100
Steady

Maintained, but at a slower pace than the leaders in its category.

Maintenance 13/40
Releases 25/25
Community 12/20
Momentum 15/15

Commit activity more than 33% of tracked projects; popularity more than 61%. How this is calculated.

Commits, last 11 months

2025-12: 10 commits 2026-01: 17 commits 2026-02: 9 commits 2026-03: 7 commits 2026-04: 6 commits 2026-05: 9 commits 2026-06: 12 commits 2026-07: 19 commits 2026-08: 11 commits 2026-09: 17 commits 2026-10: 23 commits
2025-12 140 total 2026-10
Stars3.8k
Latest release5.10.0-ls501 · 18 Nov 2026
Repo updated18 Nov 2026
LicenceGPL-3.0
Built withDocker

Is SWAG (Secure Web Application Gateway) actively maintained?

SWAG (Secure Web Application Gateway) is under active development: 140 commits landed over the last 11 months, averaging roughly 17 commits a month in the most recent quarter.

The most recent tagged release, 5.10.0-ls501, shipped within the last month — a current, installable version exists today.

SWAG (Secure Web Application Gateway) ranks #11 of 19 in Web Servers, placing it mid-table for maintenance activity.

What SWAG (Secure Web Application Gateway) actually does

SWAG functions as an Nginx-based web server and reverse proxy, packaging PHP execution, automated Let's Encrypt certificate generation via Certbot, and fail2ban protection into a single containerised application. It is designed to route incoming web traffic while handling encryption and basic intrusion prevention out of the box. The project operates under the GPL-3.0 licence and maintains an active release cycle.

Best fit: It suits self-hosters who want a pre-configured Nginx proxy stack with automated TLS certificate management without manually wiring Certbot and fail2ban together.

Worth knowing: Configuration relies heavily on text-based Nginx files and container environment variables, which can introduce friction for administrators preferring a graphical management interface.

Deployment notes

You will typically need to mount persistent volumes for your configuration files, log outputs, and web root directories, while ensuring ports 80 and 43 for HTTP challenges and traffic are correctly forwarded.


Alternatives to SWAG (Secure Web Application Gateway)

Projects in the same categories, ordered by health score.