Appearance
A team tool to share Android test phones across several computers
In short: BenchFleet Team shares the Android phones on several computers as one fleet. Phones plugged into other computers join through gateways, each person signs in with their own role, owner, operator, viewer or automation, and rights can be limited to chosen phones, groups, apps or workflows. Team costs £20 per seat a month + VAT. Clouds and open-source options are compared below.
Test phones end up spread over the office: a few on each tester's desk, a shelf in the lab, one in the build machine. Sharing them means one list of every phone, a way in for each person with the right access, and no two people or scripts fighting over the same phone. Checked on 23 October 2026 on each tool's own pages. We make BenchFleet.
Free for up to 3 phones, with no account. Pro adds workflows, schedules and AI for up to 25 phones from £12 a month + VAT.
The options compared
| Option | Phones on several computers | Roles and permissions | Where the phones are | Price as seen | Website |
|---|---|---|---|---|---|
| BenchFleet Team | Yes: gateways join other computers' phones to one fleet over an encrypted link | Owner, operator, viewer and automation roles; rights for chosen phones, groups, apps or workflows | Your computers | £20 per seat a month + VAT | benchfleet.com |
| DeviceFarmer (STF) | A shared web UI for devices on the servers you run | Not covered in the facts we checked | Your servers | Free, open source | github.com/DeviceFarmer/stf |
| DeviceLab | Devices on your machines join an organisation | Unlimited teammates on Free; team roles, permissions and SSO on Pro | Your machines, coordinated by its hosted service | Free for one device; then $99 per device a month | devicelab.dev |
| Vysor | Vysor Share sends a link to a device, with screen and ADB access | Not described on its site | Your computer | Pro $2.50 a month; Enterprise $2 per active user a month, 5 users minimum | vysor.io |
| BrowserStack | Not applicable: its own devices | Owner, Admin and User roles in an organisation | Its data centres | Live Team $150 a month billed annually | browserstack.com |
| AWS Device Farm | Not applicable: its own devices; private devices available | AWS IAM policies | AWS data centres | $0.17 per device minute | aws.amazon.com/device-farm |
| TestGrid | Its cloud, or a Custom Device Lab on-premise | Cloud Admin, Team Admin and Team User roles | Its cloud or your site | Starter $249 per seat a month | testgrid.io |
| Genymotion | Virtual devices, on each computer or in its cloud | Business licence per user and workstation | Your computers or its cloud | Desktop Business $479.99 a year; SaaS $0.06 a minute | genymotion.com |
| Firebase Test Lab | Not applicable: Google's devices | Through your Firebase project | Google's data centres; shuts down on 30 September 2027 | $5 per device hour above the no-cost allowance | firebase.google.com/docs/test-lab |
| Appium and Maestro | Frameworks, not sharing tools: each runs tests on the phones its computer sees | None of their own | Each computer | Free, open source; Maestro Cloud $250 per device a month | appium.io, maestro.dev |
How BenchFleet Team shares a fleet Team
- One fleet from many computers. On the Hub's computer, Gateways → Add a gateway makes a one-time code. On the other computer, which has BenchFleet installed and the phones plugged in, run the command the page gives you. The gateway connects out to the Hub over an encrypted link, so it works behind a router and opens nothing on that computer.
- Phones keep who they are. A phone keeps its identity, name and history if it moves to another gateway.
- Work keeps going. Workflows for a gateway's phones run on that computer with the Hub's decisions on approvals and access; if the link drops they finish there, and the results arrive when it is back.
- People and rights. Each person has their own sign-in and role. Rights can cover chosen phones, groups, apps or workflows only, so a contractor can work only on the two phones of one project.
- No fights over a phone. The page always says who is in control; taking over someone else's phone needs a confirmation, and automation leaves a phone alone while a person controls it.
- A record of who did what. Every action is in a hash-chained audit log with the person, phone and result.
On Pro, one person can already use the Hub from a browser on another device, over your own network or a VPN, and API tokens give scripts and CI a role of their own.
Who it is for
- QA teams whose phones are spread over several desks or a lab. See managing a bench of Android test devices.
- Support desks that share company test phones and take over the one a colleague asks about. See remote take-over of company phones.
- Teams with AI agents, where each agent gets its own scope next to the people. See the Android MCP server.
DeviceFarmer, DeviceLab, Vysor, BrowserStack, AWS Device Farm, TestGrid, Genymotion, Firebase Test Lab, Appium and Maestro are the names of their owners' products and projects. BenchFleet is not affiliated with any of them.
Questions
How can a team share Android test phones that are plugged into different computers?
Use a tool that joins those computers into one fleet. In BenchFleet Team, each other computer runs as a gateway with a one-time code and connects out to the Hub over an encrypted link, so its phones appear on everyone's Fleet page with their names, health and history.
Which roles does BenchFleet have?
Owner, operator, viewer and automation. On Team you add people with their own sign-in and role, and give rights for chosen phones, groups, apps or workflows only. API tokens with a role for scripts and CI come with Pro and Team.
What stops two testers using the same phone at once?
The phone page always says who is in control. Taking a phone someone else controls needs a confirmation, and automation never touches a phone a person is controlling.
Can people use the phones from home?
With remote access on Pro and Team, people use the Hub from a browser over your own network or a VPN, with TLS, passwords and two-factor sign-in. Remote sessions cannot run shell commands or change secrets and system settings.
How do device clouds handle teams?
With accounts and roles on the vendor's platform. BrowserStack organisations have Owner, Admin and User roles, AWS Device Farm uses AWS IAM policies, and TestGrid has Cloud Admin, Team Admin and Team User roles. Their devices are in their data centres, not on your computers.
Start with the Free plan
Free for up to 3 phones, with no account. Pro adds workflows, schedules and AI for up to 25 phones from £12 a month + VAT.
- A Free plan with no time limit and no account
- Starts in Local mode, with no telemetry or analytics in the app