Network online · 47 jobs running right now

Your visitors already have GPUs. Stop selling their data.

Warppool is the monetization layer for the ad-free web. Publishers embed one script tag — visitors who opt in lend idle GPU cycles to power research and computation. No tracking, no data brokers, no attention tax. The same revenue, earned by doing useful work instead of selling eyeballs.

Researchers run free. Publishers earn per GPU-millisecond. No middleman takes 50%.

worker @ detecting… checking Warppool support…
π estimate
target π = 3.141592… · error
Samples
0
Hits
0
Throughput
0
Chunks
0 / 64
--:--:--warppool worker-client · v0.3.1
This is a real Monte Carlo job. Hits are aggregated on the GPU; π = 4·hits/samples.
Workers online
0
Compute pooled
184.2TFLOPS FP32
Jobs in flight
47
Sponsor sites
218
Two audiences, one network

Publishers monetize. Researchers compute.

For publishers

Replace ads with compute.

  • One script tag replaces your entire ad stack — 11 KB, async, off the critical path.
  • Visitors opt in to lend idle GPU cycles. You earn per completed millisecond. No middleman takes 50%.
  • Digital advertising is a $680B industry built on surveillance. This is the alternative.
Publisher guide →
For researchers

Free distributed GPU compute.

  • Ship a shader, get results back. Free for anyone with an .edu email — no cap, no waitlist.
  • Every job runs on GPUs that are already manufactured and powered on. No new data center needed.
  • No AWS account, no Kubernetes. The simplest path from “I have a kernel” to “I have a result.”
Submit a job →
What people are running

Real workloads, running right now on the Warppool network.

Climate ensemble forecasts

A weather lab runs 4,000-member regional precipitation ensembles overnight, distributed across volunteer browsers in the same time zone as the model domain.

Type Monte CarloMedian task 2.4 s
See demos →

Batched FastVLM inference

A classroom batches 220k video frames through Apple's open FastVLM model for captioning research. Each task is one frame; tasks stream to whichever idle Warppool device picks them up first.

Type ML inferenceFrames/hour 38,400
See demos →

Hyperparameter sweeps

An ML team sweeps 20k learning-rate × batch-size combinations on a small classifier. Each task is one config × 5 seeds. Warppool returns the best 50.

Type SweepConfigs/run 20,000
See demos →
Trust & verification. Every task is checked by 2–3 independent workers. Canary tasks catch bad actors. The browser sandbox protects visitors. Full details in the docs →
The environmental case

Use the GPUs that already exist.

There are over 1.8 billion GPUs in consumer devices worldwide — laptops, tablets, phones — sitting idle right now. Meanwhile, new data centers consume 2–4% of global electricity and their construction generates thousands of tons of embodied carbon. Warppool puts existing hardware to work instead of building more.

0
New hardware required

Every Warppool job runs on GPUs that are already manufactured, already powered on, and already in someone's hands. No new silicon. No new cooling. No new land.

<2 W
Marginal power per worker

An idle browser tab uses roughly 0.5 W. A Warppool worker raises that by 1–2 W — less than the backlight on most screens. The laptop was on anyway.

100%
Useful work

Unlike proof-of-work mining, every cycle on Warppool does real computation — climate models, ML inference, scientific simulation. Nothing is wasted on hash puzzles.

A single hyperscale data center emits 20,000–50,000 tonnes of CO₂ during construction alone. Every embarrassingly parallel job that runs on Warppool instead is compute that didn't need a new building.
Common questions

Things people ask before dropping their ad network.

Can this actually replace my ad revenue?

For content sites with engaged readers (avg. session >2 minutes), yes. A site with 100k monthly visitors and 50% opt-in rate earns roughly $0.04 per GPU-hour contributed. That works out to comparable or better revenue than programmatic display ads for most niche publishers — and you keep 100% of it instead of 30–50% after the ad network's cut. The math gets better as GPU utilization rates improve and compute demand grows.

Is this just a cryptominer with extra steps?

No — and we built the network specifically to be the opposite. Cryptominers run inside ads, without consent, and benefit the site operator at the visitor's expense. Warppool requires explicit per-session opt-in, surfaces what's running, throttles to background-tab limits, and pays the credit to whoever the visitor authorized. The first thing on every roadmap is making fraud easy to spot.

What does it cost to run a job?

Researchers with verifiable institutional affiliation (university, public lab, school) run free — no cap, just don't be silly with it. Everyone else is billed per millisecond of completed compute: you pay only for tasks that returned a verified result. Failed tasks, timeouts, canary tasks, and redundant re-runs cost nothing. Indicative rate is around $0.04 per GPU-hour. Embed the worker tag on your own site and you earn credits back at the same rate.

How fast is one browser GPU, really?

A mid-range integrated GPU (M-series, recent Intel) returns ~1.5 GFLOPS-equivalent on the Monte Carlo benchmark you see in the hero. A discrete RTX-class card returns 30–80×. Calibration runs on join, so the Warppool scheduler always knows roughly how big a task a given worker can swallow in ~2 seconds.