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.
In development · Pre-launch
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.
- 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
Configurations, not labels
"Playwright" is not a configuration.
WhoScrapes describes automation as a complete, specific stack, and reports the access outcome and detection results for that exact stack.
- Playwright / Chromium 152
- Linux
- HTTP/2
- Residential network
- FR region
- Persistent session
- Standard browser profile