> ## Documentation Index
> Fetch the complete documentation index at: https://docs.phoneuse.com/llms.txt
> Use this file to discover all available pages before exploring further.

# What PhoneUse is not

> The boundaries of this surface, so you can rule it in or out quickly.

Most of this site describes what the control plane does. This page describes
what it does not, because finding that out three days into an integration is
expensive and finding it out here is free.

Nothing below is a soft no with a roadmap behind it unless it says so.

## 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`) answer `422 capability_unavailable`. See [The console](https://docs.phoneuse.com/getting-started/console.md).
* **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.

These are deliberate boundaries rather than gaps. Network and identity are
chosen when you buy a phone or set up its proxy, not by the tools that drive
the phone.

## 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`,
  `failed` or `needs_user_control`, and `succeeded` means 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](https://docs.phoneuse.com/cli/ci-cd.md).

Two limits to know:

* **Managed apps only.** Install approved builds from the Console
  [App Store](https://docs.phoneuse.com/guides/upload-app-package.md). 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](https://docs.phoneuse.com/agent/overview.md#what-version-1-does-not-do).

For a managed setup for a larger team,
[book a call with our team](https://cal.com/abdulla-ababakre-wubx6e/phoneuse?overlayCalendar=true) about the Enterprise
plan.

## 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](https://docs.phoneuse.com/getting-started/console.md) and
[Buy and drive a device](https://docs.phoneuse.com/guides/first-device.md).

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 gets `403`.
* **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](mailto:abdulla@phoneuse.com).

There are two ways to pay: **monthly**, billed every 30 days, and **per
minute**, from a prepaid balance. See [Billing modes](https://docs.phoneuse.com/billing/modes.md).

## 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](https://docs.phoneuse.com/billing/spending-controls.md).

## 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 with
`GET /v1/frames/{frameId}`, using a frame id from a run or action receipt.
See [Frame retention](https://docs.phoneuse.com/security/frame-retention.md) 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.

## What it is

Worth restating after all of that. One interface to a cloud Android phone,
with the same tool calls and the same normalized coordinates on every phone. Every action comes back as a receipt you can
look up, every observation can be bound to the frame you decided on, that frame
is still there when you go looking for it, and a retry under the same key
replays its recorded outcome instead of acting twice.

See [Quickstart](https://docs.phoneuse.com/quickstart.md) to start.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.