Your login and checkout draw scripts as well as shoppers. Blocking it shouldn’t block your crawlers or customers — Akamai Bot Manager scores every request from 0 for a human to 100 for a bot on Akamai’s edge, then slows, blocks or quietly misleads the automation you do not want — and lets the crawlers you do want through.
Buy through TechBag
Same software. Better outcome — at a lower cost.
How it’s rated
Full scoreboard ↓Quick answer
This page covers Akamai Bot Manager — bot detection and response; Account Protector includes all of it and adds account risk. The rest:
Most product pages skip this. We start here — so you buy a capability, not a buzzword.
It decides whether each request comes from a person or a program, then treats wanted bots, bad bots and humans differently.
What consolidation actually replaces, dimension by dimension.
| Dimension | Rate limits and IP blocklists | Akamai Bot Manager |
|---|---|---|
| How bots are found | Rate limits and IP blocklists | Behaviour, fingerprint and directory signals |
| What a request gets | Allowed or blocked | A Bot Score from 0 to 100 |
| Wanted crawlers | Caught in the same blocklist | Named in a known-bot directory |
| Response to a scraper | A block it notices and evades | Slowed down or a stealth reply |
| Tuning per page | One threshold for the whole site | Cautious, Strict or Aggressive per use |
| What it is NOT | — | Account takeover scoring, a WAF, or a published price |
The cheapest test is one page: watch Bot Scores on your login or checkout for two weeks before you enforce anything.
Vendors love diagrams; buyers need to know what they’re actually operating. Here’s the whole platform, demystified.
Bot Manager runs on Akamai’s edge platform, so a request is scored before it reaches your origin; Akamai’s own explainer is titled thwarting attacks at the edge.
AI models study how a visitor behaves and fingerprint the browser it claims to be, catching automation that rotates addresses and copies real user agents.
A directory of known bots, with custom categories you add, separates search crawlers and partner tools you want from scrapers and resellers you do not.
Each request carries a Bot Score from 0 to 100; a Cautious, Strict or Aggressive strategy decides whether it passes, is slowed, or gets a stealth reply.
A Bot Score on every request at Akamai’s edge — behaviour, fingerprints and a known-bot directory in, a chosen strategy out.
Akamai Bot Manager scores every request for automation and answers each bot the way you choose.
Each request is rated from 0 (human) to 100 (bot), so rules can treat a borderline visitor unlike an obvious script.
AI models analyse user behaviour across a session, the signal a headless script finds hardest to fake for long.
Browser fingerprinting checks whether the client matches the browser it claims, exposing tools that only borrow a user agent.
A maintained directory identifies known bots, so search engines and monitoring services are recognised rather than guessed at.
Custom categories hold the bots only you know about, such as a price-comparison partner or an internal uptime checker.
Akamai says it sees more than 40 billion bots a day across its platform, the pool its models learn from.
Three preset response strategies set how hard Bot Manager leans on a score, so a login can be stricter than a blog.
Rather than block outright, Bot Manager can slow a bot down, raising the cost of each page it scrapes or each seat it hoards.
Stealth responses go beyond block or allow, so an operator is not told at once that the bot has been spotted and should retool.
Akamai on stopping bots at the edge, detecting and managing automated traffic, and stopping bad bots. All from Akamai’s official channel, uploaded in 2020.
Akamai’s case for stopping bots at the edge. Uploaded in 2020; any analyst report it cites is out of date.
Akamai on spotting automated traffic and deciding how to manage it. Uploaded in 2020.
A short Akamai primer on stopping bad bots. Uploaded in 2020, so check today’s features in the demo.
Want a live, India-context walkthrough for your environment?
Book a guided demo →Here’s what genuinely sets it apart — and exactly where it stops.
Bot Manager rates each request from 0, a human, to 100, a bot, instead of sorting traffic into two bins. A checkout can act on a lower score than a listing page, and you can watch scores before enforcing. Behaviour models and browser fingerprints feed it.
A plain block teaches an operator to change tools. Bot Manager can instead slow a bot or send a stealth response, and three strategies, Cautious, Strict and Aggressive, set how hard it leans, making scraping and hoarding slow and unrewarding.
Search crawlers, monitors and partners need through. A known-bot directory names them, and custom categories cover the ones only you know. Akamai says it sees more than 40 billion bots a day, the pool its directory and models draw on.
No public price and no trial, only a demo. It judges automation, not account risk: that is Account Protector, which includes all of Bot Manager. No India-only processing is documented, and its videos on Akamai’s channel date from 2020.
List logins, checkouts, search, inventory and pricing endpoints, with the abuse each sees and who owns the fix.
Walk through scoring and strategies with Akamai, and get the licence basis and term in writing, since none is public.
Turn on Bot Manager in a monitoring posture and review Bot Scores page by page against your known traffic patterns.
Confirm search crawlers in the directory, add custom categories for partners and checkers, then pick a strategy per page.
Switch high-risk pages to slow-down or stealth responses, track conversion and complaints, and revisit strategies each month.
Modelled on Gartner Peer Insights structure. *Counts and breakdowns are illustrative pending verified review collection.
“Sneaker-drop bots used to empty our stock in a minute. Slowing them, rather than blocking, stopped them retooling every week.”
“We ran in monitor mode for a month and watched Bot Scores per page before enforcing anything at checkout.”
“Fare scrapers were costing us in search API calls. The known-bot directory kept the metasearch partners we want flowing.”
“Custom categories let us tag our own uptime checker and a reseller feed, which ended the false alarms on night shifts.”
“Strict on login and Cautious on content pages was the split that worked; Aggressive everywhere annoyed real users.”
“It works, but there is no trial and the quote cycle was long. Budget for the demo and a pilot before you commit.”
Analyst firms bury this view behind paywalls, and G2 retired its Grid. So here’s TechBag’s synthesis of the bot management market — tap any vendor to see why it sits where it does.
Execution strength vs product vision — the classic market map, minus the paywall.
Quote-only; free demo, no trial mentioned.
The grid nobody publishes — how many delivery stacks the bot layer can sit in front of vs how many kinds of signal it uses to tell a bot from a person.
Behaviour, fingerprints, directory; Akamai edge only.
Positions are TechBag’s illustrative synthesis of public review-platform data and vendor documentation — not a reproduction of any analyst graphic. Verify before relying on it.
Against Cloudflare Bot Management, AWS WAF Bot Control, DataDome Bot Protect, Imperva Advanced Bot Protection and HUMAN Bot Defender — on deployment, detection, scoring, responses, price, India data and exit.
| Dimension | Akamai Bot Manager | Cloudflare Bot Management | AWS WAF Bot Control | DataDome Bot Protect | Imperva Advanced Bot Protection | HUMAN Bot Defender |
|---|---|---|---|---|---|---|
| What it is | Standalone bot SKU | Enterprise add-on | Managed WAF rule group | Specialist bot SaaS | Bot module of Imperva | Module of HUMAN platform |
| Deployment | Akamai edge | Cloudflare proxy | AWS resources only | 80+ integrations | Cloud or connectors | SaaS |
| Detection signals | Behaviour + fingerprint | Heuristics, ML, JS | Static, then Targeted | AI on every request | 200+ device attributes | Signals not itemised |
| Scoring | 0 human to 100 bot | 1 bot to 99 human | Labels, not a score | Scale not published | Reports, 100+ fields | Not published |
| Response options | 3 strategies, slow-down | Block, challenge, maze | Block, CAPTCHA, silent | Real-time blocking | Five response types | Actions not listed |
| Wanted bots and AI | Known-bot directory | Verified bots, robots | Verified bots allowed | Agent Trust listing | Human, good, bad | Not itemised |
| Pricing model | Quote; unit unknown | Plan or add-on | Per ACL + per request | Annual, by volume | Quote; FlexProtect | Per module contract |
| Published entry price | Not published | Pro ~$20/site/mo | $10/mo + $1/M | $45,960 a year | No list price | $7,800 a month |
| Included vs add-on | Own SKU; AP superset | Free tier is basic | WAF billed on top | Overage past tier | Part of one stack | Modules priced apart |
| Telemetry scale | 40B+ bots a day | 330+ cities | Your own baseline | 5T signals a day | Global network data | 20T+ a week |
| India data | Not documented | India DLS region | Mumbai or Hyderabad | Not published | Not stated | Not in the listing |
| Support | Terms not published | Onboarding included | Paid AWS plan | 24/7 SOC coverage | Bot analyst team | Self or managed |
| Lock-in and exit | Tied to the edge | Tied to the proxy | Tied to AWS | CDN-neutral | Connectors travel | Monthly terms |
| Best fit | Akamai-fronted sites | Cloudflare customers | AWS-hosted apps | Multi-CDN estates | Imperva or Thales shops | Fraud-led programmes |
Honest fit signals — because the fastest way to lose your trust is to pretend one product wins every scenario.
TechBag has no bot management guide yet, so Akamai Bot Manager sits outside the category guides. Browse all products to compare it with the rest of the catalogue. →
Drag the sliders (bot-exposed endpoints; security engineer-hour cost). Estimates model time spent writing rate limits and blocklists, chasing scrapers and cleaning up after hoarding or fake sign-ups at an assumed 1.5 hours per endpoint a year, with 70% of it removed by scored detection and preset responses. Both figures are assumptions. Illustrative.
Loaded cost = salary + overheads per productive hour. Illustrative only — your TechBag quote models your actual environment and modules.
Quote only. Akamai publishes no price and no licensing unit for Bot Manager, and its product page offers a free demo but mentions no trial. Account Protector, a separate quote, includes all of Bot Manager’s capabilities and adds account risk scoring, so price both if account takeover is on the list. TechBag maps the pages bots target first, then gets the quote itemised in INR with GST.
Best for scraping, hoarding and automated abuse
Best for a broader rollout
Best when account takeover is the main risk
Whatever the list prices above, TechBag negotiates a significantly better deal — with GST-compliant INR invoicing and local support. Ask us for your discounted quote.
Tell us your requirements and current tools — we’ll model it against what you spend today.
Take this into your next vendor call — including ours.
Is the site already delivered through Akamai? Bot Manager scores at the edge, so traffic must pass through it.
Which endpoints face scraping, hoarding, carding or fake sign-ups, and what does each incident cost today?
Is account takeover the main worry? If so, price Account Protector, which includes all of Bot Manager.
Which crawlers, partners and monitors must pass, and are they in the directory or a custom category?
Which pages warrant Strict or Aggressive, and which should stay Cautious to protect real users?
Where would slowing a bot or a stealth reply beat a block, and who watches the effect on conversion?
Does your regulator need bot telemetry kept in India? Akamai documents no in-country processing for it.
What unit is the quote based on, what term, and is it itemised in INR with GST beside any App & API Protector deal?
List the pages bots hit hardest first, or let a TechBag advisor arrange the Akamai demo, run scores in monitoring and get the quote itemised in INR.
Stats, ratings, review counts and pricing are illustrative and sourced from public materials; verify before purchase.