Summary
ERIUS PHONE is a cloud Android device for AI agents: a real, isolated Android 13 phone or tablet that an agent drives over a plain HTTP API or an MCP server. It reads the screen, taps, types, swipes and installs APKs like a human user.
- From
- $39/monthbilled monthly
- Free tier
- NoVendor states there is no free tier and no free trial. A shared demo phone can be used in the browser for 90 seconds without signup, and early access currently takes no payment and no card because billing is not live yet.
What it does
- Debugs and fixes
- PartlyIt supplies the diagnostic evidence rather than a fix: your agent can pull a screenshot, the UI tree and Android's crash log at any step, but nothing changes your code.
Today your agent pulls a screenshot, the screen's UI tree and the crash log at any step through the API.
eriusphone.com - Writes tests
- NoNo test artefacts are produced: flows are given to the agent as plain-language goals, and the packaged pass/fail QA run is explicitly still unshipped on the Team plan.
Coming soon: goal-based QA runs with reports
eriusphone.com/pricing.html - Done-for-you service
- PartlyYou run your own agent against the API, but during early access the vendor's people set up each device and issue the API key by hand rather than self-serve.
During early access we provision your dedicated Android device by hand and hand you its API key — running in its own isolated environment.
eriusphone.com
How much it does unattended
- Runs autonomously
- PartlyYour agent can run a whole flow unattended over the API, but account sign-ins are a deliberate human step and the agent never gets your credentials.
Account sign-ins (Google and others) are done once by a person, by design. The agent works inside the session you set up and never handles your…
eriusphone.com/docs.html - Multi-agent
- PartlySeveral agents can hold keys and drive separate phones in parallel, but one phone serialises actions and shares snapshot refs between everyone driving it.
UI actions on a device run in order, so a snapshot's refs stay valid for the next tap. Different devices run in parallel. Refs are shared by everyone…
eriusphone.com/docs.html - Agent permissions
- PartlyA key is scoped to its own account's devices and nothing else, but there is no finer control: no IP restriction, no per-action scoping and no expiry.
No self-service keys. You cannot rotate or revoke a key yourself. Keys do not expire on their own, and a key cannot be limited to certain IP…
eriusphone.com/security.html
Which models it runs on
- Claude
- YesThe vendor's own MCP server turns the device into tools for Claude Code and Claude Desktop, so Claude-based agents drive the phone without glue code.
An MCP server that turns your ERIUS PHONE device into native tools for Claude Code, Claude Desktop, Cursor, or any other MCP client.
github.com/Protremix/erius-phone-mcp - Model choice
- YesThe product supplies no model at all: any framework or tool-calling LLM you choose can call the HTTP API, which is how the vendor frames its no-lock-in pitch.
Your agent (any framework — LangChain, custom code, an LLM with tool-calling) decides it needs to do something in a mobile app.
eriusphone.com/ai-agents
Not established: GPT, Open models
Where you use it
- In your editor
- YesThrough the vendor's MCP server the device appears as native tools inside Cursor and the Claude desktop and CLI clients, configured via an mcpServers block.
Put the same `mcpServers` block in `~/.cursor/mcp.json` to use it in all projects, or in `.cursor/mcp.json` for one project.
github.com/Protremix/erius-phone-mcp - On the command line
- PartlyThere is no product CLI; the terminal surface is curl against the HTTP API, plus the MCP package's own stdio executable you install yourself.
This installs an `erius-phone-mcp` command at `~/.venvs/erius-phone-mcp/bin/erius-phone-mcp`.
github.com/Protremix/erius-phone-mcp - In a browser
- YesA hosted dashboard shows your phones live and is where you do the human sign-ins; a shared demo phone is also pokeable in the browser without signup.
Once you have a key, the [dashboard](/dashboard/) shows your phones live: sign in with the same key.
eriusphone.com/docs.html
Not established: In your pipeline
Whose machine it runs on
- Self-hosted
- NoHosted only, and on a single vendor-operated server: devices run in the vendor's Helsinki data centre with no bring-your-own-infrastructure option on any tier.
Everything runs on one server, in a Hetzner data centre in Helsinki, Finland.
eriusphone.com/security.html - Open source
- PartlyOnly the client side is open: the vendor's MCP server package is MIT-licensed on GitHub, while the device platform and API implementation are closed and hosted.
An [MCP](https://modelcontextprotocol.io) server that turns your [ERIUS PHONE](https://eriusphone.com) device into native tools
github.com/Protremix/erius-phone-mcp
What it costs to run
- How it meters
- YesFlat monthly price per device, with the plan deciding how many phones you get; the vendor explicitly rules out per-minute or per-session metering.
Starter and Team are fixed prices for the phone count shown above — no per-minute or per-session metering.
eriusphone.com/pricing.html - Free tier
- PartlyNo free tier and no trial, and signup is by invitation rather than self-serve, but anyone can poke a shared demo phone for 90 seconds without an account.
Not right now. Every phone is a real Android system running in its own container, so each one costs us real compute … You can try a live phone for 90…
eriusphone.com/pricing.html - API access
- YesThe API is the product: one documented JSON over HTTP interface with key auth covering reads, gestures, app install and crash logs, usable from any language.
Every Erius Phone device is driven through one small JSON API for AI agent mobile automation: read the screen, tap, type, swipe, press keys, open…
eriusphone.com/docs.html - MCP server
- YesThe vendor publishes an MCP server over stdio exposing devices, screen reads, gestures, app control and crash logs as tools to any MCP client.
The server speaks MCP over **stdio**. Point your client at `uvx erius-phone-mcp`, or at the `erius-phone-mcp` executable, and pass the environment…
github.com/Protremix/erius-phone-mcp - Bring your own key
- PartlyInference is always yours since the vendor ships no model and the API is plain HTTP, but the device itself cannot run on your own cloud or hardware.
One small JSON API any agent framework can call.
eriusphone.com/about.html
Buying it for a team
- A company can buy it
- YesA Team plan with multiple phones and keys and a custom Enterprise tier exist, and the terms bind the company when you sign up on its behalf.
If you're using it on behalf of a company, you're agreeing for that company too.
eriusphone.com/legal.html - Seat model
- NoBilling counts devices, not people: plans are priced per phone with a fixed device count, and no user seat, seat floor or seat ceiling is published.
Simple plans, priced per phone.
eriusphone.com/pricing.html - Pooled budget
- NoThere is no shared balance to pool: each plan is a flat monthly fee for a fixed number of phones with no metered consumption behind it.
The plan is a flat monthly price per plan, billed in advance, cancel anytime.
eriusphone.com/pricing.html - Admin controls
- NoThere is no administrative layer to constrain the agent with: the API has no admin endpoint or master key, and keys cannot be scoped beyond the account.
The API has no admin endpoint and no master key. Every key belongs to exactly one account.
eriusphone.com/security.html - Audit log
- YesEvery API request is written to an audit log with account, key fingerprint, IP, device and action, though bodies are excluded and retention is not yet fixed.
Every API request is recorded in an audit log so we can operate the service, investigate problems and detect abuse.
eriusphone.com/legal.html - Single sign-on
- NoNo SAML or OIDC anywhere: the dashboard is entered with the API key itself, there is no password and the vendor states no second factor exists.
No second factor in the dashboard. The API key is the only credential.
eriusphone.com/security.html
What happens to your code
- Opt out of training
- YesNothing on your device is used for training at all, so there is nothing to opt out of; the vendor also says it does not log what the agent types.
We don't look through it, analyse it, or use it to train anything.
eriusphone.com/legal.html - Data residency
- PartlyJurisdiction is known but not selectable: every device and volume sits on one server in Finland, with no published alternative region on any tier.
Everything runs on one server, in a Hetzner data centre in Helsinki, Finland.
eriusphone.com/security.html - Getting out
- PartlyYou can email for a copy of your data or for deletion of devices, but export is manual rather than self-serve and no retention procedure is defined yet.
You can ask us for a copy of the account information and logs we hold about you, ask us to correct it, or ask us to delete your account and all of…
eriusphone.com/legal.html - Certifications
- NoNo SOC 2, ISO 27001 or claimed GDPR compliance; the vendor states plainly that it holds no certifications at this stage, while honouring data rights on request.
No certifications. We hold no security or privacy certifications, and we do not claim compliance with any specific regulation.
eriusphone.com/security.html
28 sourced claims on this page. Checked 2026-10-09. How we check.
Sources and updates
The pages we read8
Every fact below comes from the vendor. Nothing here is independently corroborated yet.
Updates1
- Capabilities · Commercial terms · Free tier · Price
