Kasada

---

What Kasada actually does

The root site of a vendor whose approach leans on client-side proof-of-work and heavily obfuscated sensor code rather than on scoring a set of collected attributes.

What can and cannot be measured about Kasada

This entry has no repository, so none of the usual repository fields exist for it — no push date, no release tag, no archive flag, no licence identifier. Its state comes from one measurement only: the register requested the address and recorded what came back. Anything in the range 200 to 399 makes a non-repository entry ACTIVE, and that clause is the one the first edition of the rubric did not have at all, which is why documentation entries carried no state under it.

Read that for exactly what it is. It says the thing is reachable. It does not say the documentation matches the shipped product, because no HTTP status can carry that. Where a stronger signal exists — a repository, a version, a dated revision — this register prefers it, and where one does not, it prints the weaker signal and names it as weak rather than dressing it up.

Where Kasada sits in this catalogue

Kasada is filed in section 04, anti-bot vendors & public documentation, whose scope is this: The detection side, listed by its own public documentation. Where a vendor's marketing host refuses automated clients, the docs host is listed instead and the refusal is recorded. An entry sits in exactly one section here. Where a project could defensibly go in two, it is placed where a reader would look for it first rather than where it fits most tidily, and that is an editorial decision rather than a measured one.

Filed beside it in the same section: HUMAN Security documentation (ACTIVE), Akamai Bot Manager (ACTIVE), Arkose Labs developer docs (ACTIVE). Comparing an entry against its own section-mates is more informative than comparing it against the catalogue as a whole, because everything in a section is answering roughly the same question and the differences left over are the ones that matter.

There is no licence field, because there is no source to licence — this is a documentation rather than a code repository. It is grouped instead with every other entry the rubric marks ACTIVE, which is the axis that actually distinguishes entries of this kind from one another.

What to settle before you adopt Kasada

Its documentation sits behind a portal login, so the public surface is thin by design and that thinness is itself informative. Anything you read about its internals comes from third-party analysis, not from the vendor.