PUBLIC VALIDATION

Public validation benchmarks and consistency evidence

Review public validation scope, benchmark results, and cross-platform consistency evidence in one place.

Request validation walkthrough Open proof docs

40+ public check scenarios4 supported platforms100+ isolated contextsOne browser model

Public validation scope

Evidence is organized around signal dimensions, runtime paths, and public checks that show how the model stays aligned.

Consistency evidence

The same profile is expected to stay aligned across supported platforms and runtime modes.

Benchmark and rollout depth

The key parts of the browser model remain stable from first validation to scaled deployment.

What this public evidence covers

Validation scope, benchmark coverage, and consistency standards describe the supported operating model.

VALIDATION METHODOLOGY

How the public validation model works

The public proof model is organized around scope, method, reproducible benchmarks, and alignment criteria.

Validated scope

Signal groups, runtime paths, and platform combinations that represent the current public scope.

Validation method

Public checks, reproducible replay methods, and cross-platform runs under the same browser model.

Alignment standard

Stable profile output, no obvious runtime drift, and consistent behavior across the supported rollout path.

40+

Validated scenarios

Public checks plus reproducible validation paths

Supported platforms

Windows, macOS, and Linux hosts plus Android targets

100+

Isolated contexts

Independent runtime model for scaled workloads

Browser model

The same core from first validation to enterprise rollout

PUBLIC BENCHMARKS

Public benchmark evidence under load and scale

Public benchmark results cover both performance pressure and concurrent profile scale.

<1%

Speedometer overhead

Headed and headless runs stayed within run-to-run variance versus stock Chromium.

0ms

Added API latency

Canvas, WebGL, Navigator, Screen, and Font APIs showed no measurable added latency.

29%

Less memory at 50 profiles

Per-context architecture used less memory than launching 50 separate browser instances.

57%

Fewer processes at 50 profiles

Shared browser infrastructure cut process count at the same 50-profile scale.

Benchmarks were run locally across macOS, Linux, and Windows.

Public benchmark runs also include roughly 2x faster profile creation at 50 concurrent profiles.

Benchmark scope, repeatable method, and operating behavior are all documented publicly.

PUBLIC VALIDATION COVERAGE

What public validation covers today

The signal dimensions and runtime paths below are the public evidence areas used to judge whether the model stays aligned.

Signal collection coverage

Public proof includes the browser-facing signal groups most likely to reveal drift or leakage.

CanvasWebGLAudioUA-CH

Tracking correlation coverage

Validation also looks at where browser, network, and storage state start to correlate across runs.

Proxy pathSession continuityStorage stateIP linkage

Runtime parity coverage

The model is checked across runtime modes and host environments where output often starts to drift.

Headless parityGUI parityLinux runtimeAndroid targets

Identity control coverage

The proof surface also includes the layers that matter once the browser becomes part of a larger workflow.

FontsWebRTCGPU pathContext isolation

ANONYMOUS WORKLOAD PATTERNS

Validation paths shaped by real production workloads

The names stay private. The engineering constraints are concrete: stable browser identity, controlled network signals, repeatable runs, and a path from evaluation to scale.

Search and market intelligence

Recurring authorized search-result collection, price monitoring, and regional comparison require stable profiles and consistent proxy-aware browser output.

Compliance and account workflows

Long-running sign-in, form, and review workflows depend on browser, network, storage, and locale signals remaining aligned across runs.

Brand and fraud-protection validation

Defensive teams validate how customer-facing sites respond to browser signals, challenge flows, and cross-device consistency without exposing customer identities.

High-concurrency browser infrastructure

Scaled workloads combine isolated contexts, Linux or headless deployment, repeatable profiles, and resource-aware rollout planning.

CONSISTENCY MODEL

Proof is about keeping the same model stable across checks and rollout stages

The strongest public proof point is that the same browser model stays coherent across platforms and rollout stages.

Same profile across platforms

The product is designed to keep one profile aligned across Windows, macOS, and Linux hosts, while Android targets are simulated from that same model.

Runtime discipline

Proxy paths, isolated contexts, and browser-level control stay part of the same deployment model.

Scale without model drift

The same proof model extends from early validation into long-running and enterprise-oriented deployment stages.

RELATED GUIDES

Guides that support the public validation claims

These guides explain how the checks work and which browser signals matter most when you evaluate consistency.

PlatformJun 1, 2026

Cross-Platform Browser Profiles: One Identity on Every Host

Why a browser profile, not the host operating system, should define browser identity, and how to check that it holds on Windows, macOS, and Linux hosts.

Read guide

FingerprintApr 2, 2026

Client Hints Fingerprinting: HTTP Headers as Identity

Client Hints headers such as sec-ch-ua describe browser brand, version, and platform on every request. Learn where mismatches arise and how to compare headers with JavaScript.

Read guide

FingerprintApr 2, 2026

WebRTC Codec Fingerprinting: Media Capabilities Leak

WebRTC codec enumeration through getCapabilities() and SDP offers exposes hardware-specific media capabilities that differ across operating systems. Learn how codec lists become a platform fingerprint and how to control them.

Read guide

DeploymentMar 26, 2026

Scaling Browser Contexts with Per-Context Profiles

Plan profile-backed browser capacity with measured workloads, bounded queues, clean lifecycles, and explicit isolation requirements.

Read guide

FingerprintApr 25, 2026

Canvas Fingerprinting: How It Works and What Helps

How Canvas rendering differences become a stable device identifier, why VPNs and private browsing leave it unchanged, and how profile-driven deterministic output works.

Read guide

FingerprintApr 25, 2026

WebGL Fingerprinting: GPU Identity and Browser Protection

WebGL can expose GPU identity and rendering behavior. See the browser signal families involved and how profile consistency helps reduce tracking across sessions.

Read guide

Map your target checks to the right public validation path

Match public checks, platform scope, and rollout stage to the right model path.

Request validation walkthrough Open proof docs