Showing off Kasada’s edge integration on Fastly

  1. Tell us who you are and what you’ve built!

Kasada has developed a radical approach to defeating automated cyberthreats (bots) based on its unmatched understanding of the human minds behind them. Kasada Bot Defense overcomes the shortcomings of traditional bot management to provide immediate and enduring protection for web, mobile, and API channels. Its invisible, dynamic defenses provide a seamless user experience and eliminate the need for ineffective, annoying CAPTCHAs. Our team handles the bots so clients have freedom to focus on growing their businesses, not defending it.

  1. What problem are you solving?

Businesses that operate in retail, travel, hospitality, media, and financial services are subject to account takeovers, fake account creation, carding, scraping, scalping, and other exploitations of their customers, products, infrastructure and inventory. These bot attacks produce both excess cost as well as revenue loss. They also harm customers, cripple website UX, and overload busy security teams.

The problem has become more challenging to solve because fraudsters have an advantage - solver services readily available online allow anyone to quickly and cheaply bypass CAPTCHAs without much skill required.

Kasada delivers effective protection without impacting the site’s user experience, and with the lowest false positive rates in the industry (i.e. a real customer is almost never wrongly flagged as a bot).

  1. Who are the ideal users for this product?

Large eCommerce and Travel/Hospitality vendors are the ideal customers for Kasada, but bot attacks are likely anywhere there is value and a means to extract it. Value can be access to credit cards, products, loyalty and rewards points, paid accounts and many other variations. Any business with web, mobile, or API-based applications which enable login, registration, payment processing, or share product information are ideal users for Kasada.

  1. How are you using Fastly within the product?

Fastly customers enable Kasada as a web service called directly from Fastly Compute. Kasada becomes an added layer of protection within the Fastly cloud.

  1. How can people get started right now, and what’s a good “hello world” example?

Kasada will run a 30-day “proof concept” trial with production-grade integration and testing to allow any customer to determine the scope and impact of their bot problem. Kasada will provide analysis, monitoring, and mitigation to allow any customer complete confidence in the efficacy of the solution, and reliability within their staging and production environments.

See Kasada’s case study with True Alliance - an umbrella of brands that includes Reebok, Gap, and The North Face. Kasada increased traffic conversion by 60% and reduced false positives (incorrectly flagging real customers as bots) to below 0.01%.

  1. Where can people learn more?

To get started with Kasada, click here

  1. Do you have any screenshots, gifs, or videos that should be embedded in the post?

This is pretty cool @arif, thanks for posting here! Are there specific features within Compute that made building this easier than other platforms?

Alternatively, are there things we should build in the future that would make the development experience even better?

Are there specific features within Compute that made building this easier than other platforms?


  1. The documentation is really great
  2. The dev tooling (CLI, starter projects, etc.) is very smooth
  3. There is a good focus on reusing web-standard functions and objects rather than creating custom ones (e.g. using fetch() for network calls rather than creating custom functions like httpRequest() in Akamai EdgeWorkers that have weird, non-standard function signatures)

Are there things we should build in the future that would make the development experience even better?


  1. Ability to easily assign Compute functions to specific routes on a CDN Service
  2. Ability to edit code in the web interface, rather than requiring customers to have a full development environment set up on their local machine
  3. Ability to use Dynamic Backends without needing to talk to Fastly’s team to enable them
  4. Auto assigning a domain for a Compute Service or making that process smoother somehow
  5. An overall smoother, less convoluted management experience of services would be greatly appreciated