Kasada: the fully managed option, and what you give up for it

Kasada is the clearest expression of one philosophy in this market: you should not have to operate bot defence, so Kasada operates it for you. Whether that is the right answer depends entirely on whether you have someone who wants the job.

What Kasada is

Bot Defense and AI Agent Trust, delivered as a managed service. Headquartered in Australia with major New York operations. The Vercel OEM partnership means some buyers meet Kasada through their hosting platform rather than through a direct evaluation.

Where it leads

Forrester singles out Graph Explorer, a visual mapping of users, devices, IPs and sessions. The value is that account abuse rarely shows up as one bad request. It shows up as a pattern across a campaign, and a graph view finds that faster than a log filter. Forrester also credits Kasada for transparent roadmap communication, which sounds soft but matters when you are betting a checkout flow on a vendor's next two quarters.

Kasada is the right answer for customers who want to offload bot defence day to day. That is Forrester's framing and it is accurate.

Where Forrester identified gaps

Limited UI customisation, and relatively few out-of-the-box marketing and e-commerce integrations. Kasada customers told Forrester that customisation options in the UI are limited.

That is not an oversight. It follows from the managed model. If Kasada's team is running the operation, a deep deep self-serve configuration is something they have to support without benefiting from. The cost falls on the customer who needs to change something during a live incident.

What it costs

Quoted, with the managed service in the bundle rather than priced separately. Kasada calls the bundle a strength and Forrester agrees, particularly next to Netacea's onboarding, platform, support and usage-band structure.

Where data is processed

Australian and US operations. European buyers who must keep processing in the EU should pin down the available regions before the trial. Prosopo confines Protect processing to the EU where that is the requirement, and on the Custom plan can give a customer a dedicated database, keeping their visitors' data separate from every other site's.

How a block gets explained

Kasada does human-readable explanations, and Forrester did not mark them down for it. The constraint is not the quality of the explanation, it is that you are reading an explanation of a decision somebody else's team configured.

Who authors the rules

Kasada. That is the product.

Which buyers Kasada suits

Kasada is the stronger fit if you do not want to staff bot defence at all, if you want one bundle with the service included rather than a line-item SOC, if graph-based account abuse investigation is the specific problem, or if you are already on Vercel and the OEM path removes a procurement step. And it suits a procurement process that needs SOC 2 and ISO 27001 attestations completed today, where Prosopo's ISO 27001 certification is still in progress.

How Prosopo compares

If you have an engineer who wants to write the rule themselves. Prosopo Access Rules match on IP CIDR, ASN, country, User-Agent, headers, JA4 TLS fingerprint and OS, and apply the moment they are saved.

If you want to see exactly why each request was stopped, in the same drill-down view our own engineers use to build the next detector.

Side by side

Full context in the Forrester Wave breakdown.