How it works
A proxy on your server, a control panel for your fleet
FlowGuard takes over ports 80 and 443 on the server itself and hands every request it lets through to your web server. Your sites, DNS and certificates stay exactly where they are.
The internet
-
GET /shop/house-espresso
Visitor
-
GET /sitemap.xml
Googlebot
-
GET /journal/
GPTBot
-
POST /wp-login.php
Botnet, 420 IPs
-
GET /.env
Scanner
Your server
FlowGuard proxy
-
1
Identify
Client IP, network, country and TLS fingerprint
-
2
Match
Your rules, top to bottom, first match wins
-
3
Act
In microseconds, before your app does any work
Stopped at the proxy
-
Rate limited
429
-
Challenged
PoW
-
Blocked
403
Allowed and logged requests
Your web server
nginx, Apache, Caddy, Traefik or your app, exactly as it is today.
- No configuration changes
- The real client IP in a header or as the source address
- Its certificates are reused by the proxy
- Only receives traffic your rules let through
Never leaves this server: the traffic itself, your TLS keys, request and response bodies, cookie values and authorization headers.
Rules, IP lists, GeoIP
Logs and heartbeats
FlowGuard control panel
Not in the request path
- Dashboards and incident analysis
- Live stream of every request
- Rules for one server or all of them
- Managed IP lists and GeoIP data
- Proxy versions and upgrades
- Emails when a proxy goes offline
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.
1
Add a server
Create the server in the control panel and copy its setup command.
2
Install the proxy
One command installs the package, finds your certificates and redirects ports 80 and 443. A clean stop removes the redirect again.
3
Watch and decide
Requests show up in the dashboard right away. Start from the basic actions and add rules as you learn what hits your sites.