From proxy checks and device initialization to live control, group control, files, and apps, CloudTon brings the device workflow into one team workspace.
✓Registration creates a team and 5 GB drive. No paid resource is created automatically.New users can bring their first device online in five guided steps without learning every team, pool, or billing concept first.
Devices, network, files, apps, members, and billing share one team context, with centralized status and recovery.
Purchase, initialize, and control Android cloud phones in the browser, with image, proxy, simulation, billing, and task state in one lifecycle.
Choose one master device and synchronize human touch, navigation, and text input to a group of running devices.
Store, manually check, group, and assign SOCKS5/HTTP proxies, with optional CloudTon dynamic proxy plans.
Keep devices, proxies, files, apps, billing, and logs within team boundaries, with role and device-scoped access.
Keep files in a private team drive, then deliver cached files to 1–200 selected cloud phones.
Create an app catalog from Team Drive APKs, then install, uninstall, start, stop, or restart across authorized devices.
Open temporary online ADB access for authorized devices and debug alongside live control, screenshots, and image metadata.
Capabilities are organized around outcomes, without pretending to provide unattended automation or exposing infrastructure jargon.
Create isolated mobile environments for stores, markets, and regions while keeping proxies, devices, assets, and team access in one operating path.
Learn more →Manage isolated mobile environments, regional proxies, apps, and access for different accounts, then control one device or a group from the browser.
Learn more →Organize device environments by campaign, market, and member to review mobile landing pages, apps, and assets from different regions.
Learn more →Run hands-on validation across Android images, screens, regions, and networks, supported by ADB, screenshots, and file delivery.
Learn more →Use verified proxy exits and isolated mobile environments to manually inspect ads, app stores, and account settings in target markets.
Learn more →Device environments are purchased by quantity and term. Runtime then uses slots, minute packs, or pay-as-you-go billing. Final prices always come from an authenticated server quote.
Permissions are verified on every request, credentials are encrypted, batch results stay per-device, and unknown create outcomes are reconciled instead of blindly retried.
Wallets, devices, proxies, files, apps, and logs stay inside team boundaries.
Proxy passwords and refresh URLs are encrypted and masked in normal responses.
Callbacks, polling, idempotency, and safe retry rules prevent blind duplication.
Create a workspace, then follow the guided proxy, check, purchase, initialize, and boot flow.
