Start Here: Residential Proxies (Shared Account)

Team Data Collection

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 Residential Proxies pack with per-person or per-region extract URLs. Optional: joyproxy-server as a single office hop. SaaS allowlists belong on Remote Work (ISP Proxies · Static Dedicated).

Purchase Residential Traffic I Need SaaS Allowlist IPs →
Who It's For

Distributed Teams Collecting Public Pages

Consultancies

Contractors in different countries, one bill.

Startup Data Teams

No scraper farm yet — laptops plus shared endpoints.

Research Pods

Regional staff pulling local pages without home-IP bans.

Ops Leads

Need to revoke a person without rotating everyone’s password.

Pain Points

Do Not Confuse This with Remote Work

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.

🏠

Home IP Burns

Each analyst crawls from home and gets blocked.

🔐

Passwords in Slack

One shared proxy user for twelve people.

🌍

Travel Geo Drift

Someone abroad still needs home-market pages.

💼

VPN Collision

Corp VPN and scraper proxy fight on the same laptop.

📊

No Owner

Nobody knows which job burned yesterday’s GB.

🚪

Offboarding

Ex-contractor still has the endpoint.

What to Buy

Shared Rotating Pack, Optional Gateway

Recommended: Residential Proxies on a shared account with separate authorizations. Alternative: joyproxy-server if the office wants one local SOCKS hop. Do not buy ISP Proxies · Static Dedicated here — that is Remote Work.

Product Billing Use It When…
Residential Proxies Recommended for This Workflow 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.
Recommended Path

How to Start (One Recommended Path)

Path A — Shared Residential Account (Recommended)

One bill, many extract URLs.

  1. Create the JoyProxy account; buy Residential Proxies.
  2. Issue sub-authorizations or separate credentials per person.
  3. Generate country endpoints; write them in the team doc.
  4. Revoke auth the day a contractor leaves.
Residential Proxies →

Path B — Hard Pages in One API Pipeline

Laptops only orchestrate.

  1. Workers submit URLs to your queue.
  2. A central job calls Web Scraping API.
  3. People do not each buy credits.
  4. Keep easy volume on the shared rotating pack.
Web Scraping API →
Decision Guide

Pick One — Do Not Mix These on the Same Job

Use Residential Proxies When

  • The work is public page collection.
  • People already have scripts or browsers.
  • You need regional exits and one invoice.

Use Remote Work (ISP Proxies · Static Dedicated) When

  • Staff must log into SaaS with an allowlisted IP.
  • The target is HR, ERP, or a vendor portal — not scraping.
  • Sessions must stay on one address for weeks.
Getting Started

First-Week Checklist

FAQ

Common Questions

Office Intranet / NAS / VPN Replacement?

No. Public web collection only.

Same as Remote Work?

No. Remote Work is ISP Proxies · Static Dedicated for SaaS. This is Residential Proxies for team scraping.

Need JoyProxy-Server?

Only if you want one office SOCKS hop. Many teams use extract URLs directly.

Static IP for the Whole Team?

Usually a bad idea for scraping. Static is for allowlists.

Filename Remote-Work-Tunnel?

Historical. The page is team data collection.

Resources

Go Deeper

Remote Work (SaaS IPs) Data Scraping Proxy Gateway Software Help Center

Give the Team One Rotating Pack, Not Twelve VPNs

Shared residential traffic plus revocable auth. Use Remote Work instead if this is SaaS login, not collection.

Purchase Residential Traffic I Need SaaS Allowlist IPs →