For anyone with a spare machine
Get paid for bandwidth you already have
A process on a machine that stays on. It caches content and serves people near you, and you keep a share of the revenue it generates, up to 25%.
What it pays
You earn a share of the revenue your node generates: up to 25% of what customers pay for the workloads your node delivers. The better your node performs, the more workloads it is selected to run, the more you earn.
Your hardware sets the ceiling. Your machine's CPU, memory and upload speed place it in a tier between 8% and 25%. How well it actually performs then decides how close to that ceiling you get. That's measured automatically from real traffic: uptime, delivery speed and reliability, sustained capacity, and a stable machine. There are no benchmarks to run and nothing to report. You can check your node's performance at any time in the portal and receive tips for improving it.
Consistency beats specs. In the documented examples, a mid-range machine that stays up and serves reliably keeps 20.15% of its revenue, while a faster machine that overheats and restarts keeps 18.90%. An ISP or power outage costs you far less than a preventable crash or a reboot in the middle of a delivery.
Payouts are in U.S. dollars, by ACH direct deposit or to a Visa or Mastercard debit card. Referral (opens in a new tab) and uptime bonuses are paid exclusive of your node's earnings. The full formula, with worked examples, is in the payout documentation (opens in a new tab).
What your machine needs
If it fails the first two rows it will not be accepted. The rest are preferences. These figures are provisional.
| Requirement | Minimum | Status |
|---|---|---|
| Upload bandwidth | 100 Mbps sustained | Required |
| Uptime | 18 h a day, unattended | Required |
| Free disk | 500 GB SSD | Recommended |
| Memory | 2 GB free | Recommended |
| Public IP | Not needed | Not required |
| Port forwarding | Not needed | Not required |
What is actually involved
Run one command
MacOS, Windows, Linux or a NAS. Single binary or Docker. Takes about 90 seconds.
It warms up
For a week it takes a small share while we measure it. Earnings start on day one.
You ignore it
No moderation, no support queue, no traffic you are responsible for.
You can leave
Stop the container. The cache wipes itself and the final month is still paid.
Is this legitimate?
A fair question to ask of anything that offers to pay you for a spare machine. Four answers, each checkable.
You are not a proxy
Your node serves our customers' signed content and nothing else. It cannot be used to route arbitrary traffic through your connection.
You cannot read the cache
Chunks are encrypted and you do not choose what you hold. That also means you are not liable for it, which is the point of the design.
The node agent is open source
Read it before you run it on GitHub (opens in a new tab), with reproducible builds, so the binary matches the source you read.
Network activity is public
You can watch network activity in every Metro Area we serve on the leaderboard (opens in a new tab).
Operator questions
Will this violate my ISP's terms?
This depends on your ISP but CDN traffic is indistinguishable from a Googe Meet call or other WebRTC-based applications.
Does it slow down my own connection?
The node yields to your traffic. It watches your net connection and backs off when you are using it, so your own traffic takes priority.
What are the tax implications?
You'll receive a U.S. 1099 for earnings above $600 for your annual tax return filing.
Can I run more than one node?
Yes, up to three per operator at present. The operator documentation (opens in a new tab) covers setup. Get in touch (opens in a new tab) if you want more and can explain the use case.
See whether your machine qualifies
Six questions, no account, no email address.