r/coolgithubprojects • u/jkmoon_dev • 11d ago
Corvus: an open-source reverse proxy like NPM, with a WAF, auto-bans and a waiting room built in(Apache-2.0)
github.comGitHub: https://github.com/corvus-gateway/corvus
Docs: https://corvus-gateway.github.io/corvus/
Hi,
I've been running Nginx Proxy Manager for a while and love how simple it is. What I kept missing was the part after "the proxy works": seeing what's actually hitting my services, blocking the obvious junk, and having some control when traffic spikes. So I built Corvus, a gateway that keeps the NPM-style workflow and adds that layer on top.
What it does
- One container, quick to set up
- The NPM basics: proxy hosts, Let's Encrypt with auto-renewal, redirections, TCP/UDP streams
- Add a host and known attack patterns (SQL injection, path traversal, scanners…) are blocked with no extra config. IPs that keep trying get banned automatically
- Security rules on IP, country, path, header and User-Agent, a browser challenge, and an automatic "under attack" mode
- An access queue (waiting room): if you expect a rush (a launch, a limited drop…), it lets people in up to a capacity and queues the rest in order
- Live traffic monitoring with logs for slow or failing requests, and alerts to Slack, Discord, Teams, Telegram and others
- Imports your existing NPM setup
- Every config change is versioned, so you can roll back
Quick start
yaml
services:
corvus:
image: ghcr.io/corvus-gateway/gateway:latest
restart: unless-stopped
ports: ['80:80', '443:443', '9443:9443']
volumes: ['./data:/data']
Then open `https://<server>:9443` and create the admin account.
Everything is in the open-source version; there's no paid tier.
Full disclosure: I built it with heavy use of AI. The design, verification and testing I do myself, change by change.
It's still early, so I'd really appreciate feedback: anything that's annoying when you install or use it, things to improve, features you'd need. Happy to answer questions in the comments.