Pricing
Pro starts with a 14-day trial, every feature unlocked. The free tier runs without an account, before or after.
Runs without an account. Good for one site with ordinary bot noise.
Cloud scoring for sites where bots are costing you money.
14-day trial, every feature unlocked
For volume, bespoke terms, or more sites than a single plan covers — with a person on the other end.
The split is the same on every integration — JavaScript, PHP and the WordPress plugin.
| Capability | Free | Pro | Custom |
|---|---|---|---|
| User-agent whitelisting | ✓ | ✓ | ✓ |
| Login page protection | ✓ | ✓ | ✓ |
| Rate limiting | ✓ | ✓ | ✓ |
| Known-bad-bot blocking | ✓ | ✓ | ✓ |
| Works without an account | ✓ | — | — |
| Cloud verification | — | ✓ | ✓ |
| Deep detection | — | ✓ | ✓ |
| VPN, proxy and emulator blocking | — | ✓ | ✓ |
| Verified crawler allow-list | — | ✓ | ✓ |
| Dashboard with filters | — | ✓ | ✓ |
| Signed cookie for server-side checks | — | ✓ | ✓ |
| Priority support with a named contact | — | — | ✓ |
| Volume pricing and agreed terms | — | — | ✓ |
Yes — fourteen days of Pro with every feature unlocked, so you can see what the cloud scoring catches on your own traffic before deciding.
BlockBots steps aside and your site keeps serving with protection off. A notice appears in the dashboard. Protection going quiet is never as expensive as real visitors stranded on a screen they cannot get past.
No. Crawlers you allow are verified against the cloud rather than trusted on their user agent, so Googlebot gets through and anything borrowing its name gets a 403. Verdicts are cached, so a crawler costs one call an hour rather than one per page.
No. The JavaScript SDK covers the browser, the PHP file and the WordPress plugin cover the server. Most sites use one; using both means a bot is turned away before your page is built and again if it reaches the browser.
No. A script tag, one PHP file, or the plugin. No build step, no Composer, no database and no infrastructure of your own.
The free tier needs no account and no card. Add the script tag, the PHP file or the plugin, and see what it catches.