Start here
Three ways in
If you have never run a cloud phone
Start with the quickstart. It takes you from signing up to a booted device with a bound identity and a verified integrity check, which is the step ninety per cent of "it got banned immediately" tickets turn out to have skipped. Then read the identity guide before you create your second device, because the rules about what can and cannot be regenerated only matter once you already have accounts on a device.
If you are moving an existing fleet
Read the migration guide first. The short version: profiles, cookies, tokens and proxy configuration all transfer, and device identities deliberately do not — the identity you had on a container-based provider is the thing that was getting you flagged. For a mature account the rebuild reads as a device change, which platforms tolerate, rather than a fresh registration.
If you are wiring it into your own stack
Go straight to the API reference. Every screen in the console maps to an endpoint, so anything you can click you can script: device lifecycle, identity management, proxy binding, RPA execution, file transfer and ADB tunnelling. Official SDKs exist for Python, Node and Go, and every event fires a signed webhook.
Getting started
Getting started
Quickstart: your first cloud phone in 5 minutes
Create an account, provision your first PhoneCloudify cloud phone, review the identity, install an app from Play and verify integrity before you register anything.
Migrating from another provider
Import profiles, cookies and proxy config from GeeLark, Multilogin, AdsPower or GoLogin. What transfers, why identities do not, and the side-by-side week.
Still stuck? Ask an engineer.
Median first response on Telegram is under four minutes during business hours.