Bot detection, made self-serve.
We built Botect for the gap between a coarse on/off toggle and the heavyweight enterprise tools — a real score, a real API, real behavioral signals, self-serve.
We ran content sites that got scraped. The bots weren’t crude — they ran real browsers, set cookies, and slipped right past the on/off toggle our CDN offered. The only tools that actually caught them started at thousands of dollars a month and a sales call.
So we built the thing we wanted: a detector that scores every request 1–99, reads the behavioral signals the big providers skip, and shows its work. No black box, no enterprise minimum, no waiting on a quote.
We dogfood it on our own traffic before anything ships. On one site we protect, the scores showed roughly 98% of the “traffic” was automated. That’s the problem Botect exists to make visible — and then to stop.
Principles we build on.
No black boxes
Every score ships with the detections behind it. You can see why a session scored the way it did — and override it with a rule you wrote.
Observe before you block
Enforcement is off by default. You watch real scores against your own traffic and turn protection on when the numbers earn it — not before.
Fail open, always
A detection product should never be the reason a real customer hits a wall. When in doubt, Botect allows — degradation is our problem, not your users’.
Specific over salesy
We quantify instead of hype. 1–99 scores, <50ms p99, 30-day retention. Confidence comes from the numbers, not the adjectives.
Specific over salesy.
score per session
p99 verdict read
detection engines
raw-event retention
Talk to us
Questions, feedback, or a traffic problem you want a second opinion on? Email the team — a human reads every message.
See your traffic the way we see ours.
Sign up, drop in the SDK, and find out how much of your traffic is actually human.