Several people collecting public web data, one JoyProxy account, regional endpoints, revocable tokens. This is not a VPN, not an office intranet tunnel, and not the Remote Work SaaS page.
Recommended: one rotating residential pack with per-person or per-region extract URLs. Optional: joyproxy-server as a single office hop. SaaS allowlists belong on Remote Work (business static).
Contractors in different countries, one bill.
No scraper farm yet — laptops plus shared endpoints.
Regional staff pulling local pages without home-IP bans.
Need to revoke a person without rotating everyone’s password.
Remote Work (solution-remote.html) is for logging into HR and vendor SaaS on a stable business IP. This page is for public collection jobs shared across a team.
Each analyst crawls from home and gets blocked.
One shared proxy user for twelve people.
Someone abroad still needs home-market pages.
Corp VPN and scraper proxy fight on the same laptop.
Nobody knows which job burned yesterday’s GB.
Ex-contractor still has the endpoint.
Recommended: rotating residential on a shared account with separate authorizations. Alternative: joyproxy-server if the office wants one local SOCKS hop. Do not buy static business IPs here — that is Remote Work.
| Product | Billing | Use it when… |
|---|---|---|
| Residential · Rotating Recommended | Pay per GB | Recommended — shared GB pack, regional extract URLs, revocable auth. |
| Web Scraping API | Credits · pay per success | Alternative — centralize hard pages so laptops never run Chrome. |
One bill, many extract URLs.
Laptops only orchestrate.
No. Public web collection only.
No. Remote Work is static business IP for SaaS. This is rotating residential for team scraping.
Only if you want one office SOCKS hop. Many teams use extract URLs directly.
Usually a bad idea for scraping. Static is for allowlists.
Historical. The page is team data collection.
Shared residential traffic plus revocable auth. Use Remote Work instead if this is SaaS login, not collection.