Updated 16 September 2026
01 · what this page is, and what it avoids
What this page is, and what it avoids
This page makes no claim about what Vercel BotID does or does not do. Their capabilities change, their documentation is public, and a claim written here would be out of date before it was useful — and wrong in the direction that suits us, which is how these pages usually go.
What follows is the set of questions worth asking of either product, and a plain statement of where Botscope is the weaker choice.
02 · what to look for in either
What to look for in either
Where does it sit? A platform feature runs where the platform runs, which means it is already in the path and needs no installation — and is available on the platform it belongs to. Botscope classifies at your origin, after the edge has done whatever it does, which is why it sees what actually arrived rather than what was let through.
Can one decision be explained? Ask to see a single verdict with the signals behind it. If the answer is a score, the follow-up is what you tell a customer who was stopped by it.
What does it cost to find out? Whether you can answer either question above without a sales process is itself an answer.
Who is it for? if your application is on Vercel and you want protection switched on rather than deployed, the platform's own feature is the shortest path there is.
03 · where vercel botid is the better choice
Where Vercel BotID is the better choice
Nothing to deploy at all
Protection that is a setting on the platform you already use beats anything that needs installing, and no third party is added to your stack.
One vendor, one bill, one support thread
If something behaves oddly, the platform and the protection are the same company, which removes an entire category of argument.
04 · where botscope is the one to pick
Where Botscope is the one to pick
When the estate is not all on one platform, or when a decision has to be explainable outside it. Botscope runs anywhere PHP or a DNS record does, and hands the blocked visitor an ID they can look up.
Questions
Can I run both?
Usually yes, and often that is the right answer. Botscope classifies at the origin and does not sit in the request path, so it does not conflict with something running in front of it. What it adds is the record of what got through.
Why does this page not list their weaknesses?
Because we would be choosing which weaknesses to list, and you would have no way to check. The questions above are ones you can put to both vendors and compare the answers yourself.
How do I try Botscope without committing to anything?
The free tier is 100,000 events a month with no card and every feature on, and new sites start in observation mode — everything classified and recorded, nothing blocked. You can answer "what is actually reaching me" before deciding whether to act on it.
What does Botscope not do at all?
It is not a WAF, it is not DDoS protection, and it shows no CAPTCHA. It classifies requests and records why; it does not absorb volume and it does not replace whatever you run at the edge.
See which of these reach your site
Free plan, no card: 100,000 events a month with every feature on. Nothing is blocked until you turn enforcement on.