Amaya Labs01

Amaya Labs

Infrastructure forautonomous influence.

Already serving ≈50K billed Google SERP requests daily against one of the internet's most sophisticated automation defenses.

23 July 20261 / 13

Amaya Labs02

How the pieces fit together

Google SERP is the first paid workload on Amaya's automation platform.

Owned platformHardware-to-network control

Device identityAndroid runtime + native inputChromium + retained session stateNetwork egressFleet scheduling + recovery

Production workloadGoogle SERP API

≈50Kbilled requests/day99.31%recent completion$0.075estimated COGS / 1K

Account-network foundationPersistent operation under active defenses

The same identity, routing, scheduling and recovery primitives extend to account creation, incubation and coordinated native/browser operation.

23 July 20262 / 13

Amaya Labs03

The adversarial boundary

Platforms deliberately resist automation at scale.

Official APIs expose sanctioned actions. Everything beyond them is defended by systems scoring device integrity, interaction, browser state and network reputation.

23 July 20263 / 13

Amaya Labs04

Owned stack

Control reaches below the automation layer.

Custom Chromium, Android input, browser identity, network routing, provisioning, health and recovery operate as one system.

23 July 20264 / 13

Amaya Labs05

Execution tiers

Trust, density and elasticity require different runtimes.

Physical Android

Hardware-backed trust and native-app fidelity.

Persistent containers

Long-lived state at high device density.

GPU passthrough

Hardware-faithful rendering for WebGL fingerprinting, renderer integrity checks and client-side proof-of-work.

23 July 20265 / 13

Amaya Labs06

Inside one billed request

A search crosses every layer we own.

01Atomic admissionhealth-weighted Valkey slot

02Per-boot trustpinned worker TLS identity

03Android isolationfail-closed TUN · control out of band

04Browser continuityStoragePartition · NetworkContext

05Structured outputbrowser-native AX · external URLs

3.47sbrowser p50

46 KBproxy data / request

99.31%request completion

$0.075estimated COGS / 1K

23 July 20266 / 13

Amaya Labs07

Paid usage

A paying customer has consumed 452,383 searches.

16active usage days

8.51×daily growth · Jul 11–18

1.4M30-day request run rate

23 July 20267 / 13

Amaya Labs08

Daily production

134 → 50,851requests / day.

440,602billed requests in the preserved daily series

10–23 July · zero-baseline scale

134Jul 10

5.9KJul 11

19KJul 12

20.3KJul 13

21.7KJul 14

25.8KJul 15

26.1KJul 16

31.8KJul 17

50.6KJul 18

41.1KJul 19

43.7KJul 20

52.3KJul 21

51.3KJul 22

50.9KJul 23

23 July 20268 / 13

Amaya Labs09

Production learning curve

8.6× more daily volume.Failure fell from 49.55% to 0.51%.

11 July5,948requests · 50.45% complete

19 July79.84%challenge regime changed

22 July51,335requests · 99.49% complete

Paid traffic became revenue, telemetry and operating knowledge.

23 July 20269 / 13

Amaya Labs10

Production quality

99.31%

request-level completion across the latest 102,186 billed requests

10.43sp50 end-to-end

13.22sp95 end-to-end

23 July 202610 / 13

Amaya Labs11

Unit economics

Owned infrastructure sustains low prices.

90%estimated gross margin

$0.075estimated total COGS / 1K

$0.75Amaya price / 1K

$1.50Bright Data PAYG / 1K

$3.75SerpApi at 1M / 1K

One supporting signal: 46 KB proxy data per request versus 104 KB in the founder Bright Data comparison.

23 July 202611 / 13

Amaya Labs12

Building next

Account creation and coordinated social operation.

Acquisition, state incubation and persistent account operation extend the device platform already serving SERP.

23 July 202612 / 13

Amaya Labs13

What capital builds

The influence machine.

More intelligence aboveAI reasoning, creative generation and adaptive interaction

Execution layer already builtChromium · Android · network · orchestration

More trust belowBoard-level physical Android for hardware-backed actions at scale

Search maps attention.Persistent account networks move it.

23 July 202613 / 13