Bot intelligence as an API — not another CDN

Stop wasting infrastructure on unwanted bots.

BotDetect is a server-side bot intelligence API for websites and applications. Send request metadata and receive an explainable 0–10 score, reason, signals and recommendation — without moving your traffic behind another CDN or giving up control of enforcement.

Server-side No CDN migration Explainable decisions Shared reputation
/v1/check
{
  "request_id": "req_7H2K",
  "score": 9,
  "reason": "fakecrawler",
  "action": "block",
  "signals": [
    "googlebot_asn_mismatch",
    "browser_headers_missing",
    "ip_reputation"
  ]
}
RecommendationBlock
9/10
Server-side by designNo CDN lock-inExplainable scoringNetwork reputationWordPress ready
Product

Intelligence your application can use — not a black-box block.

BotDetect separates detection from enforcement. Your backend sends request context, BotDetect evaluates it in real time, and your application decides whether to allow, monitor, challenge or block.

01

Server-side, without a CDN migration

Use BotDetect from your existing stack. Core detection does not require browser JavaScript, a DNS move or putting your application behind another reverse proxy.

02

Explainable decisions

Receive a 0–10 score together with a reason and concrete signals. Understand why a request looks suspicious instead of relying on an opaque yes/no decision.

03

Reputation built across the network

Benefit from shared reputation created from abusive behavior observed across BotDetect nodes and participating customers. Reputation is a signal — not an automatic permanent block.

04

You keep enforcement control

BotDetect recommends an action, but your application owns the final decision. Start in monitor mode, inspect the data and enforce only where it makes sense.

1Collect

Plugin, PHP client or REST integration sends request metadata before expensive application work.

2Score

A regional BotDetect node evaluates headers, crawler identity, ASN, behavior and shared reputation.

3Act

Your application receives the explanation and decides whether to allow, monitor, challenge or block.

Why it pays

Bots are not free traffic.

Unwanted requests consume bandwidth, PHP workers, application CPU, database time, logs, cache capacity and sometimes paid third-party APIs. Tiny per-request costs become real infrastructure spend at scale.

Stop paying server costs for unwanted bots.

Reject suspicious traffic before it reaches expensive application logic whenever your architecture allows it.

Prevent AI scrapers from consuming your content.

Identify automated crawlers and decide whether they should be monitored, challenged or blocked.

Keep fake crawlers out.

Detect clients claiming to be legitimate search crawlers when their network identity and behavior do not match.

Illustrative cost math

Even one hundredth of a euro cent adds up.

If one unwanted request costs only €0.0001 in origin compute, bandwidth, database work and logging, the cost grows quickly.

1 millionrequests€100
10 millionrequests€1,000
50 millionrequests€5,000

Illustrative example only. Actual infrastructure cost per request depends on your application, hosting model, caching and where BotDetect is integrated.

BotDetect in numbers

More than 147 million requests processed in the last month.

The more than 147 million figure is the total request volume processed by BotDetect during the last month. The screenshots below are selected traffic statistics from the dashboard of a real BotDetect customer and show what an individual customer can see in their own dashboard.

147+ millionrequests processed over the last month
24/7continuous scoring and reputation updates
0–10explainable request score with reason and signals
Example real BotDetect customer dashboard showing the last 24 hours of allowed and blocked requests
Example customer dashboard — Last 24 hoursTraffic statistics from the dashboard of a real BotDetect customer, showing hourly requests and allow/block decisions.
Example real BotDetect customer dashboard showing a monthly traffic trend with total, allowed and blocked requests
Example customer dashboard — Monthly traffic trendTraffic statistics from the dashboard of a real BotDetect customer, showing daily request volume and decision trends over the selected month.
Solutions

Use BotDetect where bots cost you money or attention.

Start with a WordPress plugin, call the REST API directly or use shared reputation as an additional security signal in higher-volume environments.

WordPress protection

Protect frontend pages, wp-login.php, XML-RPC, REST API and admin-ajax. Monitor first, see how much traffic is automated, then enable challenge or block modes when you are comfortable.

  • Reduce wasted PHP and database work
  • See fake crawlers and AI scraper activity
  • Protect login and automation-sensitive endpoints
  • Benefit from network reputation
Start with WordPress

REST API

Call BotDetect over HTTPS from any backend stack. Receive score, reason, signals and recommendation while keeping your own application logic and enforcement.

API workflow

Server-side PHP

Use the ready-to-use PHP integration from custom applications and common PHP frameworks without introducing client-side fingerprinting as a requirement.

Server-side workflow

Reputation intelligence

Premium environments can use shared reputation built from observed abuse as an additional signal beyond individual request scoring.

Ask about reputation access
For website owners

WordPress protection is also traffic intelligence.

Blocking is only one outcome. BotDetect helps site owners understand which parts of WordPress attract automation, test protection in monitor mode and reduce unnecessary application work before turning on enforcement.

  • Monitor before you block to reduce false-positive risk
  • See automated activity against login, REST, XML-RPC and frontend paths
  • Identify fake search crawlers and AI scraping behavior
  • Reduce noise in logs and repeated application/database work
  • Use reputation learned from abuse observed elsewhere in the network
Pricing

Monthly capacity that is easy to compare.

Plans are shown as approximate 30-day request capacity. Technical hourly limits remain in place to protect service stability and keep traffic bursts predictable.

Free

€0/month

≈720K requests/month

For testing BotDetect on one website.

  • 1 website
  • API access
  • WordPress plugin
  • Basic dashboard
  • Technical limit: 1,000 requests/hour
Start free

Standard Plus

€100/month

≈86.4 million requests/month

For the same Standard features with higher request capacity.

  • Up to 5 websites
  • API access
  • WordPress plugin
  • Standard dashboard
  • Technical limit: 120,000 requests/hour total
Choose Plus

Premium

Custom

Custom request capacity

For high-volume environments and reputation intelligence use cases.

  • Custom traffic volume
  • API access
  • WordPress plugin
  • Standard dashboard
  • Reputation feed
  • Priority support
Contact sales

Monthly figures are 30-day equivalents of each plan's technical hourly capacity. Limits are enforced hourly; unused hourly capacity does not roll over into another hour.

Trust & operations

Security through clear boundaries and transparent operation.

BotDetect is an independently developed and operated EU-based security service. The project focuses on direct technical ownership, minimal data use and infrastructure controls that are appropriate for a security product.

EU-based control plane

Customer account, service configuration and central control-plane data are managed from EU-based infrastructure. Request metadata is evaluated by geographically distributed BotDetect API nodes to keep scoring latency low.

Payments handled by PayPal

Payment processing is delegated to PayPal. BotDetect does not need to store customer card numbers or process raw card details itself.

Customer data is not an advertising product

BotDetect does not sell customer data or share it for advertising. Operational data is used to provide the service, protect it, build security reputation and support customers.

Actively maintained infrastructure

Hosts and software are kept updated, public exposure is minimized, TLS is used for service traffic, application secrets are separated from public code and internal data services are not intentionally exposed to the Internet.

Founder-operated engineering

The service is currently developed and operated directly by its owner. Technical questions and security issues do not disappear into a multi-layer support chain — they reach the person responsible for the architecture and operations.

Procurement questions welcome

Need an architecture review, data-processing explanation or security questionnaire answered before deployment? Contact the project directly and get a technical response rather than generic sales copy.

BotDetect makes only the security and compliance claims it can substantiate. Formal certifications are not implied by this page.

About

Independent bot intelligence, built from the EU.

BotDetect is designed around one simple idea: you should be able to add bot intelligence to an existing application without moving your traffic behind a new CDN or surrendering enforcement control.

The system combines request-level analysis with crawler verification, behavioral signals and shared reputation. Detection remains explainable, while your application decides what happens next.

Being independently operated keeps the feedback loop short: product development, infrastructure decisions and technical support are connected directly.

Design principles

  • Server-side and API-first
  • Geographically distributed scoring for low latency
  • Monitor-first deployment before enforcement
  • Explainable score, reason and signals
  • Shared reputation without permanent automatic punishment
  • Customer-controlled enforcement
Ready to see your bot traffic?

Start in monitor mode. Block when the data earns your trust.

Connect your first site, observe real decisions and use BotDetect as an intelligence layer before enabling enforcement.