DeviceFarm
All guides
By the DeviceFarm TeamUpdated 10 min read

How to Build a Phone Farm, Step by Step

To build a phone farm, count the accounts that must stay separate, choose a device source (used phones on a rack, a box phone farm or cloud phones), give every device its own proxy, and warm up accounts before automating. A cloud build is running the same day on a plan from $39.99 for 20 phone slots plus runtime; a physical build takes weeks.

This guide is for teams that operate accounts: agencies, sellers, marketers and automation builders. App-testing grids are a different job with different tools. The steps below run in the order you will actually face them, and each one compares the physical route with the cloud route, because the right answer depends on your account count, your budget and whether anyone can be on site when a cable fails.

What is the fastest way to build a phone farm?

The fastest way to build a phone farm is to rent Android cloud phones instead of buying hardware. You create devices in your browser, each live in under 60 seconds, attach a proxy to each, and start operating. There are no handsets to source, no firmware to flash and no hubs to wire. A physical build of 20 phones takes weeks of sourcing and setup and $1,400–2,800 upfront; a cloud build of 20 phones is $39.99 a month plus runtime.

Step 1: Should you use loose phones, a box or cloud phones?

There are four ways to put devices in a farm, and the choice shapes every step after it:

  • Loose phones on a rack: used Android handsets on shelves, wired to powered USB hubs. Full control and no subscription, but you are the repair shop.
  • A box phone farm: phone mainboards without screens or batteries, mounted in a chassis with shared power and USB. Denser than loose phones, with the same maintenance in a smaller space.
  • An emulator farm: Android virtual machines on a PC or server. Cheap and quick to create, but x86 emulators expose traits apps can read (see the Android emulator glossary entry), so they suit testing more than long-lived accounts.
  • A cloud phone farm: Android phones hosted in a datacenter and operated from your browser, with the provider running the hardware.

For accounts that need to last, the realistic choice is between your own hardware and cloud phones. Cloud wins on speed, upfront cost and maintenance. Owned hardware usually wins on raw cost within a year once phones run more than about an hour a day. The phone farm cost calculator shows where that crossover falls for your numbers.

What about a box phone farm?

A box phone farm packs about 20 phone mainboards into one chassis with shared power, cooling and a link to a control PC, which saves shelf space and removes batteries but lets one power or USB fault take every board offline at once. The box phone farm guide covers how the boxes work, the risks, and a dated price: one Alibaba listing showed $550 to $1,880 for a 20-board box when we checked it on October 3, 2026.

Step 2: How many phones do you need?

Size the farm by the accounts that must stay unlinked, not by the total number of accounts: one phone for each account you cannot afford to lose, plus a few spares. The phone farm guide has the sizing formula and a table of phones and plans for 10 to 200 accounts.

Step 3: What do you need to buy for a physical phone farm?

If you build it yourself, this is the shopping list. The cost ranges are the assumptions our cost calculator uses as of October 2026; check current prices where you buy.

  • Phones: used Android handsets at $60–120 each. Buy batches of the same model so one firmware image and one set of settings fit all of them.
  • USB hubs, cables and racking: $10–20 per device. Powered hubs with enough current per port, short certified cables, and open shelving that lets air through.
  • A control computer: one machine running ADB and screen-mirroring software such as scrcpy, plus your automation tool.
  • Proxies: $3–8 per device per month for a residential IP per phone. Without them, every phone shares your office IP.
  • Power: $1–2 per device per month, more with cooling.
  • A spare-parts reserve: replacement phones, cables and hubs for the units that fail each year.

For 20 phones, that adds up to $1,400–2,800 upfront and $80–200 a month in proxies and power, before your time. Software is the cheap part: ADB and scrcpy are free, and automation runs through RPA scripts that tap through apps as a person would. The expensive part is the time it takes to glue them together, which is what all-in phone farm software with its own devices replaces.

Step 4: How do you handle power, cooling and space?

Twenty to fifty phones on permanent charge are a small electrical installation, and they fail in predictable ways. Plan for these before the first phone goes on the shelf:

  • Batteries. Lithium batteries kept at full charge in a warm room degrade and can swell. Inspect them regularly, and pull any phone with a lifted back or a bulging screen out of service immediately.
  • Hubs. Cheap hubs brown out when every port draws current at once, and phones then drop off ADB. Use powered hubs rated for the number of ports you fill.
  • Heat. Phones throttle when hot, and heat ages batteries faster. Leave space between devices, keep air moving, and avoid enclosed cabinets.
  • Circuits and backup. Spread the load across circuits, and put the router and control PC on a small UPS so a power blip does not drop the whole farm.
  • Labels. Number every phone, port and cable. At 3 a.m., “phone 14 on hub 2, port 6” is the difference between a five-minute fix and an hour of guessing.

If your build uses SIM cards, check the law where you operate. In the UK, the Crime and Policing Act 2026 makes it an offence, from October 29, 2026, to possess or supply a “SIM farm”: a device capable of using five or more physical SIM cards simultaneously or interchangeably to make calls or send and receive messages. The Act includes a “good reason” defence for legitimate uses such as broadcasting (gov.uk guidance, checked October 3, 2026). Cloud phones carry no SIM cards. This is not legal advice.

Step 5: How do you set up a cloud phone farm instead?

The cloud route replaces steps 3 and 4 with an account. On DeviceFarm the setup looks like this:

  • Create an account. The free trial needs no credit card and covers a few runtime minutes to check the stream and your apps.
  • Pick the tier that covers your phone count, from 20 to 6,000 phones; phone farm rental explains how renting a whole fleet works. Each plan covers 30 days, paid upfront, and you pay by card or in crypto (Bitcoin, Ethereum, USDT, Solana and most other coins); card plans renew monthly by default, and you can cancel anytime from Billing.
  • Create phones with the Android version you need, from 10 to 16. Each phone in a cloud phone farm is live in under 60 seconds with its own IMEI, Android ID, MAC address, Bluetooth MAC, Wi-Fi BSSID, serial, model, timezone and locale.
  • Name, group and tag the phones by client, platform or market so the fleet stays readable at 200 devices.
  • Invite your team. Seats are unlimited at no extra cost, and each phone can be assigned to a member.

A new phone costs nothing beyond its plan slot until it runs, so you can stage the whole fleet before you use it.

Step 6: How do you attach a proxy to every phone?

Each device needs its own network identity in the place its account is supposed to be. Attach one proxy per phone over SOCKS5, HTTP or HTTPS, in the right country and ideally the right city. A residential proxy is the default for social accounts, a mobile proxy suits the accounts you can least afford to lose, and datacenter IPs are fine for jobs where nobody scores your network origin. Then set the phone’s timezone and language to the proxy’s region. Our guide to residential proxies for cloud phones covers types, checks and cost per phone.

Step 7: How do you warm up and automate accounts?

New accounts should behave like people before they work like machines. Spend the first days on light, human-paced activity: scrolling, watching, a few follows, at different times on each phone. Account warmup gives the account an ordinary history instead of appearing and acting at once.

Once accounts are warm, automate the repetitive work. With the Automation add-on ($99 a month on top of the phone plan), DeviceFarm runs built-in automations for TikTok, Instagram, Facebook, YouTube, Reddit, Threads, X, Pinterest, Gmail and Telegram, and opens the REST API and the MCP server so you can drive phones from your own code or from Claude in plain language. On any plan, you can install any APK manually and operate the phones yourself.

Step 8: How do you run the farm day to day?

  • Watch in batches. Stream up to 24 phones side by side in one grid instead of opening them one at a time.
  • Keep one account per device and one proxy per device for life, and write the mapping down.
  • Review weekly: accounts with new verification prompts, proxies that changed region, phones that stopped responding.
  • Scale by tier. Each plan covers 30 days, and you can change the tier from one period to the next: a bigger one when volume grows, a smaller one when it shrinks.

What does it cost to build a phone farm?

Here is what 20 phones cost on each route, using the figures above. Proxies are extra on every route, at $3–8 per device per month.

Cost of a 20-device phone farm by route, as of October 2026
Route (20 devices)UpfrontEvery monthWho maintains it
Used phones on a rack$1,400–2,800 for phones, hubs and racking$80–200 in proxies and power, plus repairsYou
Box phone farm$550–1,880 for the box in one Alibaba listing (October 3, 2026), plus a control PCProxies, power and spare boardsYou
Cloud phones, 30 minutes a day each$0$39.99 plan + $215.28 runtime (17,940 billable minutes at $0.012) = $255.27, plus proxiesThe provider
Cloud phones, around the clock$0$39.99 plan + about $1,260 runtime (20 × $2.10 daily cap × 30 days), plus proxiesThe provider

The pattern is clear: cloud is cheaper when phones work less than about an hour a day or the fleet changes size, and owned hardware gets cheaper when phones run longer than that, every day, for a year or more. See the pricing page for every tier from 20 to 6,000 phones, and run your own hours through the cost calculator before you commit.

What mistakes should you avoid when building a phone farm?

  • Putting every phone on the office Wi-Fi with no proxies. The devices are separate; the IP is not.
  • Logging several important accounts into one phone because the app allows it.
  • Buying 50 phones before you have tested the workflow on 5.
  • Recycling a banned account’s device for a new account without resetting its identity.
  • Posting on day one and automating at full volume in week one.

The short version

Building a phone farm comes down to a few decisions: own hardware or cloud phones, one device per account that matters, one proxy per device, a warmup period, and a daily routine you can sustain. Build a rack or a box if you have capital, space and someone on site; rent cloud phones if you want to be operating the same day. If you manage client accounts, read next how a phone farm for agencies keeps dozens of clients separate.

Sources

Frequently asked questions

A physical farm of 20 used phones costs about $1,400–2,800 upfront plus $80–200 a month in proxies and power. A cloud farm of 20 phones runs on a plan from $39.99 per 30 days plus runtime at $0.012 a minute, capped at $2.10 per phone per day (each paid plan includes 60 free minutes a month for the account), plus your own proxies.

A physical farm needs ADB, a screen-mirroring tool such as scrcpy, and automation scripts or an RPA tool. A cloud phone farm gives you the dashboard, streaming and a proxy slot per phone, so you do not assemble the stack yourself; on DeviceFarm, built-in automations and the API come with the Automation add-on.

A physical farm of 20 to 50 phones usually takes weeks: sourcing matched handsets, flashing, wiring, and testing. A cloud phone farm of the same size can be running the same afternoon, since each phone is live in under 60 seconds.