Remote phone farm access for teams

A remote phone farm is not a catalog of rented racks. It is this operating model: who is allowed to open a live view, from where, without a LAN story, on phones you already enrolled. Search results mix that idea with a warehouse of phones a vendor owns. FleetDeck today is the first idea.

The warehouse idea (we ship the iPhones) lives on rent cloud iPhones and it is a waitlist. The closet itself — chargers, SideStore, labeling — lives on phone farm. If you blend those three pages into one keyword blob, you get a doorway. They are different jobs.

A lead who keeps the hardware in one city and the people who need to tap it in another. A contractor who should reach two devices and never see the rest. A support pod that takes turns on the same enrolled iPhone without mailing the handset around. A QA group that wants the farm on a night shift without leaving RDP into a desktop that happens to have cables.

It is a poor fit if nobody has bought phones yet and the plan is to “just rent a farm” this week. That inventory is not on sale. It is also a poor fit if the real requirement is stealth. There is no anti-detect mode, no fingerprint theater, and no proxy product hiding behind the live view.

The owner (or an admin) invites a member by email and grants that person specific devices. The member signs in at login, sees only those rows, and opens live view. Input is the same as solo remote phone control: taps, swipes, long-press, typing, plus Android system buttons. Two people should not fight over one device at the same time and expect a clean cursor. Treat a phone like a single seat.

The phone does not call the viewer’s laptop. It calls a FleetDeck relay. Regions include Europe (Nuremberg), the United States, and Asia. “Auto” picks from the device’s country. Viewers must land on the same relay the device already pinned — in-memory frame routing requires that co-location. Pick a region when you enroll and leave it for the shift.

Nothing in that path requires the farm subnet to accept inbound connections. No port-forward, no public ADB, no “put the lab on the internet.” If iPhone touch is started away from the Mac that owns the pairing session, follow the FleetDeck VPN step in install. That VPN is for Apple’s developer services, not a substitute for the relay mesh, and it is not SideStore’s LocalDevVPN.

Remote access does not repeal physics. Android units still need capture consent after some reboots. iPhones still need to be awake, unlocked, and on Wi-Fi or they silently refuse gestures. SideStore still has to refresh 7-day certificates while LocalDevVPN stays on. A free Apple ID still caps each iPhone at three sideloaded apps (Connect + Touch use two). Someone local still has to reseat a charger. The dashboard can tell you a device is offline. It cannot walk into the closet.

Write an on-call note for the room that holds the hardware: which SSID, which power strip, which phones are allowed to sleep (almost none, if you want iOS touch). The remote team’s job is software. The local job is keeping the radios honest. Split those roles on purpose or you will file “FleetDeck is down” tickets that are actually a dead PoE injector.

Teammates see the current screen of devices you assigned. They do not get a recording. Screen frames and input events pass through relays in memory only — FleetDeck does not record, archive, or store screen recordings or screenshots in normal operation, and does not use that traffic to train machine-learning models.

Invite only people who are allowed to see those screens. Least privilege is the product feature: a member who is not attached to a device never sees that row. If a contractor’s job ends, remove the grant. The physical phone stays on your bench.

Billing is by connected phone, not by viewer count. A five-to-10 farm on the Team band is $20 per device per month. Two to four is $25. One phone is $35. Invite the people who need access. You do not buy a second plan just to add a teammate.

At 11 devices you leave self-serve. Enterprise is $500 registration, credited against $2000 setup, on a dedicated server. Same rule as everywhere else: no free tier, no refunds, 3-day grace if a card fails (devices stay online), then devices drop off the account.

Read both if you are starting from zero. Start here if the phones already exist and the pain is distance, time zones, or least-privilege access. Start on phone farm if the pain is that you do not have a reliable bench yet.