How to build a phone farm

What a working device farm needs, component by component, from hardware and network to the software layer most builds never finish. Written for agency owners, not engineers.

Reviewed by John Carroll · Updated 7 October 2026

This is the build, honestly described, including the parts that take months rather than days.

1. Hardware

• Physical iPhones. Refurbished is normal. Model consistency matters more than being current.
• One control chip per phone, the USB device software uses to drive the handset.
• A Windows machine. The kernel service that drives the chips is Windows only. A Mac cannot run it.
• Powered USB hubs. Unpowered hubs brown out under charging and transfer.
• A rack with airflow. Heat throttles phones and throttled phones fail jobs.

2. Network

Decide this before you buy anything. One office connection links every account on it. Options are mobile data per phone, mobile proxies covering groups, or shared Wi-Fi if the fleet is small. More on proxies.

3. The software layer

This is the project. Driving one phone is a week. The rest is where builds stall:

• Account creation that survives verification, repeatedly.
• Warming that varies genuinely rather than on a fixed offset.
• A job queue with retries and circuit breakers, so one stuck phone does not stall the fleet.
• Ban detection and automatic replacement.
• Credential storage that is encrypted and audited.
• Observability: which phone, which account, which job, which error.

4. Operations

Phones need rebooting. Apps update and break selectors. Chips disconnect. Agents need to survive a power cut without someone driving to the office. None of this is visible at ten devices and all of it is the job at two hundred.

5. The decision

Build it if you have a developer who is yours and time to spend. Licence it if your constraint is traffic this quarter. The full comparison.