A real phone, remotely
Tap, swipe, type, and navigate Android in a live browser view. Your allocated phones stay in your workspace.

Real Android devices you control from your browser. Work on one phone, sync a selected group, or save a sequence to run again.
Tap, swipe, type, and navigate Android in a live browser view. Your allocated phones stay in your workspace.
Choose your phones and a main device. Send the same supported actions to the whole group, or return to individual control.
Capture your taps, typing, navigation, and swipes. Review the steps in the RPA builder, then run or schedule the saved workflow.
Create a separate MCP account with expiring, revocable keys. Choose which phones it can view, control, or run workflows on.
Choose your capacity. Availability and subscription details are shown in your workspace before checkout.
$39.99 per phone / month
$26.00 per phone / month
$18.00 per phone / month
$12.50 per phone / month
Phone rental, AI-agent usage, and cloud storage are separate. Proxy service is priced separately unless expressly included in your order.
Once you have a working sequence, save it as a workflow. Replaying saved steps uses your allocated phone and does not consume AI credits.
AI-assisted phone control and cloud drive are being prepared as paid add-ons. Their prices and spending limits will be shown before use.
Record supported actions on your phone.
Review and name the steps that worked.
Run on selected phones or set a schedule.
The current BadAssProxy fleet uses physical Android devices connected to our hosted control service. Models and Android versions vary by device.
No. Deterministic replay of your saved workflow steps has no per-run AI or automation-credit charge. Your phone subscription still applies.
No. The in-app AI agent will be a separately metered add-on. Connecting an external agent through MCP may also incur charges from that agent’s AI provider.
Yes. MCP service accounts have explicit phone permissions and expiring keys. You can revoke their access from the workspace.
No. App layouts, login state, permissions, and network timing can change. Test a workflow on one phone before running it on a group. Login challenges and verification may need your input.
Close the phone’s live control view before workflow execution. This prevents simultaneous controllers from interfering with each other.