Warppool Ad-free webmonetize with compute, not surveillance
For publishers

Drop your ad network. Ship one tag. Earn from compute.

The ad-tech stack takes 50–70% of every dollar, tracks your readers across the web, and slows your site down with third-party scripts. Warppool is the alternative: one <script> tag, visitors who opt in lend idle GPU cycles, and every millisecond of completed compute earns revenue for your site. No middleman. No tracking. No data leaves the reader's machine.

Get the embed snippet See the consent flow

The web's first viable alternative to selling attention. Free for sites under 1M monthly visitors.

This site is ad-free. Your GPU keeps it that way.

A tiny background task helps fund this site instead of ads. No tracking, no personal data. Stops when you close the tab.

Powered by warppool.tech
No thanks · What is this?
Why switch

Your ad network sells your readers. Warppool borrows their GPUs.

Compute is finite, measurable, and reversible. Attention is none of those. Here's what the switch actually looks like.

!Ad networks (AdSense, programmatic)
  • You keep $0.30 of every ad dollar.Google, Meta, and the SSP/DSP chain take 50–70%.
  • Revenue requires surveillance.third-party scripts, fingerprinting, cookie syncing, real-time bidding.
  • Degrades the reading experience.layout shift, modal overlays, autoplay video, 2–5 second load penalty.
  • Two companies decide who gets paid.Google and Meta control >55% of all digital ad spend.
  • Opaque to everyone.readers don't know who tracks them; publishers don't know what they sold.
✓Warppool compute tag
  • You keep 100% of what you earn.~$0.04/GPU-hour, no middleman, no revenue share to a platform.
  • Zero tracking, zero data collection.one consent panel, plain English, one click to stop.
  • Makes your site faster, not slower.11 KB async script vs. 500 KB+ of ad-tech JavaScript.
  • You choose what compute runs.research grants, your own jobs, a specific sponsor — your call.
  • Fully transparent.visitors can audit exactly which kernel is running on their GPU.
The switch

Remove your ad tags. Add this one line. Ship.

Drop the Warppool tag into your site footer. Delete the AdSense/programmatic scripts. Set a default GPU budget. Optionally restrict to specific job classes (research-grants only, your own jobs only, a particular sponsor).

your-site.html 
<!-- in your <body>, ideally near the end -->
<script
  src="https://warppool.tech/w.js"
  api-key="2835ef562fcdfd84eeb061d9c7e9d1ad"
  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

api-key
Your site's API key in the Warppool dashboard. 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.

Spending your earned credits? You don't have to write WGSL.

Credits your site earns can run your own jobs on the network. Write the kernel as an ordinary annotated Python function and let our open-source py2wgsl package (pip install py2wgsl) compile it to a WGSL compute shader — bindings and all. See how jobs work →

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 task counter. Click for full transparency.

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

The stop

Close the tab and the worker detaches in under one frame. No background process. No persistent state. The Warppool scheduler reassigns any in-flight task to another node.

⏻worker:disconnected
tasks_completed = 14
credits_earned = 0.011 task-h
all clean. thanks.
How the sandbox protects visitors. Workers run inside your browser's sandbox — no filesystem, no network, no persistent state. Full security details in the docs →

Questions?

Consent rates, page performance, GDPR, custom job pools — it's all in the publisher FAQ.

See the publisher FAQ in the docs →
Make the switch

Drop ads today. Start earning from compute.

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

Get the embed tag See it in action

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 →