Kasada
cdn-bot-manager · private
Marketing claims
No claim captured yet.
Claim archaeology — what has been marketed, and when
Monthly Wayback snapshots of the 1 page listed below, read back to 2019. A number reaches this timeline only after the sentence around it was read and judged to be Kasada describing its own product. Those judgements were made by an AI model (claude-opus-5) and have not yet been checked by a person. Every one is published with the quote it was made from and the reason it was made, so you can check it against the archived page yourself. Numbers that turned out to be customer case studies, uptime SLAs or traffic-composition stats are listed further down — recorded, not published. Nothing is inferred between two dated snapshots.
No claim we could publish as Kasada describing its own product has been found in any of the 79 months we were able to read on the pages we track, out of 92 probed between 2019-01 and 2026-08. That is a statement about these pages only — see the list below.
No publishable claim was found on these pages for: detection accuracy, coverage, false-positive rate, decision latency. Numbers we found and held back are listed below.
Our extractor pulled these numbers out of the same snapshots. Each was held back: a number bound to a metric is not automatically the vendor claiming a capability, and treating it as one would score Kasada against something it never said.
| Number | Seen | What it actually is | Archived |
|---|---|---|---|
| 200% | 2026-06 – 2026-07 2 months | not a vendor claim an analyst ROI figure, not a detection claim…Kasada | Stopping Automated Threats | Web & API Protection Skip to content Forrester found 200% ROI when enterprises switched from legacy bot protection to Kasada See How → Solutions Use Cases Account Takeover… | link |
| 90% | 2026-08 1 month | not a vendor claim traffic composition observed in one deployment - what share of requests were bad bots, not what share Kasada detects…Kasada caught alongside Akamai Bot Manager Deployed behind the incumbent bot-management provider, Kasada identified 90% of all requests as bad bots — 98% of them low-sophistication traffic that never executed Kasada’s JavaScript.¹ In… | link |
| 98% | 2026-08 1 month | not a vendor claim traffic composition within that same deployment's bad-bot traffic, not a detection claim…Bot Manager Deployed behind the incumbent bot-management provider, Kasada identified 90% of all requests as bad bots — 98% of them low-sophistication traffic that never executed Kasada’s JavaScript.¹ In this deployment, Kasada observed a… | link |
| Page | Era | Months probed | Months read |
|---|---|---|---|
| www.kasada.io/ 2019-01 – 2026-08 | current | 92 | 79 |
“Months read” counts snapshots we actually retrieved and searched.
Sanctioned test surfaces
| Surface | Type | Tier | Basis |
|---|---|---|---|
| Free demo account | self-deploy-trial | B | Self-serve trial we own |
A — vendor invites testing · B — our own deployment · C — passive observation
Our test results
No sanctioned runs recorded yet.
Real-world challenge rate (passive, anonymized)
Across 2 sites detected running Kasada, this is what a default automated client met:
ServedChallengedBlocked
Challenge rate 100.0% — 95% CI 34–100% (±33pp, n=2). A wide interval means a small sample; read it accordingly.
Site identities are not published. This measures whether a vanilla client is challenged — no bypass performed.
⚠ Only 2 site(s) measured — too small a sample to draw a reliable rate from; shown for completeness.
Detection is by CDN fingerprint, so “served” means the site sits behind Kasada but a default bot was not actively challenged — CDN presence is not proof the paid bot-management product is engaged. The challenged + blocked share is where protection actively fired.
Cited external benchmarks
- Scrapfly — Kasada bypass — reported bypass 94%Self-reported by Scrapfly (commercial bypass API) — vendor marketing figure, not independently verified (captured 2026-08-14).
- techinz/browsers-benchmarkIndependent open-source browser-automation benchmark; per-engine bypass rates vary.
We cite these rather than generating real-world bypass numbers against non-consenting production systems. Commercial-vendor figures are self-reported marketing claims, flagged as such above — treat them as the ceiling a paying bypass service advertises.