Everything FlowGuard does, on every plan
A self-hosted security proxy on your servers and a control panel for your whole fleet. Your traffic never leaves your infrastructure.
A security proxy that runs where your sites already are
FlowGuard is a single Go binary on your server. It takes over ports 80 and 443, filters every request with your rules and hands the rest to the web server you already have.
nginx, Apache, Caddy, Traefik or your app, exactly as it is today.
Never leaves this server: the traffic itself, your TLS keys, request and response bodies, cookie values and authorization headers.
If the panel is unreachable, your sites keep working and the proxy keeps filtering with the configuration it has. Prefer your own stack? The proxy also writes logs to files, Loki or OpenObserve and runs from a configuration file.
Ports 80 and 443 are redirected to FlowGuard with iptables or ip6tables, no changes to your web server or DNS. A clean shutdown removes every firewall rule FlowGuard added, and missing rules are repaired automatically.
TLS is terminated with the certificates you already have, loaded from NGINX configuration, a directory or Traefik acme.json. Renewed certificates are picked up without a restart.
HTTP/1.1, HTTP/2 and HTTP/3 on IPv4 and IPv6, on as many addresses as you bind. Regular expressions are compiled when the configuration loads and IP lists use prefix tables, so rules evaluate in microseconds.
Trusted proxy chains, CDNs and PROXY protocol from layer 4 load balancers are resolved before rules run. Your backend receives the client IP in canonical headers, or as the source address on same-host setups.
Rules, IP lists, certificates and log destinations reload without dropping connections. On shutdown, in-flight requests get time to finish.
Already on Caddy? Run FlowGuard inside it: Caddy keeps its listeners and certificates, FlowGuard evaluates rules, writes logs and stays connected to the control panel. No firewall changes or root access needed.
A fleet server lets any number of containers or machines, such as Fly.io machines, share one key. Instances come and go without setup and show up individually.
Bans from your active Fail2Ban jails are enforced at the proxy, and show up in the logs with the jail that banned them.
Decide exactly what happens to every request
Rules run top to bottom and the first match decides. Actions are reusable, so one change to "Block request" applies to every rule that uses it.
Path, method, domain, headers, query parameters, cookies, user agent, IP or CIDR, ASN, network name, country, continent, JA4 fingerprint and IP lists. Combine conditions in nested AND, OR, NAND and NOR groups.
Match on how many requests a client, fingerprint or path sent in the last second, ten seconds or minute, and on how many addresses, networks and countries share one TLS fingerprint.
Limit requests per client IP, connection, JA4 fingerprint, domain or path, or a combination of them. Visitors stay below the limit, bots and brute force do not.
Ask browsers to solve a small proof-of-work before they reach a page. Real visitors barely notice, scripts and headless scrapers stop there.
Block with the status and message you choose, allow trusted traffic past later rules, or log matches and let evaluation continue.
Apply a rule to every server, a selection, or all servers except a few. Changes reach your proxies within seconds.
Share a rule with a link, or copy it as a Cloudflare expression for the places where you also use Cloudflare.
Drag rules into the order you want. Each one shows how many requests it matched in the last 24 hours, so a rule that never fires stands out.
Know who is behind every address
Every request is enriched with the country and network it came from, and you can match it against lists that are kept up to date for you.
The country, network and organization of every client. The databases refresh automatically without downtime.
AbuseIPDB with a confidence threshold, search engine and AI crawlers, webhook senders, uptime monitors and CDNs, from Google and OpenAI to Stripe and Cloudflare, kept up to date for you.
IPv4 and IPv6 addresses and CIDR ranges in one list, with a comment per entry. Import in bulk, or block a client straight from the request stream.
Every HTTPS request carries its JA4 fingerprint, which stays the same when a botnet rotates through hundreds of addresses.
See what reaches your servers, down to a single request
Request logs flow into the control panel, where dashboards, the analysis view and the live stream show what is happening and why.
Requests over time by result, with the top domains, user agents, networks, rules, actions and servers, for the whole fleet or one server, rule or action.
Request rates, unique clients, networks and countries, latency percentiles, comparisons with the previous interval and yesterday, and JA4 fingerprint correlation for any time window.
Every request as it happens, with a query language to filter, a detail view per request, jump to a moment in time and export.
Each entry holds request, client, rule and response details. Only allow-listed headers are logged, never bodies, cookie values or authorization headers.
Send logs to the control panel, files, Loki or OpenObserve, or several at once.
A REST API to query logs and manage rules, actions, servers and IP lists, and an MCP server so an AI assistant can investigate traffic and propose rules.
Easy to install, easy to keep up to date
Install from a package repository, connect the server with one command, and let the control panel keep your proxies current.
Install from the APT or YUM repository on Debian, Ubuntu, RHEL, CentOS, Rocky Linux, AlmaLinux and Fedora, on amd64 and arm64. The setup command finds your certificates and configures the rest.
Upgrade proxies from the control panel, or let them upgrade automatically once a release has been out long enough to prove itself.
An email when a proxy goes offline and when it is back, and a weekly report of what FlowGuard handled on each server.
Invite your colleagues and manage your servers together, with every team member seeing the same rules and logs.
The proxy is open source under the Apache 2.0 license. Review the code, contribute, or build it yourself.
The control panel is optional: the proxy also runs from a JSON configuration file, with a JSON schema for autocompletion and validation in your editor.
Every protection feature is on every plan
Plans differ by the number of servers and the request logs we keep for you, not by what FlowGuard can do.
Need help?
We are happy to help you with any questions you might have.
Documentation Roadmap Changelog Report a bug Get in touch