Short answer: one person can run a small phone farm if the routine is written down and the alerts are quiet. Spend ten to twenty minutes each morning reviewing what posted and what didn't, do hardware and signing checks weekly, and battery, update and security checks monthly. Build the rack so faults are rare and obvious, and grow only when the current size runs without surprises.
Keep the farm a size you can run
A solo farm fails from attention, not hardware. Before adding phones, check that the current rack runs a full week without you fixing anything more than once. If it doesn't, fix that first.
Choices that reduce work:
- One iPhone model, so settings and stands match. See which iPhone to buy.
- A paid Apple developer account, so there's no weekly re-sign.
- Powered hubs and short data cables, the usual cause of dropouts. See USB hubs.
- Clear labels and one inventory sheet.
- Batch content creation on one day rather than daily.
The routine
The times are rough guides for a small rack, not measurements.
| When | Task | About |
|---|---|---|
| Daily, morning | Read the summary: posted, not posted, refused, uncertain | 5 min |
| Daily, morning | Check uncertain posts on the account profiles | 5 min |
| Daily, morning | Look at any stopped runs' screenshots; fix or park | 5–10 min |
| Daily, evening | Glance at the rack: all phones on, room not hot | 2 min |
| Weekly | Queue the next week's posts | Varies |
| Weekly | Re-sign runners if on a free Apple account | Per phone |
| Weekly | Check account notices in each app | 10–20 min |
| Weekly | Check cables and hub ports on any phone that dropped | As needed |
| Monthly | Battery health, swelling check | 10 min |
| Monthly | Staged iOS/app updates: canary first | Varies |
| Monthly | Review who has access; rotate if anyone left | 10 min |
What to automate, what to keep manual
| Automate | Keep manual |
|---|---|
| Scheduled posting | Deciding what to post and where |
| Warm-up sessions at human pace | Checking uncertain posts |
| Alerts on failures | Replying to comments and messages |
| Daily summary | iOS and app updates |
| Proxy checks | Anything involving account recovery |
Replying to people is yours to do. Don't use comment bots or bought engagement, and don't let the farm speak as someone it isn't.
When something breaks
- One phone down: cable, then hub port, then Auto-Lock — see iPhone keeps disconnecting.
- All phones down: hub power, Mac asleep, or a power cut.
- Runs stopping on one app: probably an app update; check the screenshot and hold updates on the other phones.
- An account warning: stop automating that account and read the notice in the app.
Keep a spare phone and spare cables so the fix is a swap.
Doing this with Farmero
Farmero is built for this kind of routine. It reports what posted, what didn't and what was refused on the Mac and optionally to Telegram or ntfy, marks posts it couldn't confirm as "uncertain" rather than retrying them, and resumes after crashes and disconnects. Drop a clip once and fan it out to the accounts you pick; Farmero warns if the same clip is headed to the same platform twice. Warm-ups can run on a schedule or in smart windows. Setup is in the Mac setup guide; the free trial covers two iPhones for seven days with no card — start here.
Automating these apps may breach their terms, and nobody can promise an account will never be restricted.
FAQ
Can one person run a phone farm?
Yes, at a size where the daily review takes minutes, not hours. Write the routine down and grow only when the current rack runs a week without trouble.
How much time does a small phone farm take each day?
Plan for a short morning review plus weekly and monthly checks. The exact time depends on your rack and how often things break.
What should a solo operator never automate?
Replies to people, account recovery, and decisions about what to post.
When should I add more phones?
When the current setup has run a full week without repeated fixes. See scaling to 50 phones for what changes.