Run joyproxy-server on Linux or Windows and give your team one controlled HTTP/SOCKS5 gateway. Connect JoyProxy residential or business upstreams without putting cloud credentials on every laptop.
This is the server-side gateway. For per-process routing on one PC, use the desktop client; for per-app routing on phones, use Android Client.
One approved egress.
Point all scrapers at an internal gateway.
Staff laptops should not each hold cloud passwords.
Self-host instead of system-wide VPN.
joyproxy-server is the box. Upstream IPs are a separate purchase. JoyProxy Multi is per-process on one PC — not a team gateway.
Every laptop configured differently.
Leaks.
A part-time job.
Cannot change upstream without touching clients.
Finance cannot allocate GB.
The gateway does not fetch pages. It forwards TCP.
Recommended: joyproxy-server. Alternative upstream: Residential Proxies for mixed browsing/scraping, or ISP Proxies · Static Dedicated if the gateway exists only for SaaS allowlists.
| Product | Billing | Use It When… |
|---|---|---|
| JoyProxy-Server Gateway Recommended for This Workflow | Open Source · Self-Hosted | Recommended — self-hosted HTTP/SOCKS5 gateway. |
| Residential Proxies | Pay per GB | Typical upstream — team sharing Residential Proxies through the gateway. |
One box, whole team.
Do not deploy a gateway.
The software is. Upstream traffic is billed.
See Product Page / Releases.
Enterprise is the operating model (pools, chargeback). The binary is still joyproxy-server.
No. Forward proxy only.
Yes — GitHub.
Install joyproxy-server, then buy the single upstream pack that matches the team’s job.