-
Use certificates issued by certbot
FlowGuard can now serve the certificates that certbot manages, whichever web server uses them, such as Apache with certbot's Apache plugin. Point the certificate path at
/etc/letsencrypt, or accept the suggestion fromflowguard setupwhen it finds no other web server configuration. -
Install FlowGuard on servers without systemd, including EL7
FlowGuard now installs and runs on servers without systemd, such as Ubuntu 14.04, Debian 8 with SysV init, and containers. The packages include an init script and choose the right init system when you install, upgrade, or remove FlowGuard. Upgrades from the control panel work on these servers as well.
-
Set up FlowGuard on servers without a public IP address
On a server behind NAT or a load balancer, use
--bindto tellflowguard setupwhich addresses to listen on, for examplesudo flowguard setup --bind 10.0.0.5. Setup checks that each address belongs to the machine and keeps it for later runs. When FlowGuard finds no public IP address, it suggests a--bindvalue. -
Set up FlowGuard on DirectAdmin and CloudLinux servers
The install script now supports CloudLinux, and also other distributions derived from Debian, Ubuntu, or RHEL. On a DirectAdmin server,
flowguard setupoffers to load certificates straight from DirectAdmin: each domain's certificate and the server hostname's certificate, whichever web server DirectAdmin runs. Renewed certificates and new users are picked up without a restart. -
Run FlowGuard inside Caddy, or as a fleet of instances that share one key
If Caddy already serves your sites, you can run FlowGuard as a Caddy plugin instead of in front of Caddy. Build Caddy with
xcaddy build --with go.chief.tools/flowguard-proxy/caddy, then add theflowguardglobal option with your host key and theflowguarddirective to each site. Caddy keeps handling TLS, certificates, and proxying. FlowGuard evaluates rules, writes request logs, and stays connected to FlowGuard. No setup command, firewall redirects, or root access are needed. -
Leave matching requests out of the logs
Create an action of the Skip Log type to keep noisy requests, such as load balancer health checks, out of your request logs. Evaluation continues after the rule matches, so later rules still apply.
-
Accept PROXY protocol from your load balancers
FlowGuard can now run behind a layer 4 load balancer, such as AWS NLB or HAProxy in TCP mode, and still see the real client IP. Under Settings → Trusted proxies → PROXY protocol, add the IP list that contains your load balancers' addresses, then enable the PROXY protocol on the load balancer.
-
Export filtered logs as CSV or JSON Lines
Use the export button in the Stream to download the logs that match your current filter. Choose a time range: the last 15 minutes, hour, 24 hours, or 7 days, or a custom range. Pick CSV with the visible columns for spreadsheets, or JSON Lines with every field for jq, scripts, or a SIEM.
-
Ignore letter case in log filters and rule conditions
Text filters in the Stream, such as
contains,starts-with, andends-with, now ignore letter case. Usecontains-cs,not-contains-cs,starts-with-cs, orends-with-cswhen case must match exactly. New rule conditions also have Case Insensitive turned on by default. See Match letter case exactly. -
Rate limits apply per client by default
Rate-limit actions that use the Default scope now give each client IP its own bucket. Previously the default bucket was shared by all clients, so one client could use up a limit, such as a login limit, for everyone. IPv6 clients are grouped by /64, so rotating addresses within one allocation no longer gets a fresh allowance.
-
Rules match request values the way backends read them
Proxy v0.27.0 reads request values the way common backends do, so requests can't slip past a rule by spelling a value differently:
-
Give AI agents access to all your teams at once
When you connect an AI client such as Claude, ChatGPT, or Codex to FlowGuard, you can now choose All my teams instead of a single team. The agent can then investigate logs and manage rules for every team you belong to, including teams you join later. It names the team on each request and asks you when the intended team is unclear.
-
Upgrade proxies automatically
Turn on Upgrade proxies automatically under Proxy upgrades in settings. Once a day, every online server that allows remote upgrades is upgraded to the latest proxy release. A release that failed to install on a server isn't retried there automatically.
-
Add country and request ID headers to backend requests
FlowGuard proxies now add two headers to requests sent to your backend:
-
View usage and log history in settings
Settings now shows FlowGuard proxy usage against your team limit, logs received this month against the monthly limit, retained log count, and stored log size. Open the Usage page to see daily log volume and storage history for the last 90 days.
-
Set rate limits by IP, fingerprint, domain, or path
Rate limits can now use explicit buckets for each client IP, connection, JA4 fingerprint, domain, or path. Combine dimensions to give each unique combination its own allowance and tune limits to the traffic you want to control.
-
Create rules based on traffic behavior
Rules can now use behavior metrics such as client request bursts, concurrent requests, and JA4 fingerprint activity. Choose a metric and numeric threshold, then pair the condition with an action to respond to unusual traffic.
-
Investigate incidents with traffic analysis
The dashboard's Incident analysis view brings together the signals needed to investigate recent traffic. It shows request volume, average and peak request rates, latency, top paths, methods and countries, and related JA4 fingerprints.
-
Jump to a specific time in the log stream
Choose a date and time in your browser's timezone to load retained requests near that moment in the log stream. Browse earlier and later events for context, then return to the live stream when you are done.
-
Connect AI assistants through MCP
FlowGuard now has an MCP endpoint at
https://flowguard.network/mcpfor compatible AI assistants. Connect it to inspect request logs, list the rules, actions, proxies and IP lists in your team, and investigate an event using its stream ID or surrounding log window.