Warppool Public GPU networkbrowser-native compute
For site owners

Stop selling readers. Lend their GPUs instead.

Trackers, ad networks, and "consent" modals exist because the bargain is bad: someone is paying for the content, and it's not the reader. Warppool changes the bargain. Visitors who opt in share a few seconds of GPU compute while they read; that compute funds research grants and pays for your hosting. No third-party scripts. No data brokers. One <script> tag.

Get the embed snippet See the consent flow

218 sites are running the tag today. Largest contributor sent 3.4 GPU-days last week.

What a visitor sees
This site asks to use a sliver of your GPU.

While you read, your browser would run small chunks of a researcher's compute job (like a weather lab's ensemble forecast). It uses ~3% of your GPU and stops when you close the tab. No ads, no trackers, no data leaves your machine.

running  monte_carlo_ensemble
submitted by  nrlmry-sponsor-pool
budget  3% GPU · idle priority
duration  while tab is open
What is this?
Powered by warppool.tech
The argument

Compute is a fairer thing to ask a reader for than attention.

Every interesting business model for the open web has been compromised by what it asks of readers. Compute is finite, measurable, and reversible. Attention is none of those.

!Programmatic advertising
  • Pays you in pennies per thousand impressions.after the ad network's 50–70% take.
  • Funds itself by tracking the reader.third-party scripts, fingerprinting, cookie syncing, real-time bidding.
  • Degrades the reading experience.layout shift, modal overlays, autoplay video, performance tax.
  • Concentrates power.two or three companies decide what content is monetizable.
  • Opaque to everyone.readers don't know who's paying for what; advertisers don't know what they bought.
✓Volunteer compute
  • Pays you per completed millisecond.roughly $0.04 per GPU-hour earned. No middle, no cut.
  • The reader gets to see and decide.one panel, plain English, one click to stop.
  • Bounded resource use.3% GPU default, idle priority, throttled in background tabs.
  • One research pool, public ledger.research-grant jobs are visible to every contributor.
  • Readable by humans.any visitor can audit the kernel running on their device.
The embed

One script tag. One config. Done.

Drop the tag into your site footer. Set a default budget. Optionally restrict to specific job classes (research-grants only, your own jobs only, a particular sponsor). Ship.

your-site.html 
<!-- in your <body>, ideally near the end -->
<script
  src="https://warppool.tech/w.js"
  data-site="acme-news"
  data-budget="3"
  data-priority="idle"
  data-jobs="research-grants,acme"
  async
></script>

<!-- defaults to a consent strip in the corner;
     swap for inline placement: -->
<div id="warppool-consent"></div>

What each attribute does

data-site
Your site's slug in the Warppool ledger. Credits accrue here.
data-budget
GPU percentage cap (1–25). Defaults to 3. The worker measures real utilization and backs off.
data-priority
idle only runs when the visitor isn't actively interacting. active runs continuously. visible-only pauses in background tabs.
data-jobs
Comma-separated whitelist of job classes. research-grants is the default pool. Add your site's slug to spend earned credits on your own jobs.
Default behaviour

Contributing to the research-grants pool. No data, no tracking, no third parties. The script weighs 11 KB gzipped and loads off the critical path.

Visitor experience

What your readers actually see and feel.

Three moments: the ask, the running state, the stop. The default consent strip is dismissible, doesn't block content, and never reappears once a visitor decides.

Moment 01 · First visit

The ask

Small panel in the lower-right. Plain English. Three buttons.

Share a sliver of your GPU?
This site uses ~3% of your GPU to help run a research weather model. Stops the moment you close the tab.
Details
Moment 02 · While reading

The running state

A 24px badge in the footer. Live chunk counter. Click for full transparency.

Contributing pause
chunks done 14
GPU load 2.8%
elapsed 4m 12s
job weather-l63
Moment 03 · Leaving

The stop

Close the tab → worker detaches in under one frame. No background process. No persistent state. Coordinator reassigns any in-flight chunk to another node.

⏻worker:disconnected
chunks_completed = 14
credits_earned = 0.011 chunk-h
all clean. thanks.
Why this is safe

What a Warppool worker can and cannot do.

The protections come from the browser, not from us trusting kernels. Same security model as any WebGPU site — the kernel sees only the buffer you bound to it, runs only the operations WGSL allows, and stops when the tab does.

What it can do

Operations the worker is allowed to perform.

  • Receive a chunk parameter blob over WebSocket from the coordinator.
  • Compile a WGSL kernel inside the browser's WebGPU sandbox.
  • Dispatch compute workgroups, read back a bounded result buffer.
  • Report the result and a chunk-runtime timestamp.
  • Heartbeat the coordinator so it knows the worker is alive.
What it can't do

Things the browser sandbox makes impossible.

  • Touch the filesystem, clipboard, microphone, camera, location.
  • See other tabs, the host's other GPU buffers, or system memory.
  • Open arbitrary network connections (only the coordinator endpoint).
  • Persist anything across a tab close.
  • Exceed its declared memory or wall-clock budget — the worker stops itself.
Site-owner dashboard

Watch your site contribute, in real time.

A live count of consenting visitors, chunks completed, credits earned, and how those credits are being spent. Plus a public-facing "what we sponsor" page you can link from your footer.

Visitors helping now
218
of 412 consenting today (53%)
Chunks this week
94,210
↑ 18% vs last week
Credits earned
142.3 chunk-h
≈ $5.69 / mo at current rate
Currently sponsoring
NRL ensemble forecast
+ 2 other research jobs

Contribution timeline · last 24h

00:0006:0012:0018:00now

Top contributing devices

Apple M-series38%
NVIDIA discrete31%
Intel Iris / Arc18%
AMD Radeon9%
Other4%
Site-owner FAQ

Before you ship the tag.

Will visitors actually opt in?

Sites running the tag today see consent rates of 45–65% — higher than any cookie banner, lower than no banner at all. It helps that the ask is small and the reward is legible ("we fund research grants") rather than "we sell your data." We publish anonymized aggregate consent stats by category so you can benchmark.

Does it hurt page performance?

The script weighs 11 KB gzipped, loads async, and doesn't run a kernel until consent is granted and the page has been idle for at least 4 seconds. By default the worker uses 3% GPU on a 16ms budget — well below the threshold where users notice. We publish a Core Web Vitals impact report monthly.

What about visitors on phones or slow devices?

The worker only attaches if the device's calibration benchmark clears a minimum threshold (roughly: modern phone or anything with discrete graphics). Slow devices never see the consent strip. Battery-powered devices that aren't on AC get a lower default budget.

Is it legal under GDPR / CCPA / DSA?

The tag collects no personal data and processes no identifiable signals — so the regulations that apply to ad networks don't apply here. We still surface a one-click stop and a transparency page because that's the right thing to do, not because the law forces it.

Can I run jobs from my own site, paid by my own visitors?

Yes. Add your site's slug to data-jobs and submit jobs through your account; credits earned and credits spent net out on the same ledger. This is how a research blog, for example, can pay for its own simulation runs out of reader contributions.

What stops a malicious site from impersonating a Warppool tag?

The tag's behavior is verifiable on a per-page basis at warppool.tech/verify?site=<you>. The script is served from one origin only, source-pinned via Subresource Integrity, and the worker refuses to attach without a valid coordinator handshake.

Ship it

Reserve your site slug and start contributing.

Free for any site under 1M monthly visitors. Above that, talk to us — we'll set up dedicated coordinator capacity in a region close to your readers.

Get the embed tag Read the threat model

Sites running the worker tag

news.commons.org3.4 GPU-days / wk
opensci-quarterly2.1 GPU-days / wk
archive.everywhere1.9 GPU-days / wk
plain-text-magazine1.2 GPU-days / wk
+ 214 moreSee all →