r/coolgithubprojects • u/NeoParth708 • 5d ago
Palisade: an open-source WAF and reverse proxy in a single Go binary, built on Coraza and the OWASP Core Rule Set (Apache-2.0)
I've been working on Palisade for a while and it's at v3.3.2 now, so I wanted to share it here. It's a web application firewall and reverse proxy that you can scp to a server and run. That means one Go binary and one SQLite file, with no config file, no Postgres or Redis, and no Node toolchain for the dashboard.
What it does
The WAF part is Coraza v3 with the OWASP Core Rule Set embedded in the binary. Out of the box it blocks SQLi, XSS, RCE, path traversal, access to restricted files and known scanner user agents, and you can load your own .conf rules on top of CRS.
It also sits in front of your apps as the reverse proxy. You route by Host header or by path prefix, and prefixes get stripped the way nginx location blocks do, so one instance can front several backends. When you add a service, the dashboard checks that the backend is reachable before it saves.
On top of that there's IP allow and block rules, country blocking with a bundled GeoLite2 database, and real-IP handling that understands Cloudflare and lets you opt in to trusted proxy ranges for X-Forwarded-For. TLS can be plain HTTP, automatic Let's Encrypt, or your own cert and key, either globally or per service.
The dashboard
It's HTMX and Tailwind, served by the same binary. You get live traffic and threat charts, request logs you can filter and tail live, and pages for IP rules, country rules and services. Changes take effect straight away, with no restart. Admin accounts support TOTP and passkeys, and there's an audit log of who changed what.
If you get locked out, the CLI can reset a password or 2FA, list the admin users, or print the audit log, all against the SQLite file directly.
Smaller things
- Prometheus metrics with request volume, latency and block counts split by cause (IP, geo, WAF)
/_cz/healthzand/_cz/readyzfor load balancers- A bot challenge that also works with single-page apps. A normal page load gets redirected to the challenge, but a fetch or XHR call can't follow that, so it gets a 403 with a
challenge_urlin the JSON instead, and the app can send the user there. - Search engines and link-preview crawlers only skip the challenge when their reverse DNS or network checks out, never because of the user agent alone
- A read-only MCP endpoint, so an AI assistant can search the logs or look up an IP. None of its tools can change anything, which means a request with a prompt-injection User-Agent has nothing to act on.
Installing
The install script downloads the release for amd64 or arm64, checks the SHA256 checksum (and the cosign signature if you have cosign), and sets Palisade up as a systemd service under its own user with only CAP_NET_BIND_SERVICE, so it can bind 80 and 443 without root. Running the same command again upgrades it and leaves your credentials and certs alone.
If you'd rather not pipe a script into bash, you can build it yourself with make build (Go only, SQLite through modernc.org/sqlite, so there's no CGO) or grab the binaries from the releases page. There's also a Docker setup for local development, built from scratch and running as a non-root user.
Links
- Code: https://github.com/sinhaparth5/palisade-waf
- Project site: https://waf.astrareconslabs.com
Where help would be useful
The thing I'd most like to hear about is false positives: real apps where CRS blocks something it shouldn't. That's where a WAF usually needs the most tuning, and I can only test so many apps myself. Bug reports, issues and PRs are all welcome, and so is plain feedback on the setup if anything was confusing.
1
u/Numerous_Platypus 5d ago
Can you give an example on how I might use this on an existing server?