Faable Challenge
Hosted in the EU · No cookies

Bot protection for any form. No puzzles.

Faable Challenge stops scripted spam on contact forms, bookings and sign-ups with an invisible proof of work that the browser solves while people type. Your server verifies a one-time token with Faable — no image grids, no cookies, no third parties. Included in every Faable plan.

1,000 verifications a month on Free · No credit card required · Try it live

You just passed Faable Challenge

Came here from the badge on a form? This is what it did.

  • Your browser did a little maths

    While you filled in the form, it solved a small proof of work in the background — usually a fraction of a second. No puzzle, no images to click.

  • Your form carried a one-time token

    The site checked it with Faable before accepting what you sent. It works once and expires after 5 minutes.

  • Nothing followed you

    No cookies, no fingerprinting, no profile across sites. The widget never reads the fields of the form.

Faable runs this in the EU, on behalf of the site you used. To help it spot abuse, each check is logged — including the IP address that solved it — and kept for 30 days. What you wrote in the form goes to that site, not to Faable. See the privacy policy. This page itself, faable.com, uses its own analytics, which you can manage from the cookie banner.

Try it live

This is the real widget, on a real Faable Challenge site. Start typing: the badge starts solving on your first keystroke, and the token is usually ready before you press Send.

What the form carries
Waiting for you to start typing…

Protect a form in three steps

Works on any form, on any host — a contact form, a booking request, a newsletter or a sign-up that goes to your own backend.

  1. Step 1

    Create a site

    In the dashboard, name it and list the domains your form lives on. You get a public site key for the page and a secret key for your server.

  2. Step 2

    Add the widget

    One element and one script tag. The browser solves the challenge on the first keystroke and puts a one-time token in a hidden field of the form.

  3. Step 3

    Verify on your server

    Send the token and your secret to POST /v1/verify, and act on the form only if it answers success. A token works once and lasts 5 minutes.

Your page
<form action="/contact" method="post">
  <input name="email" type="email" required />
  <textarea name="message" required></textarea>
  <div class="faable-challenge" data-sitekey="fcs_pk_…"></div>
  <button>Send</button>
</form>

<script src="https://challenge.faable.com/v1/api.js" async defer></script>
Your server
curl -X POST https://challenge.faable.com/v1/verify \
  -H 'content-type: application/json' \
  -d '{"secret":"fcs_sk_…","response":"<faable-challenge-response>","remoteip":"<client IP>"}'

# → {"success": true, "hostname": "www.example.com", "action": "contact", …}

With a bundler: npm install @faable/challenge (MIT). Node.js, React and every option: Get Started · The Widget · Verify API

More work for riskier traffic

Every challenge starts at 18 bits — around 0.3 s in a laptop browser. Requests from a Tor exit node, a datacenter IP address or with a User-Agent no browser sends pay one more bit per signal, up to 21, and each bit doubles the work. The signals come back in the verify response for your server to weigh.

It already guards Faable Auth

Signup Protection on Faable Auth runs on Faable Challenge, and it never counts towards your allowance. If your own form creates Auth users, they can be marked as verified. With Faable Auth

Compared with a puzzle CAPTCHA

A puzzle asks people to prove they are human. Faable Challenge makes every request cost the sender a little CPU instead — nothing for one person, a lot for a script sending thousands.

What the person does
Faable Challenge: Nothing: the browser solves it while they fill in the form
Puzzle CAPTCHA: Ticks a box, and sometimes solves a visual puzzle
Cookies and tracking
Faable Challenge: None — no cookies, no fingerprinting, no cross-site profile
Puzzle CAPTCHA: Depends on the provider
Who processes the data
Faable Challenge: Faable, in the EU — the same provider that already hosts your app or your users
Puzzle CAPTCHA: A third party
What it proves
Faable Challenge: That the browser spent CPU on this request
Puzzle CAPTCHA: That someone (or something) solved the puzzle
Accessibility
Faable Challenge: No task to perform; the badge is announced to screen readers
Puzzle CAPTCHA: Visual and audio tasks can be a barrier
Server-side integration
Faable Challenge: One POST /v1/verify, the same shape as the common siteverify APIs
Puzzle CAPTCHA: One siteverify call
What it does not do
It does not prove there is a person: a real browser driven by automation solves it like any browser. Proof of work makes abuse in bulk slow and expensive, not impossible. It is not a rate limit either — your endpoint should still limit what it accepts. And it never sees your form's data: the widget sends your site key and an optional action label, never the fields.

Included in every plan

Nothing to add to your subscription and no metered line on your invoice: each plan includes verifications a month and a number of sites, per project. The same plan covers Faable Deploy and Faable Auth.

Free
€0forever
  • 1,000 verifications a month
  • 1 site
Start free
Hobby
€15per month + tax
  • 10,000 verifications a month
  • 5 sites
Start free
Pro
€99per month + tax
  • 100,000 verifications a month
  • Unlimited sites
Start free
  • Going over never breaks a form: verification keeps working, and the dashboard suggests the next plan.
  • Only successful verifies count — not challenges issued, not failed checks.
  • Faable Auth's Signup Protection never counts, whatever its volume.

Prices in EUR, excluding VAT · No credit card required to start · What counts · Everything each plan includes

Frequently asked questions

What is Faable Challenge?

Bot protection for any web form. The browser solves an invisible proof of work while the person fills in the form, and the site's server verifies the resulting one-time token with Faable before acting on the submission. No puzzles, no image grids, no cookies and no third parties. Hosted in the EU.

I clicked the badge on someone's form. Did Faable track me?

No. The widget sets no cookies, does no fingerprinting and builds no profile across sites, and it never reads the fields of the form. Faable processes the check on behalf of the site you used: to help it spot abuse, each check is logged with the IP address that solved it and kept for 30 days. What you wrote goes to that site, not to Faable. The details are in Faable's privacy policy.

Why did the check take longer for me?

Requests that look risky get more work: one extra bit of difficulty per signal — a Tor exit node, a datacenter IP address (a VPN or a cloud server) or a User-Agent no browser sends — up to 21 bits. Each bit doubles the expected work, so on a phone it can take a few seconds instead of a fraction of one.

Does it prove that there is a human?

No, and no proof of work can. A real browser driven by automation solves it like any other browser. What it does is make abuse in bulk slow and expensive: every request costs the sender real CPU, and a token works only once.

Do I need to host my app on Faable?

No. Faable Challenge protects any form on any host: create a site with your domains, add the script and the element to the page, and call POST https://challenge.faable.com/v1/verify from your server. It also has an npm package, @faable/challenge, for bundlers and single-page apps.

How much does it cost?

It is included in every Faable plan, per project: Free has 1,000 verifications a month and 1 site, Hobby (€15 a month) 10,000 and 5 sites, Pro (€99 a month) 100,000 and unlimited sites. Only successful verifies count, going over never breaks a form, and Faable Auth's Signup Protection never counts.

Stop form spam without a puzzle

Create a site, paste two snippets and verify on your server. Hosted in the EU, included in every plan — 1,000 verifications a month on Free, no credit card required.