WhoScrapes Join waitlist

In development · Pre-launch

Understand web automation
from both sides.

Test access. Measure detection. Audit protection. Research the web automation landscape.

01 Can automation access it? 02 What detects the automation? 03 What gets through your protection?
Join the waitlist Explore the platform

WhoScrapes is currently in development. No product is available yet.

Run Execute complete, tested automation configurations. Labs Measure access and protection coverage. Probe Benchmark your client across protection systems and detection layers. Atlas Research automation and protection technology.

Both sides of the connection

One platform. Two perspectives.

For automation teams

Understand access.

  • Which configurations can access a target?
  • What characteristics make my client detectable?
  • How do browsers, libraries and network stacks compare?
  • Which configuration should I run?
Labs Probe Run

For website owners

Understand exposure.

  • Which types of automation can access my site?
  • What does my current protection detect?
  • Which client classes still get through?
  • Where are my protection gaps?
  • How does my protection stack compare with the wider web?
Probe Labs Atlas

The same benchmark can answer opposite questions depending on which side of the connection you operate.

Automation teams ask: "What detects me?" Website owners ask: "What am I detecting?"

The platform

Four products. One measurement layer.

Each product answers a different question, from either side of the connection. Use one, or use them together. None of them requires the others.

Run Execute a complete, tested configuration consistently.
Labs Experiment with configurations and measure both access outcome and protection coverage.
Probe Benchmark your client across protection systems and detection layers, or test your own site's protection against controlled automation.
Atlas Research the automation and protection technologies used across the web.
Atlas / Inspect Observe which technologies appear to be deployed on a supplied site.
WHOSCRAPES
Atlas Automation + protection intelligence
Labs Compare configurations Test protection coverage
Probe Benchmark across protection systems Measure detection layers
Run Execute known configurations
Each product stands on its own. There is no required order.

Two example paths. Examples only: start anywhere and stop wherever you have your answer.

Automation team
  1. InspectInspect target
  2. AtlasResearch its stack
  3. ProbeProbe my client
  4. LabsCompare configurations
  5. RunRun the chosen one
Website owner
  1. InspectInspect my site
  2. AtlasCompare with the web
  3. ProbeProbe my protection
  4. LabsCoverage testing
  5. RepeatMonitor and re-test

Run

Run configurations that work.

Run will be the execution layer of WhoScrapes: take a tested configuration and run it through a consistent execution environment.

A configuration is more than a library name. "Playwright" says very little about how a request actually looks on the wire. Run treats the whole stack as one versioned unit, so what you tested is what you execute.

Use a configuration discovered in Labs, one you've built yourself, or a known stack you simply want to execute consistently.

Run is execution infrastructure. It is designed to be used on its own, without Labs, Probe or Atlas.

Explore Run
configuration =
  • engineBrowser or HTTP engine
  • versionExact engine and library versions
  • launchLaunch flags and runtime options
  • networkTLS, HTTP/2 and HTTP/3 stack
  • headersHeader order, values and Client Hints
  • fingerprintBrowser fingerprint and profile
  • egressProxy and network configuration
  • sessionCookies and persisted session state
  • navigationNavigation and pacing strategy
  • runtimeOther environment settings

Labs

Find out what works.

Labs will be a controlled experimentation environment. It runs many complete configurations under the same conditions and records how each one behaves: the access outcome on one side, the protection outcome on the other.

  • For automation teamsConfiguration compatibility: which configurations reach the intended content, and which change affected the result.
  • For site ownersProtection coverage: with proof of ownership, which classes of automation can still access my site.
Explore Labs
01 Target https://target.example/
02 10–100 configurations
03 Controlled benchmark Same target, same conditions, repeated runs
04 Outcomes Access and protection, per configuration

Probe

See what sees your bot.Or see what your protection misses.

Probe is being built as a benchmarking layer across the bot-protection ecosystem. The goal is not a single generic "bot score": Probe will show how the same client is classified across real protection systems, signal families and network-intelligence sources.

  • Real products + detectorsBenchmark against commercial protection systems wherever direct integration or controlled environments are available, alongside independent detectors that explain the outcome.
  • Test my client · Test my sitePoint your own scraper, browser or agent at Probe, or benchmark a domain you own with controlled automation classes.
  • Every result labeledNative · Controlled · Implemented · Modeled · Observed. Native and Controlled are real-product benchmarks.
Explore Probe
probe · client report Illustrative · not real data
Protection systems
Protection AnativePASS
Protection BcontrolledCHALLENGED
Protection CcontrolledBLOCKED
Detection layers
TLS / transportimplementedPASS
Browser automationmodeledDETECTED
CDP instrumentationimplementedDETECTED
IP reputationimplementedPASS

Atlas

Map the automation and protection landscape.

Atlas will be the research and intelligence layer of WhoScrapes. It catalogs both sides: what protection the web uses, what automation stacks exist, and how the two interact.

  • Protection intelligenceAnti-bot vendors, WAFs, challenge systems, fingerprinting, device and IP intelligence, open-source detectors.
  • Automation intelligenceBrowser automation and HTTP libraries, crawling frameworks, browser infrastructure, AI agents and crawlers.
  • Evidence levelsVerified Observed Inferred Unknown

Inspect observes. Probe tests.

Explore Atlas
inspect example.com Concept · not a live service
Infrastructure
Edge / CDN · CloudflareHigh confidence
Protection
Bot protection · DataDomeObserved
Client-side fingerprintingObserved
Rate limiting · possibleInferred
Automation surface
Known crawler handlingObserved
Crawler authenticationUnknown

Why WhoScrapes

Most tools look at one side.

Most tools measure one side of the connection. WhoScrapes is designed to measure the interaction between them.

Automation Can I access the site?
WhoScrapes Measures the interaction.
Protection Can I identify or stop the automation?

Transparent diagnostics

Move beyond PASS, BLOCKED, and generic bot scores. The goal is a per-layer explanation, readable from either side.

Typical result
BLOCKED
WhoScrapes result Illustrative
TransportPASS
Browser consistencyFAIL
Automation artifactsFAIL
IP reputationPASS
BehaviorPASS

Cross-vendor benchmarking

Anti-bot products do not classify every client the same way. Probe is intended to compare real protection systems, independent detectors and network-intelligence providers using the same automation configuration.

Access + exposure

Understand both successful automation and successful protection, from the same measurements.

Reproducible benchmarking

Repeat the same client and protection tests under the same conditions, and compare changes over time.

Neutral research

Atlas studies automation technology and protection technology with the same evidence standards.

Who it's for

Built for teams on both sides of web automation.

WhoScrapes is about benchmarking, interoperability, observability and research into web automation and web protection.

Automation

  • Scraping infrastructure companies
  • Browser automation platforms
  • Data providers
  • Search and indexing companies
  • AI agent developers
  • SEO and data intelligence platforms
  • Proxy and network providers
  • Crawler developers
  • Teams maintaining browser automation

Protection

  • Website owners
  • Ecommerce platforms
  • Marketplaces
  • Publishers
  • Security engineering teams
  • Bot-management vendors
  • WAF and security providers
  • Fraud and risk teams
  • Infrastructure and CDN teams
  • QA and resilience teams

About

An engineering and research platform.

WhoScrapes is an engineering and research platform for understanding the interaction between automated clients and web protection. Automation teams can measure access and detection. Site owners can measure protection coverage and exposure. Atlas researches the technologies used by both sides.

WhoScrapes is not a proxy service and not a CAPTCHA-solving product. Active testing of third-party sites is not the purpose of the defensive testing workflow; site-owner protection testing requires ownership or authorization.

Nothing on this page is available yet. Examples are illustrative, and we will publish real results only when they are real.

In development

WhoScrapes is being built now.

We're building the first version of Run, Labs, Probe, and Atlas. Join the waitlist if you build web automation, operate protection infrastructure, or want to understand how the two interact.

We'll only email you about WhoScrapes early access. No spam.

I work primarily on optional
Primary interest optional