Rent real Android phones, not emulators.
Dedicated physical phones that stay in our racks. Drive yours from a browser, REST, ADB or MCP.
- Physical phone hardware
- One customer per device
- Browser · REST · ADB · MCP
- Month-to-month
- Acceptable Use Policy enforced
Yes, you can rent a real Android phone online without buying one. PhoneFleet keeps a dedicated physical phone in its rack and you control it over the internet: live in a browser, through a REST API, over ADB or via MCP for AI agents. Nothing is shipped, it's never shared, and you pay per device, month-to-month.
Four ways into the phone you rent
Bay 07 is yours. Watch and drive it in a browser tab, script it over REST, plug in the adb you already use, or hand it to an AI agent through MCP. All four reach the same device.
Pick a port to see a session.
Session: only you
# Grab the screen, then tap the button you foundcurl https://api.phonefleet.dev/v1/devices/pf-r03-07/screenshot \ -H "Authorization: Bearer $PHONEFLEET_KEY" -o screen.png curl -X POST https://api.phonefleet.dev/v1/devices/pf-r03-07/tap \ -H "Authorization: Bearer $PHONEFLEET_KEY" \ -d '{ "x": 540, "y": 1620 }' { "device": "pf-r03-07", "status": "ok" }
$ adb connect 127.0.0.1:15037 # local end of your tunnelconnected to 127.0.0.1:15037$ adb install -r build/app-release.apkPerforming Streamed InstallSuccess$ adb shell am start -n com.example.app/.MainActivityStarting: Intent { cmp=com.example.app/.MainActivity }$ adb exec-out screencap -p > first-run.png$ adb shell getprop ro.kernel.qemu # empty: not an emulator
// Add PhoneFleet to your MCP client"phonefleet": { "url": "https://mcp.phonefleet.dev", "headers": { "Authorization": "Bearer $PHONEFLEET_KEY" } } // What your agent callsscreenshot(device: "pf-r03-07") → imagetap(device: "pf-r03-07", x: 540, y: 1620) → oktype_text(device: "pf-r03-07", text: "hi") → ok
What you get with each rented phone
A real device on a rack shelf, kept powered and online, that only your account can reach.
- Device
A physical Android phone
Phone hardware running Android, in a rack bay with its own power and network. Need a particular Android version? Ask when you reserve and we'll tell you what we can provide.
- Access
One customer per device
Nobody else gets a session on your phone while you rent it. Apps, logins and files stay where you left them, and we don't reset it unless you ask.
- Control
Four ways in
A live screen in your browser, a REST API, ADB over a secure tunnel, and an MCP server for AI agents.
- Apps
Install what you're allowed to run
Use the Play Store, or push your own APK over ADB or the API.
- Upkeep
We look after the hardware
Power, cooling, networking and replacements are our problem. If a device fails, we swap it.
- Region
Tell us where you need devices
We'll confirm the region we can serve you from before anything is billed. Need a SIM or mobile data? Ask when you reserve and we'll tell you whether we can provide it.
- Billing
Per device, month-to-month
Release devices at the end of any billing cycle. Early-access customers get founding pricing, sent to you before you pay anything.
Who rents a remote Android phone
People who need an app to behave exactly as it does on a phone, without keeping a drawer of phones charged.
AI-agent builders
Give your agent a phone it can see and touch through MCP or the API. It uses the same app your users do, on the same kind of hardware, and stays logged in between runs.
- Agents that operate Android apps
- Evaluating agents on real apps
- Long jobs on one persistent device
App developers and QA
Test on real hardware without buying, charging and replacing test phones. Point your CI at the device over ADB, as you would a phone on your desk.
- Release smoke tests
- Bugs that only show up on hardware
- Install, upgrade and permission flows
Automation and ops teams
Run mobile-only workflows around the clock on phones nobody has to babysit. Agencies can run the client app accounts they're authorised to manage.
- Mobile-only internal workflows
- Client app accounts you're authorised to manage
- Watching your own app in production
Check it's real yourself
"Real phone" gets stretched a lot. Some services mean a handset, some mean Android running on a server, and some say outright that their phones run without any hardware.
Wondering how this compares with a virtual device? Read real phone vs cloud phone. You don't have to take our word for it. Once you have ADB, ask the device. Emulators report themselves through system properties like these; a phone on our rack doesn't.
Not convinced by what you see? Release it. Plans are month-to-month.
$ adb shell getprop ro.kernel.qemuemulator1rented phone(empty)$ adb shell getprop ro.hardwareemulatorranchurented phone<the phone's chipset>$ adb shell getprop ro.product.manufactureremulatorGooglerented phone<the phone's maker>$ adb shell getprop ro.boot.qemuemulator1rented phone(empty)
Renting a device vs borrowing a session
Most "real device" services lend you a phone for a session, then reset it for the next person. That suits a quick test. It doesn't suit an agent that runs for hours or an app that needs to stay logged in.
| Question | PhoneFleet rental | Shared testing clouds | Free device labs | Virtual cloud phones | Your own rack |
|---|---|---|---|---|---|
| Physical phone hardware | Yes | Yes | Yes | No | Yes |
| Same device, every day | Yes, all month | Per session | Per session | Yes | Yes |
| Apps and logins persist | Yes | Reset between users | Reset after each session | Yes | Yes |
| Runs unattended for hours | Yes | Idle timeouts | Time-limited | Yes | Yes |
| Control | Browser, REST, ADB, MCP | Browser, test frameworks | Android Studio or browser | Browser, API on paid plans | Whatever you build |
| Hardware to buy and maintain | None | None | None | None | All of it |
| You pay for | Each device, monthly | Each user, or device minutes | Nothing (time-capped) | Profiles plus minutes or rentals | Phones, hubs, power, your time |
Shared testing clouds: BrowserStack App Live, AWS Device Farm (pay as you go). Free labs: Google's Android Device Streaming, Samsung Remote Test Lab. Virtual: cloud-phone services such as GeeLark. Based on each provider's public pages, October 2026; AWS also sells private dedicated devices through sales, from $200 per month. Price your own rack.
What a racked phone can't do, and what we won't allow
The phone lives on a shelf, not in a hand. Nobody points its camera at things, carries it around or taps a card on it. If your work depends on camera input, location changes, calls or SMS, ask before you reserve and we'll tell you straight whether it fits.
Real phones on real networks only stay useful if they're used honestly. The full rules are in our Acceptable Use Policy; accounts that break them may be suspended without refund.
- YesTesting your own apps and the apps you're paid to test
- YesAgents working apps and accounts you're allowed to automate
- YesManaging accounts you own or are authorised to run
- NoFraud of any kind: ad, click, payment or identity
- NoSpam, fake engagement, bought followers or reviews
- NoImpersonation, phishing, or anything that breaks the law
Renting an Android phone: questions
Can I rent an Android phone online for development or testing?
Yes. You rent a physical Android phone that stays in our rack, and you control it over the internet from your browser, the REST API, ADB or MCP. It's built for developers, QA teams and AI agents. It isn't a rent-to-own handset and nothing is shipped to you.
Is it a real phone or an emulator?
A real phone. Every device is physical phone hardware running Android, not an emulator or a virtual instance on a server. Once you have ADB access you can check this yourself with the system properties shown on this page.
Is the device shared with anyone else?
No. Each phone is rented to one customer at a time. Your apps, logins and files stay on it between sessions, and we only reset it if you ask.
How do I connect to the phone?
Four ways: a live screen in your browser, a REST API, ADB over a secure tunnel, and an MCP server that AI agents can call directly. Use whichever fits; they all control the same device. API documentation goes to early-access customers.
Can an AI agent control the phone?
Yes. Point your MCP client at the PhoneFleet server and your agent gets tools to see the screen, tap, type and launch apps on your device. Agents that don't speak MCP can use the REST API instead.
Why rent a phone when Google and Samsung offer free remote devices?
Free device labs and shared testing clouds lend you a phone for a time-limited session and reset it afterwards. That's fine for a quick check of your own build. A rented PhoneFleet phone is yours all month: it stays logged in, keeps your setup, and can run unattended for hours.
How much does it cost to rent an Android phone?
Pricing is per device, per month, with no long contract. We're confirming early-access prices now; founding customers get them before anything is billed, and keep them locked in. Reserve devices to get the numbers first.
Can the phone use a SIM card, camera or GPS?
The phone sits on a rack shelf, so anything that needs it to be moved, pointed at something or handled won't apply. If your work depends on camera input, location changes, a SIM, mobile data, calls or SMS, ask when you reserve and we'll tell you whether we can provide it.
Where are the phones hosted?
Tell us the region you need when you reserve. We'll confirm where we can serve your devices from before you're billed.
What happens to my data when I stop renting?
When you release a device, we wipe it and set it up fresh before anyone else can rent it. Copy off anything you want to keep before the end of your billing cycle.
What isn't allowed?
Fraud, spam, fake engagement, impersonation and anything illegal. The full list is in our Acceptable Use Policy. Accounts that break it may be suspended without refund.
Reserve your phones.
Tell us how many devices you need and what they're for. We'll come back with what we can provide, the region, and founding pricing.
Month-to-month · One customer per device · No payment to reserve