Standardize egress for dozens of seats: regional gateways, named upstream pools, chargeback, and offboarding. This is an operating model on top of joyproxy-server — not a different binary and not a scraping tutorial.
Deploy gateways, attach business or residential pools, keep tokens off laptops. Individual Multi installs are for exceptions, not the standard image.
One approved path for research teams.
Seat-to-port maps.
GB by cost center.
Regional pools per office.
If every analyst buys their own pack, you do not have an enterprise deployment — you have a mess. Centralize or do not use this page.
Cannot allocate GB.
Unknown owners.
Policy violations.
Unapproved.
Unsupportable.
Overkill for browser research.
Recommended: joyproxy-server per region. Alternative upstream packaging: business custom / residential custom pools. MCP may watch balances — read-only.
| Product | Billing | Use it when… |
|---|---|---|
| joyproxy-server (team) Recommended | Self-hosted · team ops | Recommended — regional joyproxy-server gateways. |
| Business / ISP · Custom | Per port / period | Typical upstream — business custom pools mapped to teams or sites. |
EU gateway exits EU, etc.
Do not build this yet.
No — joyproxy-server plus process.
Per deployment guide.
Gateway on-prem; upstream typically JoyProxy cloud.
You design the architecture; we provide egress.
Still pick residential vs API per job — this page is how people connect.
One binary, pooled upstream, named owners. Skip this if you only have a couple of laptops.