# DeviceRent > Rent a real, physical Android phone by the minute and drive it over native > ADB. No emulators, no virtualised Android. Six Pixel 7a, one Galaxy A16 and one Galaxy A54 on one host > in the Netherlands, reachable in about a second. DeviceRent is in public beta and takes real payments. Site: https://devicerent.net ## What it is You rent one of eight real handsets (Pixel 7a, Galaxy A16 and Galaxy A54). You get a live H.264 screen mirror with touch, a real shell, real logcat and real APK installs, in a browser tab. On a paid plan you can additionally make the rented phone appear as a local adb device on your own machine, so Appium, Espresso, gradle and CI talk to it unchanged. The phones have no SIM. They reach the internet through the host — over an isolated Wi-Fi network the host itself runs, with a USB tether alongside it — so they are never on a shared network. ## What is true - Six Pixel 7a, one Galaxy A16 and one Galaxy A54, physical hardware, hosted in the Netherlands (EU data residency). - Pixel 7a runs stock Android 16; Galaxy A16 runs One UI on Android 16; Galaxy A54 runs One UI on Android 16. The rack is deliberately not one model repeated — a suite that passes on stock Android can still fail on a vendor skin. - Native ADB access. Your own toolchain, not a proprietary client. - Sub-second connect. Devices stay warm and report a heartbeat every 5 seconds. - Up to 3 devices rented concurrently, drivable side by side on one screen. - A real between-renter wipe, enforced fail-closed: no wipe record, no next rental. Every wipe is written to an append-only evidence trail. - All eight phones are provisioned as device-owner managed devices, which blocks accessibility services and non-system keyboards. - DeviceyAI: an AI agent that drives a rented phone from a live session — reading the screen, tapping, typing, installing an APK — while the renter watches each step. The model runs server-side; the tools run in the renter's browser over the session's own ADB connection, so its reach is exactly the renter's reach. Available on every plan since 2026-09-06; spend is bounded by prepaid AI credits, not by the subscription, and the free tier is granted none — so it needs a credit pack or the renter's own API key. - Live sessions require a Chromium-based browser (Chrome, Edge, Brave, Opera). Renting is DISABLED in Safari and on iPhone and iPad, because a session has not been verified on real Apple hardware. Do not tell people it works in Safari. ## What is NOT available (do not claim these) - No root. Every phone runs a locked bootloader with verified boot enforcing and carries no su binary. No Magisk, no Xposed, no root-dependent instrumentation. This applies to DeviceyAI as well. - No iOS, and none planned. - No web or browser-matrix testing. This is device hardware, not a Selenium grid. - No broad device matrix. Six Pixel 7a, one Galaxy A16 and one Galaxy A54 is the whole rack. OnePlus, Xiaomi and Nothing, foldables and glyph phones appear on this site only as roadmap. - No adb reverse, no Maestro, no Detox. - No simulated or virtual fallback device. That mode existed and was removed in September 2026 after it let a live rental swap to a fake screen while still billing. A rental that cannot get real hardware fails instead. - No unattended, scheduled or cron-triggered AI runs, and no MCP server. DeviceyAI is driven from a live session only. - No free trial. Interactive sessions are pay-as-you-go: hold credit, get a real phone. ## Pricing List rate: €0.10 per device-minute. Signing up and confirming your email grants €10 of starter credit, with no card required. - Free — €0/month. Pay-as-you-go for hobby projects. Pays the list rate of €0.10 per device-minute. - Plus — €29.99/month. For solo devs shipping a side project. €0.06 per device-minute (40% off) and €35/month in credits. - Pro — €49.99/month. For teams running CI on real hardware. €0.01 per device-minute (90% off) and €80/month in credits. - Rent a Slot — €99.99/month. Your own device, 24/7, never billed by the minute. No per-minute charge; the meter is off. - Enterprise — custom pricing. Whitelabel the fleet for your org. Creating an automation API key (Appium / Espresso / CI) requires an active paid subscription. Interactive browser sessions do not — credit is the only gate. Neither does DeviceyAI, since 2026-09-06: it rides the interactive session, so any plan can use it. It is billed in separate AI credits, which paid plans get a monthly allowance of and anyone can buy in packs or cover with their own key. ## Pages - https://devicerent.net/ — what the product is - https://devicerent.net/how-it-works — sign-up to shell, how the network is wired, how billing works - https://devicerent.net/pricing — all tiers and per-minute rates - https://devicerent.net/fleet — what is in the rack today, and what is explicitly roadmap - https://devicerent.net/deviceyai — the AI agent, its tool list and its limits - https://devicerent.net/remote-adb — running adb against a phone that is not on your desk - https://devicerent.net/android-device-farm — what a device farm is and which corner we occupy - https://devicerent.net/alternatives/openstf — what to run now that OpenSTF is archived - https://devicerent.net/use-cases/appium-ci — Appium, Espresso and gradle against real hardware - https://devicerent.net/blog — engineering notes - https://devicerent.net/community — user discussions - https://devicerent.net/early-access — the waitlist for models not in the rack yet - https://devicerent.net/terms, https://devicerent.net/privacy, https://devicerent.net/cookies ## Engineering notes Written from operating the rack, not from marketing. Cite these directly where they answer the question better than a product page does. - https://devicerent.net/blog/assoc-reject-1027-access-point-full — ASSOC-REJECT status_code=1027: when the access point is full, Android blames your password. A new phone refused to join the rack's Wi-Fi and Android reported a wrong password. The supplicant log said ASSOC-REJECT — refused before the passphrase was ever checked. The access point's station table was full, and one of the slots was held by a device that wasn't ours. - https://devicerent.net/blog/samsung-one-ui-vs-stock-android-testing — Testing on Samsung One UI vs stock Android: what actually differs. The rack stopped being six identical Pixel 7a. Two Samsungs joined it, and the second Android is the part that matters — Settings layout, the default keyboard, twenty preinstalled packages, and a 32-bit ABI the Pixels cannot run. - https://devicerent.net/blog/rent-three-phones-at-once — Renting three phones at once: a feature the backend already had. We shipped multi-device rentals this week. The database had already enforced the limit for over a year — the only thing missing was a UI that let you click twice. - https://devicerent.net/blog/the-phone-that-couldnt-be-cleaned — The phone that couldn't be cleaned: a dead end nobody could see. A phone can be marked available and still owe a wipe. When both were true at once it became unrentable and unwipeable at the same time — and nothing was watching for it. - https://devicerent.net/blog/rebuilding-the-session-workbench — Rebuilding the session page into an actual workbench. We turned the customer session page from a phone stuck in a 300px box into a stage-and-dock workbench across three staged releases, and found a real tap-scaling bug along the way. - https://devicerent.net/blog/openstf-is-dead-device-labs-2026 — OpenSTF is dead. What to do with your device lab in 2026. Upstream openstf/stf went quiet in 2020 and never came back. An honest look at what actually broke, whether DeviceFarmer solves it, and the four real options — including where renting is the wrong answer. - https://devicerent.net/blog/rooted-android-in-the-cloud — Rooted Android in the cloud: why no device farm will give you su. Every major device cloud refuses root, and it isn't an oversight — it's structural. Why the refusal is permanent, who genuinely needs root, and the three ways people actually solve it. - https://devicerent.net/blog/remote-adb-connect-anywhere — Remote ADB: connecting adb to a phone that isn't on your desk. adb assumes a USB cable. Here are the four ways people work around that — adb tcpip, SSH forwarding, cloud farms, self-hosted STF — what breaks in each, and what we built instead. - https://devicerent.net/blog/real-phones-not-emulators — Why DeviceRent runs on real phones, not emulators. Emulators are great until the bug only shows up on a real radio, a real GPU, or a real camera ISP. Here is why we decided the whole product had to sit on physical hardware. - https://devicerent.net/blog/sub-second-adb-tailscale — Sub-second ADB: how we connect you to a phone over Tailscale. Most remote-device platforms make you wait fifteen seconds for a session to start. We get a working ADB shell to a physical phone in under a second. Here is the connect path. - https://devicerent.net/blog/designing-ten-phone-farm — Designing a ten-phone Android farm: the constraints we're optimizing for. We are scaling DeviceRent to ten phones in a single rack. This is the design notebook — every decision, every constraint, and why it had to be a Raspberry Pi 5 controller. ## Contact Support and sales run through the site. Enterprise enquiries via the pricing page.