JoyProxy groups residential proxy products into three lines: Rotating Residential Proxies, Static Residential Proxies, and Custom Residential Proxies. The names describe behavior, not marketing tiers—rotation frequency, session stability, and how much control you need per port.
If you are new to the dashboard, the parent menu stays Proxy IP (covering all proxy types today). Inside it you will see Purchase Proxies, My Proxies, Authorization, and Endpoint generator—the same workflow for every line.
Rotating Residential Proxies (pay per GB)
Use this when each request or short-lived session should look like a different household connection.
- Billing: prepaid traffic packages (GB).
- Behavior: generate fresh endpoints on demand; IPs rotate on the provider side.
- Best for: web scraping, price monitoring, ad verification, large-scale crawls.
- Geo: country / state / city via geoname IDs at generation time.
Start on the Rotating Residential Proxies product page or open Purchase Proxies → Rotating after login.
Static Residential Proxies (dedicated ports by duration)
Use this when a platform should see the same egress identity for days or weeks.
- Billing: per IP / port by duration (daily, weekly, monthly, annual).
- Behavior: stable host:port for the rental period; city locked at purchase.
- Best for: marketplace seller accounts, logged-in dashboards, partner portals that whitelist IPs.
- Geo: pick country (and optionally province / city) before checkout.
See Static Residential Proxies or Purchase Proxies → Static.
Custom Residential Proxies (multi-port + optional rotation)
This line sits between pure rotation and pure fixation: multiple ports in one order, flexible geo per allocation, and optional timed rotation (e.g. every N minutes) while staying in the same region.
- Billing: priced per port × duration plan (similar unit economics to static).
- Behavior: run several isolated slots (stores, channels, QA environments) under one account.
- Best for: multi-store ops, regional QA, automation that needs predictable geo with controlled refresh.
Details: Custom Residential Proxies and Purchase Proxies → Custom.
Quick comparison
| Line | Primary cost driver | Session identity | Typical operator |
|---|---|---|---|
| Rotating | GB transferred | Changes frequently | Data / growth engineering |
| Static | Rental duration | Fixed for the plan | E-commerce / account ops |
| Custom | Ports × duration | Fixed or timed rotation | Multi-region product teams |
Authorization and endpoint generation are shared
All three lines use the same Authorization step first—IP whitelist and/or username/password credentials. Then open Endpoint generator (or the API in OpenAPI Center) for the product tab you purchased.
Integration endpoints still use short-term, long-term, and custom-ip product types in JSON—the public names above map to those values. No breaking change for existing scripts.
Common mistakes
- Logging into a high-value seller account through a rotating pool that changes every few minutes.
- Buying static ports for a crawler that only needs anonymous page fetches (you will overpay for stability you do not use).
- Expecting custom ports to bill like GB traffic—they follow port-based plans, not pay-per-GB.
Most mature teams run rotating pools for collectors and static or custom ports for operators who sign in to accounts. If you are still on the $5 new-user credit, validate one rotating generation and one static or custom trial port before scaling—see our $5 credit onboarding guide.