Cloud Android phones where AI agents test, click and type like a person. No devices to buy or emulators to maintain.
Click a row. The phone runs it live in your browser.
These run on a simulated phone. On AkaPhone the same tasks run on real cloud Android via ARTEMIS.
Point Claude Code, Codex or Cursor at a phone through MCP. The agent installs the build, taps through flows and reads results back.
Open the console, type a task in plain English, watch the phone do it live, take over with a tap, and download the video.
Launch a phone. Pick a screen size, or start from a snapshot.
Give it a task. From your coding agent over MCP, from CI, or typed into the console.
Get proof. Video, screenshots and a step trace for every run. Snapshot the device for next time.
Launch phones, run tasks and watch them live in your browser. Tap, type or install an APK yourself at any point.
Give every agent its own phone. Create and control them through the REST API, or from your coding agent over MCP.
Phones keep running while your agent works and stop on their own after 30 idle minutes, so a forgotten device never burns credits.
Every agent gets its own virtual phone with its own network, storage and identity.
Freeze a logged-in device once, then clone it in one tap or start every CI run from it.
Pixel 8, a small phone and a Pixel Tablet, all on Android 14. Change locale or theme on the device like a person would.
Run up to 3 phones at once on pay as you go, or 5 on Team. Each one is billed by the minute.
Buy credits up front and they never expire. Devices stop when credits run out, so there is never a surprise bill.
Works with
Start free. Then buy prepaid credits; 1 credit is one device-minute and credits never expire.
Give your agent a
60 free minutes, then prepaid credits at about $0.04 per device-minute: 250 minutes for $10, 1,375 for $50 or 6,000 for $200. Team is a one-off $199 pack with 6,000 minutes plus 5 parallel devices for 30 days. No subscription, and credits never expire. A five-minute test run costs about 20 cents.
The agent that drives the phone is Google's open-source ARTEMIS, unmodified and credited. What we add is the part that is tedious to run yourself: a fleet of warm Android devices, snapshots, parallel runs, artifact capture, an MCP server, a console, and billing.
No. The web console lets you create a device, type a task, watch it run and download the video. Developers get the same thing as MCP tools in their coding agent and as a REST API for CI.
Yes. Gemini, Claude or OpenAI. We bill device time, not tokens.
It is never stored. It is sent with each task request (from the console, or from your MCP config), held in memory only by the worker that runs that task, and never written to a database, log or trace. In the console it stays in your browser.
Not today. Devices are emulators without Google Play Services, so apps that require Play Store or Play Integrity will not install from the store. You can install any APK directly. Physical devices and Play-enabled images are on the roadmap.
Automating third-party accounts you do not own, creating accounts in bulk, scraping, ad or review fraud, bypassing rate limits or CAPTCHAs, and anything that violates another service's terms. Devices run in isolated networks and new accounts are rate-limited. Abuse ends the account without refund.
A fresh device is usually ready in under ten seconds; from a snapshot, faster. Each step takes a few seconds depending on the model. A typical fifteen-step test finishes in two to four minutes.
Yes. The REST API starts a device, runs a task and returns pass or fail with the artifacts, so a GitHub Action or GitLab job can block a release on a failed flow. Parallel devices are billed per device-minute like everything else.
60 free device-minutes. No card. Works from Claude Code, Codex, Cursor or a browser.