Cloud Phone Farm: Run 20 to 6,000 Phones From a Browser
A cloud phone farm is a fleet of Android phones that run in a datacenter and are operated from a browser instead of a shelf. On DeviceFarm, each phone runs real Android on ARM hardware, keeps its own device identity and proxy slot, and is ready in under 60 seconds. Fleets scale from 20 to 6,000 phones.
Last updated
No credit card required
What Is a Cloud Phone Farm?
A cloud phone farm is a phone farm whose devices are hosted by a provider: you create, group and operate Android phones from one browser dashboard, each with its own identity and proxy slot, while the provider runs the hardware. On DeviceFarm the fleet scales in plan tiers from 20 phones ($39.99 per 30 days) to 6,000 ($819), plus runtime.
A cloud phone farm is the hosted version of a phone farm. The phones run Android in a datacenter instead of on your shelves, each as an isolated device with its own persistent identity (IMEI, Android ID, MAC, serial, model, timezone and locale) and its own proxy slot, and you reach all of them from one browser dashboard. It differs from a single cloud phone in scale and tooling, from a physical farm in who owns and repairs the hardware, and from an emulator farm in what runs underneath: on DeviceFarm, real Android on ARM phone hardware rather than an x86 emulator.
The farm moves; the work does not. You still decide how many phones there are, which account lives on which phone, which IP each one uses and who on your team may open them. That operating layer is what the rest of this page is about.
Day to day, running the farm is fleet management: creating phones in batches, labeling them by client or market, pairing proxies, starting and stopping them in bulk, watching several screens at once and, with the Automation add-on, spacing scheduled tasks so posts do not all go out in the same minute. All of it happens in one browser tab, and every phone keeps the same identity between sessions.
Because nothing on your side is physical, the fleet can change size with the work. Plans step from 20 phones through 30, 40, 50 and 100 up to 6,000, and a phone you delete goes to a trash you can restore from, not into a drawer of hardware you already paid for.
A real Android phone, kept in our datacenter
Each DeviceFarm phone is real Android running on ARM servers in our datacenter. It works like the Android phone you have at home, except you open it in your browser instead of holding it.
Real Android, on ARM servers
A complete Android system, Android 10 to 16, running natively on ARM servers: the same chip architecture as the phone in your pocket. Not an emulator, not an Android VM on a PC.
Used like the phone in your hand
Install apps from the catalog or your own APK, sign in, tap, swipe and type. Apps run on it natively, the way they run on an Android phone.
Kept in our datacenter
It stays on when you close the tab, keeps its own identity and proxy slot, and you control it from your browser on devicefarm.io. It has no SIM card, so no calls or carrier SMS.
How Many Cloud Phones Can One Person Operate?
It depends on how much of the work is hands-on. Scheduled work, such as warm-up sessions and posts released on a timetable, scales with plan size rather than attention. Hands-on work, such as replying to messages, fixing a login or editing a profile, scales with how many screens one person can follow.
- Watch: pick the phones you need and see up to 24 of them live on one screen.
- Act: select a filtered list, or every phone, and start, stop, assign or delete them in one pass, with progress shown phone by phone.
- Schedule: with the Automation add-on ($99 a month), queue tasks across the selection and release them in groups, minutes apart.
When hands-on work becomes the limit, add a team member rather than a second account; seats cost nothing. Each of these controls is described on the phone farm management software page.
How Do You Pair Proxies With a Cloud Phone Farm?
Give every phone its own proxy and keep the pair together for the life of the account. A phone whose IP changes country between sessions looks like a device that travels; two phones on one IP look like one household.
- Type: residential proxies are the usual default for social accounts, mobile proxies cost more, and datacenter IPs are the easiest for platforms to flag. The guide to residential proxies for cloud phones compares them.
- Session: use a sticky session so the IP holds steady instead of rotating mid-session.
- Protocol: each phone accepts SOCKS5, HTTP or HTTPS.
- Consistency: keep the phone’s timezone and language in line with the proxy’s country.
- Volume: paste proxies in bulk, one per line as type://user:password@host:port, and sort them into proxy groups before assigning them.
How Do You Scale a Cloud Phone Farm From 20 to 6,000 Phones?
Scaling is a plan change. Each tier reserves a number of phone slots, each holding one Android cloud phone, for a flat price per 30 days, and the price per slot falls as the fleet grows. Renting the fleet for a project? Phone farm rental adds worked 30-day totals by daily runtime. A selection of the tiers:
| Phones in plan | Plan price / 30 days | Per phone slot |
|---|---|---|
| 20 | $39.99 | $2.00 |
| 50 | $49.99 | $1.00 |
| 100 | $59.99 | $0.60 |
| 200 | $99 | $0.50 |
| 500 | $189 | $0.38 |
| 1,000 | $289 | $0.29 |
| 2,000 | $389 | $0.19 |
| 6,000 | $819 | $0.14 |
Runtime sits on top of the plan: $0.012 a minute once the 60 free monthly minutes included with the plan are used, with a daily ceiling of $2.10 per phone. A plan is paid up front and, by card, renews monthly by default until you cancel; an upgrade mid-cycle costs the difference between the two plan prices, and a downgrade takes effect at the next cycle. To weigh a given fleet against owning the hardware, use the phone farm cost calculator; every tier is listed on the pricing page.
Comparing providers for a fleet? Redfinger and LDCloud sell cloud phones one device at a time and describe theirs as gaming phones. DeviceFarm is built to run a fleet: one plan for 20 to 6,000 phones, each with its own identity and proxy slot, unlimited team seats and one dashboard for all of it.
How Does a Team Share a Cloud Phone Farm?
- Invite: the account owner invites members by email. Seats are unlimited and free.
- Isolate: switch on the setting that limits each member to the phones assigned to them, plus any phones left shared.
- Assign: select phones in bulk and assign them to a member, or set them back to shared.
- Revoke: remove a member when a contract ends, without touching their phones or the accounts on them.
Agencies that split phones by client will find the full workflow in phone farms for agencies.
What Happens When a Cloud Phone Fails?
On a rack, a frozen phone means someone walking over to unplug it. In a cloud phone farm you restart it from the dashboard, and anything wrong with the hardware underneath is ours to fix rather than yours to replace. If a phone stays down, support answers on Telegram at @devicefarmio.
Two habits limit the damage from any single failure: keep a few spare phones ready, as the sizing rule in the phone farm guide suggests, and keep each account on one phone, so a failure touches one account rather than a batch.
Can You Run a TikTok Phone Farm in the Cloud?
Yes. The setup is the same as for any platform: one account per phone, a proxy in the account’s market and an account warm-up period before the first posts. The cloud phone for TikTok page covers what is specific to TikTok, and cloud phones for Instagram does the same for Instagram.
Built on real hardware, run from your browser
Clone a working setup
Once one phone is configured, clone it up to 10 times in a single step. The copies keep its model, country, timezone and language, so a new batch matches the market it serves.
Groups and tags
File phones into groups by client or market and tag them freely. Filter the list by group, tag, team member or name once the fleet runs past a few dozen.
GPS set per phone
Paste a latitude and longitude for any phone, so location-aware apps see the same city its proxy exits from.
Trash before delete
Deleted phones go to the trash first and can be restored in bulk, so cleaning up after a finished project stays reversible until you empty it.
Usage by phone and by member
Billing breaks runtime down per phone and per team member, so you can see who ran what before you invoice a client.
Idle phones stop the meter
The plan reserves your phone slots; runtime is billed only while a phone runs, after the 60 free minutes a month each paid plan includes for the account. A farm that sleeps overnight costs little beyond the plan.
A Week of Operations: Racks vs. Cloud Phone Farm
Same 100 accounts, same team. Here is where the hours go in each setup.
| Phones on your own racks | Cloud phone farm on DeviceFarm | |
|---|---|---|
| Adding 10 phones for a new client | Order, wait for delivery, flash, cable and label each unit | Create or clone them in the dashboard, each live in under 60 seconds |
| A phone freezes overnight | Someone on site unplugs and reboots it in the morning | Restart it from the browser; hardware faults are ours to fix |
| Giving a VA access to 15 phones | Remote-desktop access to the whole control PC | Invite them free and assign exactly those 15 phones |
| Replacing proxies on 40 phones | Edit each device’s network or proxy app by hand | Import the new list in one paste, then reassign phone by phone |
| Posting to 60 accounts | A script per device, or a person per batch | With the Automation add-on, one task list released in groups, minutes apart |
| A client leaves | Wipe units by hand, then store or sell the hardware | Delete their phones in bulk and pick a smaller tier for the next cycle |
| The fleet doubles in a month | Double the shelving, power and cabling | Move up a plan tier |
How Do You Set Up a Cloud Phone Farm?
- 1
Create the first phones
Sign up without a card, choose an Android version from 10 to 16 and create a phone. It is ready in under 60 seconds.
- 2
Pair each phone with a proxy
Import your proxy list, give every phone its own, and match the phone’s location settings to the proxy’s country.
- 3
Organize, then hand out
Group and tag phones by client or market, then assign them to team members, who can be limited to what you give them.