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.

Join the waitlist

In development · Pre-launch

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

For automation teams

Configuration compatibility

Labs explores combinations of browser engines, HTTP stacks, runtime settings, network types, sessions and other configuration components to understand which configurations behave differently against a target.

  • Which configurations reach the intended content?
  • Which browser/library combinations behave differently?
  • Which configuration change affected the result?
  • Is the failure associated with networking, browser behavior, session state or another layer?
PlaywrightPuppeteerSeleniumChromiumFirefoxWebKitMobile browsersHTTP clientsTLS / network stacksProxy typesHeadersBrowser configurationsSession strategiesOther libraries & techniques

For site owners

Protection coverage

With proof of ownership or explicit authorization, Labs can invert the same experiment as synthetic automation testing: which classes of automation can still access my site?

Plain HTTP clientsBrowser automationDifferent browser enginesDatacenter networkingResidential networkingPersistent sessionsRotating sessionsTransport fingerprintsRuntime characteristics
labs · protection coverage Illustrative · mock data
Automation class
Basic HTTP clientBLOCKED
Default browser automationBLOCKED
Persistent browser sessionBLOCKED
Residential browser clientALLOWED
Rotating session clientALLOWED
Potential gaps
Network / identity correlationWEAK
Session continuity analysisWEAK
Browser automation detectionSTRONG
Datacenter reputationSTRONG

requires Domain verification (DNS TXT record, HTTP verification file, or an account-level ownership workflow). Reports describe automation classes and protection coverage, not site-specific techniques.