No. You need an Android phone and a data SIM. You don’t need a server, a VPS, a static IP, or a network engineer.
That answer surprises people, because a working mobile proxy genuinely does need infrastructure. The question is who runs it. A customer types a host, a port, a username and a password into their scraper or their browser, and traffic has to come out of a phone on a carrier network somewhere else entirely. Something has to sit in the middle and make that work.
What has to exist between a customer and a phone
- A tunnel from the phone to a relay, so a phone behind carrier NAT can be reached at all. Phones don’t have reachable public addresses, so the connection has to be made outward from the phone and held open.
- Port and address translation on the relay, so each customer’s port maps to the right phone and nothing leaks between devices.
- Authentication, so a port only answers to the credentials it was issued, and stops answering when a plan lapses.
- IP rotation, triggered on demand, on a schedule, or through a rotation link, and recovered cleanly when the carrier hands back a new address.
- Reconnection handling, because phones lose signal, switch towers, and reboot. A proxy that dies at the first blip isn’t sellable.
- Billing and a customer console, so the people buying from you can manage their own access without going through you.
We run all of that. You install the app, scan a QR code to pair the phone, and the device comes up as a proxy with credentials you can hand to a customer.
What you’re responsible for
The physical side, and it’s the part that decides whether your proxies are good. Phones need power, they need a data plan that isn’t throttled into uselessness, and they need to stay online. Carrier choice matters more than phone choice, because the IP reputation your customers care about belongs to the carrier, not the handset.
No root and no custom firmware. Older phones work. Adding capacity means adding phones and SIMs, not provisioning anything.