Fingerprint gives each browser a visitor ID that stays the same for weeks, with signals such as bot detection, VPN and tampering: it answers "have I seen this device before?". Bot Protection answers "is this request a person or a bot, right now, and why?", for $29 a million. Bot Protection remembers a visitor for minutes, not weeks, so for returning fraudsters Fingerprint is the better tool today.
At a glance
| Bot Protection | Fingerprint | |
|---|---|---|
| How it works | A tag on your pages reads how the browser behaves; before a sign-up, sign-in or checkout your server makes one call and gets a decision. | A JavaScript agent identifies the device; your server reads the identification event, with Smart Signals, through Fingerprint's Server API. |
| What your visitor sees | Nothing. | Nothing. |
| In your request path | No. Your server calls it with your own timeout. | No. Your server calls Fingerprint's API. |
| What your server gets | A class (human high to bot high), a bot score, the reasons, and an action: allow, challenge or block. | A visitor ID with its confidence, and Smart Signals (browser bot detection among them). |
| When it is down | Your server lets the visitor through: fail open. | Not stated; the docs' anti-tampering example rejects a request whose identification is missing. |
| Watch before it blocks | Yes: in monitor mode every answer is allow, with what block mode would have done. | Does not apply: it never blocks; your code decides what to do with the result. |
| Price to start | A 14-day free trial with 10,000 decisions, then $29 a month for 1 million. | Free: 1,000 API calls a month, without browser bot detection. Pro Plus, which has it: $99 a month for 20,000 calls, then $4 per 1,000. Enterprise through sales. |
| Integration | The tag, and one call from your server; a prompt for your coding agent does both. | The agent on your pages, and a server-side read of each event. |
| Where it runs | Servers in Germany (EU); IPs and tokens are kept only as keyed hashes. | Fingerprint's cloud. |
When Fingerprint is the better choice
- You need to know a device came back: multi-accounting, shared accounts, the same fraudster with a new email weeks later.
- Your fraud team builds its own rules on a stable device ID.
- You need mobile identification for Android and iOS.
When Bot Protection is the better choice
- You want a decision and its action per request, not an ID to build rules on.
- Volume: 1 million decisions cost $29 on Starter; 1 million Fingerprint calls on Pro Plus cost about $4,000.
- You want groups of sessions caught as a farm, with the reasons, from day one.
Using both
A good pair: Bot Protection decides each sign-up; store Fingerprint's visitor ID with the account to spot the same device coming back for another trial.
Questions
Is Fingerprint bot protection?
Bot detection is one of its Smart Signals; its core is identifying a device across visits.
Does Bot Protection fingerprint browsers?
It reads how the browser behaves and whether its signals agree, and keeps them only as keyed hashes, for minutes: enough to judge a session and its group, not to follow a person for weeks.
Sources
Checked on the vendors' own pages on 17 October 2026; prices change, so check theirs before you decide.
- Fingerprint pricing
- Fingerprint Bot Detection quick start
- Fingerprint Smart Signals reference
- Fingerprint: protecting from client-side tampering
- Fingerprint: planning your implementation
- Fingerprint CloudFront proxy integration
Bot Protection: the quickstart, pricing, and every comparison.