Skip to content

SYSTEM Cited by 1 source

Kasada (bot management)

Kasada (kasada.io) is a third-party bot-management vendor whose ML backend powers Vercel BotID — including the Deep Analysis subsystem described in Vercel's 2026-04-21 production-incident post. Stub page on the wiki; Kasada appears only as a branded dependency inside Vercel's product surface, not as an independent subject.

What the 2026-04-21 post discloses about Kasada

  • The classifier is "powered by Kasada's machine learning backend" — Vercel's product wraps Kasada, not the other way around.
  • The ML backend is responsible for per-session scoring, cross-session correlation, proxy-node identification, and adaptive re-verification — the Deep Analysis loop runs inside Kasada, not inside Vercel's edge tier.
  • The backend supports real-time learning — new browser profiles observed in one incident feed back into classifier priors in minutes, not days.
  • 40-45 new browser profiles across "thousands of requests" was the fleet size in the canonical incident; the ML backend handled the analysis with ~3-minute analysis window and ~1-minute re-verification trigger latency.

The post does not publish:

  • The Kasada model architecture (dense vs GBT vs ensemble).
  • Feature list or feature-extraction pipeline.
  • FP / FN rates or AUC.
  • Training data volumes or refresh cadence.
  • Latency budget per scoring decision.
  • Whether Kasada's backend is regional, global, or on-prem.

Position in the bot-management vendor landscape

  • systems/cloudflare-bot-management — integrated first-party product inside Cloudflare's edge.
  • Kasada — third-party backend embedded into customer products (here, Vercel BotID). Different go-to-market: the customer is a frontend-cloud vendor, not the end-application.
  • Both run ML over content-independent features to produce a probabilistic bot score; both refuse to publish feature lists on the deliberate-opacity principle; both frame the problem as continuous retraining rather than static rules.

Strategic implications

  • Because Vercel BotID is "powered by Kasada", evaluating Vercel's bot-management capability on independence grounds requires evaluating the Kasada vendor relationship — pricing, SLAs, exfiltration / data-handling, roadmap control.
  • Wiki-first disclosure of this dependency happens through the 2026-04-21 post; prior Vercel coverage on the wiki (sources/2024-08-01-vercel-how-google-handles-javascript-throughout-the-indexing-process) did not surface Kasada as an embedded vendor.

Caveats

  • Wiki stub. All content here is inferred from a single Vercel-side post. No direct Kasada source is ingested.
  • Trade-name vs product-name ambiguity. The post says "Kasada's machine learning backend" — whether the exact product component is branded "Kasada Bot Defender", "Kasada Advanced", or something else is not specified.

Seen in

Last updated · 476 distilled / 1,218 read