Phone Farm for Agencies

For an agency, the risk model comes down to one rule: no client account should ever be able to affect another. When you run dozens of brands across TikTok, Instagram and Facebook from shared phones or a shared office IP, platforms can connect those accounts, and a single flagged connection can reach accounts that did nothing wrong. This guide covers when an agency needs a phone farm and when it does not, how to set one up per client, who should own the accounts, how a team works inside it, and how to price it into a retainer.

Why do agencies need a phone farm?

Agencies need a phone farm because client accounts managed from shared devices or a shared IP get linked, and linked accounts are restricted together. One client’s aggressive campaign, or one proxy reused across clients, can trigger checks on every account that shares its fingerprint. A phone farm puts each account on its own device with its own proxy, so a problem stays inside one client instead of spreading across the book of business. Does TikTok ban all your accounts shows how that spread works on TikTok.

In agency work, isolation is not a security feature. It is part of the service: clients pay you to make sure their account is never collateral damage.

When does an agency not need a phone farm?

Not every agency does. If your work is publishing to brand accounts you manage through official tools, such as Meta Business Suite or an approved scheduler, the platform already knows those accounts belong to the brand and expects them to be managed together. A device per account adds cost without adding safety.

A phone farm earns its place when the work happens inside mobile apps (TikTok, Instagram Reels, community management in-app), when accounts belonging to different clients must not be connected, or when the tasks you run are not available through any official API. Many agencies end up with both: official tools for scheduled publishing, devices for everything that needs the app.

Which client platforms need their own device?

The answer changes by platform, because each one offers a different official route for agencies:

For Instagram specifically, Instagram multiple accounts explains how Accounts Center connects profiles and why client accounts should never share one.

How do you set up one device per client account?

The foundation is strict isolation: one account, one device, one IP. Each Android cloud phone carries its own IMEI, Android ID, MAC address, Bluetooth MAC, Wi-Fi BSSID, serial, model, timezone and locale, and those values stay the same for the life of the account. Pair each phone with a proxy you buy in the client’s market, residential or mobile; proxies are not included in DeviceFarm plans, and each phone has a slot for one. An account that has behaved normally for months keeps presenting the same device every session, unlike an emulator that resets or one handset juggling five logins. The glossary entry on device isolation lists every layer that has to stay separate.

Structure matters as much as isolation once you pass a few dozen devices:

• Group phones by client, so each brand’s devices, proxies and automations live together.
• Name every phone the same way: client, platform, handle. “acme-tiktok-acmeofficial” is readable by a new hire on day one.
• Tag phones by market or campaign, so you can filter “all US TikTok accounts” in one click.
• Keep a spare phone or two per large client for new accounts, so nobody is tempted to double up on an existing device.

Who should own the client’s accounts and logins?

The client should. The agency operates the account; the client owns it. Getting this right protects both sides when the relationship ends, and it keeps the account’s recovery details out of your team’s personal inboxes. Consent is also where the legal line sits: are phone farms legal covers what the law prohibits.

• Get written authorization to operate each account, naming the platforms and the kind of activity.
• Register or keep recovery email and phone number in the client’s name, not a VA’s.
• Store credentials in a shared password manager the client can audit and revoke, not in chat messages.
• Do not create client accounts under the agency’s own email domain or payment card. Shared recovery details link accounts across clients.
• Keep a register of which device and which proxy run which account.

How do you offboard a client cleanly?

Hand back the credentials, remove any agency recovery details, and log out of every session. Then delete the client’s phones. The device identity and everything stored on it go with the phone, and you do not recycle an identity that a platform associates with the client’s account. Remove the client’s proxies from your provider at the same time, so they are never reassigned to another client.

How does an agency team work in a shared phone farm?

A farm only works for an agency if the whole team can operate it without stepping on each other. Shared logins make that impossible to trace and painful to revoke. On DeviceFarm:

• Team seats are unlimited at no extra cost, so every account manager, VA and contractor gets their own login.
• Each phone can be assigned to a member. With per-member isolation turned on, a VA sees and opens only the phones assigned to them.
• Usage is tracked per member and per phone in the billing dashboard, so you can attribute runtime to the right person and the right client.
• Removing a member cuts their access to the phones, including the viewer and ADB.
• Up to 24 phones stream side by side in one grid, so one person can supervise a client’s whole fleet at once.

There are no roles or permission levels and no log of manual actions yet. Phone assignment is how you limit what each person sees, and your own register is how you record who worked on which account.

How do you onboard a new client in a day?

1. Collect the authorization, the account list and the credentials into the password manager.
2. Create one phone per account in a new group named after the client, with the Android version the client’s apps need.
3. Buy one proxy per account in the client’s market and attach each to its phone. Match timezone and language to the proxy.
4. Log into each account on its own phone, and be ready for a “confirm it’s you” check on the first login from a new device.
5. Assign the phones to the account manager, and record device, proxy and account in your register.
6. Start a light warmup on any new account before campaigns begin.

Why should you warm up accounts before you deliver?

New client accounts should not go straight to full-volume posting. Spend the first days on light, human-paced activity so the account builds an ordinary history before campaigns start; account warmup explains what that period does. With the Automation add-on ($99 a month on top of the phone plan), built-in automations handle warmup, scheduled posts and outreach on TikTok, Instagram, Facebook, YouTube, Reddit, Threads, X, Pinterest, Gmail and Telegram at randomized times, so a VA is not nursing eighty accounts by hand.

Read each platform’s rules before you automate anything: TikTok’s Community Guidelines, for example, list using automation to run many accounts as spam. For the behaviors that trip platform checks, see our guide to running multiple accounts without getting banned.

How should an agency price a phone-farm service?

The clean model is to pass device cost through per client and price your margin into the retainer. DeviceFarm bills a plan for the phone slots, covering 30 days and paid upfront by card or in crypto (Bitcoin, Ethereum, USDT, Solana and most other coins); card plans renew monthly by default until you cancel. On top comes runtime at $0.012 per minute, capped at $2.10 per phone per day. Every paid plan includes 60 free runtime minutes a month, shared by the account. That makes per-client cost easy to compute. A worked example:

• An agency runs 12 clients with 4 accounts each: 48 accounts on 50 phones, the Pro plan at $49.99 per 30 days.
• Each account’s phone runs 30 minutes a day: 48 × 30 × 30 = 43,200 minutes, minus the 60 free minutes, is 43,140 × $0.012 = $517.68 of runtime.
• Plan plus runtime is $567.67 a month, or about $47.31 per client.
• Residential proxies at $3–8 per account per month (our cost calculator’s assumption) add $12–32 per client.
• If you use built-in automations, the Automation add-on adds $99 a month, or $8.25 per client.
• Device and network cost per client: roughly $59–79 a month, or $68–88 with the add-on.

If you bill a “managed devices” line of $150 per client per month, that leaves $71–91 per client ($62–82 with the add-on) to cover your team’s time on the farm. The daily cap is what makes fixed-price quotes safe: even a phone left running all day costs at most $2.10 that day, so the worst case for a 4-account client is about $252 of runtime a month. Quote against that ceiling and you never lose money on an idle phone someone forgot to stop. See the pricing page for every tier, phone farm rental for how the 30-day terms work, or model a client load with the phone farm cost calculator.

Which mistakes cost agencies client accounts?

• Logging several clients’ accounts into one phone because the app’s account switcher allows it.
• Reusing a proxy from a departed client on a new client.
• Letting a VA check a client account from their personal phone.
• Recovery emails on the agency’s domain, which link every client account you created.
• Skipping warmup because the client wants results this week.

The short version

An agency phone farm runs on strict isolation: one client account per device, each with a persistent identity and a matching proxy, owned by the client, operated by a team with individual logins, organized by client, and warmed up before delivery. Get that structure right and you can grow from a handful of clients to hundreds without any account becoming another’s liability. If you are starting from scratch, follow the step-by-step guide to building a phone farm, then bring your clients onto a cloud phone farm.

Sources

• YouTube Help: Create a YouTube channel, checked October 4, 2026.
• TikTok Community Guidelines: Integrity and Authenticity, effective September 24, 2026, checked October 4, 2026.
• Federal Trade Commission Announces Final Rule Banning Fake Reviews and Testimonials, FTC, August 14, 2024, checked October 4, 2026.