Benchmarks

Every number on this page has a method, a date, and a place to check it. We publish the losses too. A benchmark table that never admits a defeat is an ad.

Anti-detection suite

The Sekreto engine drives a hardened Firefox build on per-session ephemeral workers. Each row is a public detection site or protocol-level check run through the deployed product path, with the verdict captured on disk in the repo's tests/antidetect/evidence/.

CheckResultMethodDate
BrowserScan100% authenticitybrowserscan.net full check through the session; verdict scraped and stored as evidence2026-09
Sannysoftcleanbot.sannysoft.com property battery (webdriver, Chrome plugins, permissions, WebGL vendor); zero failed rows required2026-08
CreepJSpasses machine testscreepjs machine.html battery via the session; lies/worker checks counted2026-08
Pixelscanmasking detectedpixelscan.net fingerprint check; the only detector in the suite that classifies the engine. Our write-up of every eliminated signal: server-side classification of the hardened engine, not a config defect2026-08-23
Cross-tab coherence4/4 tabs one machine identity4 parallel tabs probed through the gateway; UA, WebGL renderer, screen must all return one coherent identity (evidence: tab_coherence/*.json, post-fix run)2026-10-03
TLS fingerprintnative Firefox ClientHelloThe engine is a real Firefox build — its TLS stack presents a genuine (non-spoofed) ClientHello; no JA3 mismatch to detectstructural
HTTP/2nativeServer speaks h2 with the engine's own settings frame; no header-order or pseudo-header synthesisstructural

Verdicts are from the recorded evidence runs above. Detector sites change their pages; the suite can be re-run at any time and the numbers updated with fresh dates. The engine name and its configuration are deliberately not published — the defense would be trivially updated against it.

Stealth bench (web-task success rate)

80-site open benchmark rig (Browser-Use Stealth Bench V1), same task set and judge as the published leaderboard. This is honest-competition ground, and we currently lose it badly.

EntryOverall (80 tasks)
Spider Cloud85%
Browser Use (stealth Chromium)81%
Headful Chromium control49–50%
Headless Chromium control2–3%
Sekreto engine (bare, datacenter egress)10%
Sekreto full product1.25–3.75%

Measured across six full runs (2026-08-28 → 09-04), all raw JSONLs retained and reproducible from the harness's scoring rule. Read-out: the 81–85% band embeds premium curated residential IP supply plus challenge solving that we have not chosen to buy yet; cheap residential did not lift the score (5/80). The fingerprint leg is one leg of three — IP reputation and agent-loop efficiency are the other two. Per the pre-registered publication gate (non-superior ⇒ internal), these numbers are documented here as the honest baseline, not as a headline claim. The negative-result write-up of every filter that did NOT work, with data, is in the repo's docs.

Method

What we run. The detector suite is automated end-to-end through a deployed, paying-customer-shaped session (no operator shortcuts, no hand-tuned test profile) and each verdict is persisted as JSON evidence in the repository — the numbers on this page are the numbers the evidence files record, dated.

What we don't have yet. Latency (p50 search) and fetch-quality (% usable) axes are designed but not published — no verified numbers on disk as of the date above, so the rows read "pending" rather than invented. SimpleQA/BrowseComp augmentation scores are likewise pending the benchmark program.

Where we lose, on purpose in print. Pixelscan classifies the engine; the open 80-site stealth bench has us far behind the 81–85% band. We publish both because a bench page without losses is marketing, not measurement. Every competitor number quoted (85%, 81%, 49–50%, 2–3%) comes from the benchmark's official published leaderboard; our numbers reproduce from our raw runs.