FlowGuard

A security proxy on your own servers. See every request, stop the bad ones.

Install the open-source proxy in front of the web server you already have. It filters scanners, brute force and abusive bots with your rules, and the control panel shows you exactly what reaches your sites. No DNS changes, no traffic through us.

The FlowGuard dashboard with proxied, blocked and rate limited requests over the last 24 hours and the domains, user agents, networks, rules, actions and servers behind them

Ubuntu, Debian, RHEL, Rocky Linux, AlmaLinux and Fedora · amd64 and arm64 · or as a Caddy plugin

Questions you can answer in seconds

  • Who is hammering wp-login.php right now?
  • Is this spike an attack or a launch?
  • Which networks send the most blocked traffic?
  • How often do AI crawlers visit my sites?
  • How many requests did this rule block today?
  • What did this IP address do in the last hour?
  • Did my new rule break checkout?
  • Which servers run an outdated proxy?

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. 1 Identify Client IP, network, country and TLS fingerprint
  2. 2 Match Your rules, top to bottom, first match wins
  3. 3 Act In microseconds, before your app does any work
Stopped at the proxy
  • Rate limited
    429
  • Challenged
    PoW
  • Blocked
    403
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.

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.

$ curl -fsSL https://pkg.flowguard.network/install.sh | sudo bash
$ sudo flowguard setup fgsvr_…

Live request stream

See every request, as it happens

Your web server logs tell you a path and a status code. FlowGuard logs who sent the request, from which network and country, with which TLS fingerprint, and which of your rules decided what happened to it.

  • Filter with a simple query language, such as rule.result:block client.country:CN
  • Open any request for its headers, fingerprint, timings and the rule that matched
  • Jump to a moment in time and see what happened around it, or export what you found
  • Block a client IP straight from the stream when you spot something you do not like
The live request stream with proxied, blocked and rate limited requests to several sites, with their method, path, user agent, status, client IP and server

Incident analysis

Know in seconds whether a spike is an attack

When traffic jumps, the analysis view shows the shape of it: how many clients, networks and countries are behind it, how it compares to the hour before and to yesterday, and which TLS fingerprints the requests share.

  • Requests per second, unique clients, networks and latency at a glance
  • Comparison with the previous interval and the same time yesterday
  • JA4 fingerprint correlation finds a botnet hiding behind hundreds of addresses
  • Top paths, methods, HTTP versions and countries, for the whole fleet or one server, rule or action
The incident analysis of a credential stuffing wave against a WordPress login, with request rates, unique clients and networks, baseline comparisons and top paths and countries

Rules

Rules as precise as the traffic you want to stop

Combine conditions with AND, OR and NOT groups and match on anything in the request. Rules apply to all servers or just the ones you pick, and reach your proxies within seconds, without a restart.

  • Path, method, domain, headers, query parameters, cookies and user agent
  • IP address and CIDR, network (ASN), country, continent and JA4 fingerprint
  • Request rates per client, fingerprint or path, to catch bursts and scrapers
  • Block, rate limit by client IP, fingerprint, domain or path, challenge with proof-of-work, allow or log
The rule editor with a rule that rate limits POST requests to the WordPress login and XML-RPC paths, using a nested condition group

Rule insights

See what every rule actually does

Every rule shows how many requests it matched in the last 24 hours, so you notice the rule that never fires and the one that suddenly blocks everything. Open a rule for its own dashboard: the domains, networks and user agents it caught.

  • Traffic sparklines next to every rule, action and server
  • Drag rules to change their order, the first match wins
  • Share a rule as a link, or copy it as a Cloudflare expression
  • A dashboard per rule, action and server with the same filters as the overview
The rules list with twelve rules in evaluation order, the action each one takes and a sparkline of the requests it matched in the last 24 hours

IP lists

Reputation data, kept up to date for you

Use the managed lists in your rules to block known abusers and let the good bots and services through, or keep your own lists of offices, partners and offenders. Lists update on your proxies without a restart.

  • AbuseIPDB, with a confidence threshold you choose per rule
  • Search engine and AI crawlers: Google, Bing, Apple, OpenAI, Anthropic, Perplexity and more