Driving a phone does not change its network or identity
This surface drives a device. The tools that drive it do not change how that device appears to the software running on it.- A proxy is not set by a device tool. You cannot select an exit address
or a network route through the device or MCP tools. Managed proxies are on the
roadmap and not offered yet. The console keeps its Proxy page, and while
proxies are off the proxy routes (
POST /v1/proxy-operations,GET /v1/devices/{deviceId}/proxy) answer422 capability_unavailable. See The console. - Phone identity is chosen when you buy. A Real phone identity cloud phone is a named phone model (a Pixel, a Galaxy) that you pick when you buy it. No tool on this surface writes a phone’s identifiers or changes its model after that.
- No account isolation features. Nothing here is built to keep separate accounts from being associated with each other.
It runs your tests on cloud phones
PhoneUse can do test automation. Your test runner or CI takes a phone, acts on it and reads back what happened, and every action comes back as a receipt, so a test can check what the device actually did. A few pieces come from your own tooling rather than from PhoneUse:- Your test code makes the pass or fail call. A run reports
succeeded,failedorneeds_user_control, andsucceededmeans the worker reported the goal reached. For a strict verdict, check the screen or the receipts in your own test code. - Your CI decides when and where tests run. One call addresses one device, and there is no built-in schedule. Start sessions or runs from your CI or cron, one per phone, to cover several phones. See CLI in CI.
- Managed apps only. Install approved builds from the Console App Store. Customer APK uploads, custom app libraries and arbitrary URL installation are retired. Installation history and the apps currently on a phone remain readable.
- No run that survives a restart. See Agent tier.
It does have a self serve entry
You can sign in, buy a device, drive it from a browser and mint an API key, without talking to anybody. See The console and Buy and drive a device. Two things are genuinely narrower than “self serve” suggests, and both are boundaries rather than gaps:- Buying needs an org admin. An admin buys from a signed in session, or
grants an API key
orders:place, and a person still pays on the Checkout page. A member cannot commit the org to a purchase and gets403. - Nothing is returned online. Devices are not returned and payments are not refunded online. On a monthly phone, Cancel order on the console’s Billing page stops the next charge. For anything else, write to abdulla@phoneuse.com.
It has no spend cap you can set
There is no dollar limit you can set. The limits that do stop something are a per minute phone’s prepaid balance, the lease expiry and a run’s own budget, and they are collected on Spending controls.It does not video record a session
Frames can be archived when the deployment has frame storage configured. The default archive policy has no automatic expiry; an organisation can have a different configured policy. Read one available frame withGET /v1/frames/{frameId}, using a frame id from a run or action receipt.
See Frame retention for storage, access and
retention limits.
The archive holds individual captured frames. It is not a video or a scrubbable
timeline, and it does not record anything the agent did not look at: a frame
exists because something asked for one. Continuous screen capture is not what
this is.