Residential, datacenter, mobile IP: which “one phone one IP” actually is
The same slogan is two different products. How platforms see the three IP types, the cost bands, and when a facility IP is enough vs when you need residential.
“One phone, one IP” is everywhere. It only talks about count, not quality. A unique exit per phone, and a unique clean residential exit per phone, are an order of magnitude apart in cost.
Platforms don’t see the three types the same way
Datacenter / facility IP Address blocks from clouds and IDCs. They’re public — databases tag which IPs are facilities. A platform can tell the hit didn’t come from a house.
Cheap, stable, wide, low latency. The identity is on the label.
Residential IP A real home broadband address. Two flavors:
- Static residential: stays with you. Better for warming and long-running accounts. One account, one IP.
- Dynamic residential: rotates from a pool. Fine for scraping. Bad for logged-in account work.
Residential is expensive and uneven. Some “residential” is a botnet of other people’s devices. Stability and ethics both suffer.
Mobile / cellular IP Carrier 4G/5G. Highest trust in a platform’s eyes, because that’s how most real users come in. It’s also shared (thousands behind a tower), so IPs change and collide. A poor fit for a fixed “one phone one IP” bind.
Cloud Device is a facility IP; Home Device uses your network
Cloud Device’s default is a US dedicated line — a facility IP, not residential. We say that plainly. You can add SK5. You bring the nodes.
It solves: a stable facility line the moment you start; change the exit yourself with SK5.
It does not solve: looking like a hit from a residential block.
Home Device uses that phone’s own network. Change the route with Shadowrocket. You bring the nodes. We don’t sell proxies or “cross-border networking”.
When a facility line is enough
- Proving connect, mirroring, and dispatch
- Collection / monitoring without high-value logged-in accounts
- Tight budget; get the matrix moving first
When you should bring a residential line
- The account itself is expensive to lose
- The platform is known to punish facility ranges
- You’re past proof, into long warming and scale
Home Device can take your own line
That’s the practical network split when you choose.
Home Device uses the phone’s network. Shadowrocket if you want another route. You pick the vendor.
Cloud Device defaults to the US line. SK5 optional. You bring the nodes.
Neither locks you to our IP. We don’t sell proxy lines. See Device network.
Don’t stare only at the IP
An IP is necessary, not sufficient.
We’ve seen expensive static residential wasted on:
- US geo on the IP, domestic timezone and language on the account
- Twenty accounts tapping on the same clock
- A dirty environment — leftovers from the last account
A clean IP won’t save that. Platforms look for consistency and human pace, not one metric.
Home Device can clear keychain/sandbox leftovers and clone apps (AppsManage). Get the environment layer right; the rest is your ops.
A practical order
- Prove the flow. Connect, group control, media dispatch. Cloud Device can stay on the default US line; Home Device can stay on the phone’s Wi-Fi.
- Reassess when you start warming. Watch how the target platform treats facility ranges. Change the route: Shadowrocket on Home Device, SK5 on Cloud Device. You bring the nodes.
- After you scale, split by account value. High-value accounts on residential lines you prepared. Test and helper accounts can stay on facility lines. Don’t treat every phone the same.
Unsure? Tell us the platform, account count, and region before you lock a purchase.
