Challenge bots on your own server — no third party, no cookie banner.

A rule on your own edge sends a suspicious visitor to a proof-of-work puzzle their browser solves in well under a second — instead of a 429, or a captcha served from someone else’s network. The puzzle, its check and the pass all come from your node.

  • Proof of work, self-hosted. The challenge page is served by the node itself; nothing leaves the site. Cloudflare Turnstile instead, if you prefer it.
  • A pass that cannot be forged. A solved puzzle earns a cookie signed with your node’s secret, good for an hour by default and tied to the visitor’s address. Your rule checks it.
  • Honeypots and temporary bans. Whoever fetches a path robots.txt forbids, or keeps failing the puzzle, goes on a ban list for a while — and comes off on its own.
  • In front of your app, or inside it. A reverse proxy for an origin in any language, or a servlet filter in a Java app. Your rules are one text file.
# conf/guard-rules.conf — one line
search-challenge | uri~^/search ; client-type:guest ; !cookie-hmac:fc_pass ; rate:30/1m | challenge pow

Guests without a pass who search more than 30 times a minute solve a puzzle instead of getting a 429. Challenge pages are Pro; without them the same rule runs as a dry run, logged and harmless.

Show us the bots on your site — 45 minutes with an engineer

$200, credited toward a Cacheability Assessment or Pro. Which paths the bots hit, and the rules that would challenge or ban them.

1. Pick a time

Times are in your time zone.

Loading open times…

2. About you

Reschedule free up to 24 hours before by replying to the confirmation email; if we cancel, you get a full refund; a session missed without notice is not refunded. Payment by PayPal — privacy policy.

Not ready for a call? Tell us about your bot traffic — free.

Four Steps, All on Your Own Edge

The edge is the layer you run between the internet and your app. It sees every request before your app does — so a request refused or challenged there is a page your origin never renders.

  1. Classify Every request is a crawler, a guest or a type you declare in bots.conf — and a crawler can be required to come from its own published network, so a fake Googlebot is not a Googlebot.
  2. Decide A guard rule names the path, the visitor type, the rate and “no pass yet”. Ship it as a dry run first and watch its hit count in the log and the metrics.
  3. Challenge A matching page view goes to the puzzle; a form post gets a 429 with Retry-After, never a lost body. Fragments and the challenge page itself are never challenged.
  4. Remember A solved puzzle is a pass for an hour. An address that keeps failing, trips a limit or takes the honeypot bait goes on the ban list for a while (Pro), and your own last rule refuses it.

Two Text Files You Can Read

The rules decide; the Pro plugins only act on what the rules say. A guard rule sends a visitor to a challenge. The challenge page shows the puzzle and checks the answer. The pass is checked by the same open-source rule engine that sent the visitor there, with a key the plugin never sees.

A honeypot is a link nobody can see, to a path your robots.txt forbids. A person never follows it and a polite crawler is told not to — so one request is enough. The node logs the address it resolved behind your proxies, not the one a scanner wrote in a header.

Bans are temporary and bounded. Each defence rule says how many events in what window earn a ban, and for how long; a repeat offender’s ban doubles up to a ceiling you set. Loopback, private ranges, your own proxies and anything you list in never are never banned. dry-run = true counts what a rule would ban and bans nothing — start there.

Every rule, page and ban reloads without a restart, from the console or the node.

# conf/guard-rules.conf — first match wins.
# Your exemptions (monitoring, verified crawlers) go first.
banned | client-ip:@lists/banned.txt | reject:403 Forbidden

honeypot | uri~^/no-crawl/ | reject:404 Not Found | trap

challenge-verify | uri~^/fc-x/challenge/verify ; rate:10/1m | reject:429

search-challenge | uri~^/search ; client-type:guest ; !cookie-hmac:fc_pass ; rate:30/1m | challenge pow

The ban list is refused; the honeypot is caught; the puzzle’s own answers are rate-limited; guests who search too fast get a puzzle.

# conf/defence.conf (Pro) — what earns a ban
defence {
  list  = banned
  rules = [
    { name = trap,   on = guard.matched, rule = honeypot,
      ban = 1h, max-ban = 1d }
    { name = failed, on = challenge.result, outcome = fail,
      threshold = 5, window = 10m, ban = 6h, dry-run = true }
  ]
}

One honeypot hit bans for an hour, longer each time it comes back. Five failed puzzles in ten minutes would ban for six hours — once the dry run shows it catches only what you meant.

Your Visitors Never Leave Your Infrastructure

Exactly what goes where, so the privacy page stays true.

Proof of work: nothing leaves the site

The page, its script and the check are served by your node under /fc-x/challenge/. No third-party script, no tracking, and the only cookie is the pass itself — set once the visitor has solved the puzzle.

Turnstile: optional, and it calls Cloudflare

If you configure Cloudflare Turnstile instead, the visitor’s browser and your node talk to Cloudflare to verify the answer. An outage there is never a free pass: the visitor is asked to try again.

Who decides: open-source code

Every decision about a visitor’s request — challenged, refused, let through — is made by the open-source engine, from rules you wrote. Remove the Pro jars and the same rules run on the free engine: a challenge rule becomes a dry run, and nobody is left banned.

The Rules Are Free. The Pages and the Bans Are Pro.

Everything a request needs is in the Apache-2.0 engine. Pro adds the challenge pages and the defence that acts on its own — $3,600 per node per year, 2-node minimum.

Capability Community — free Pro
Guard rules, rate limits, dry run Included Included
Honeypot paths Included — logged with the real address Included, and can ban
Verified crawler lists Googlebot, Bingbot, Applebot — an open-source example plugin Included
Challenge rules and the signed pass The rule and the pass check; with no challenge page it runs as a dry run, or as the reject you name Included
Challenge pages Your own page can sign a pass the engine accepts Proof of work, or Cloudflare Turnstile; your own template
Temporary bans A list you keep yourself, read live From limits, honeypot hits and failed challenges; released on time
Alerts Metrics and logs to alert on Slack, Teams, PagerDuty, Opsgenie, webhook, mail, syslog — e.g. when the pass rate falls

Application-Layer Defence, Not Bot Management

Know where the line is before you buy anything.

Not a bot detector

No fingerprinting, no reputation network, no machine learning. A puzzle makes every pass cost work; a scraper driving a real browser can still solve it — and then meets your rate limits and the ban list. If you need detection, keep your bot-management vendor.

Not a WAF or a DDoS service

No signature set, no TLS termination, no global network to absorb a flood. Put a CDN in front if you need one; this is the edge behind it, next to your app.

Each node bans on what it sees

Bans are per node today, with no fleet-wide list yet, and a pass is tied to the address that earned it. Behind a load balancer, set the shared secret so any node can check any puzzle.

Find Out Which Bots Your Rules Would Catch

45 minutes with an engineer on your own traffic: which paths bots hit, and the rules that would challenge, slow or ban them. $200, credited toward an Assessment or Pro — or ask us a question for free.