Built for teams that run phones.
Some teams run a phone per account, some a matrix of test devices, some fleets for AI agents or for clients. Underneath it is the same platform: real phone models, a network per phone, snapshots, groups, roles and an API for everything.
Four kinds of fleets.
Pick the one closest to your work. Each page shows the setup, the tools and what it costs; you can mix them in one account.
Multi-accounting
Social, commerce and creator accountsOne account per phone, each with its own model, identity and network exit, run as groups on a schedule.
App and QA testing
Real models, clean runs, CIThe phones your users own, reset to a snapshot before every run and driven through ADB and the API.
Automation and AI agents
Early access for mobile agentsLook at the screen and act through the API, reset to a saved state, and clone as many copies as a job needs.
Agencies and operators
Client fleets, one teamA fleet per client under your own account, operators on the phones they run, and a wall of live screens with Sync.
Shared by every fleet.
Whatever the job, the phones underneath are the same, and so is the way you run them.
Real phone models
150+ models from 11 brands, each built from a snapshot of the real phone and measured against it before anyone can launch it.
Device catalogA network per phone
Mobile, residential, ISP or datacenter exits in the country you choose, or your own proxy. Time zone, language and SIM country follow the exit.
NetworksPersistent, with snapshots
Apps, logins and files survive stops and restarts. Freeze a state, restore it later, or clone new phones from it, each with its own identity.
Snapshots and clonesGroups, schedules, Flows
Run steps and recipes on a whole group with a random stagger, now or by weekday and time, and see the week on one calendar.
API, ADB and webhooks
Every action is a REST call. ADB runs through a relay locked to your IPs, and webhooks arrive signed with HMAC-SHA256.
DocumentationTeam roles and 2FA
Owners handle billing, keys and the team; operators run the phones assigned to them. Invite by email, protect sign-in with an authenticator app.
One price list, every fleet.
Every phone is billed the same way, whatever the model or the job. Traffic is billed per GB by exit type.
Questions, answered.
Something else? Write to support and a person answers, usually within a working day.
Which solution fits my team?
Start from the job. Many accounts: multi-accounting. Testing an app: app and QA testing. Driving phones from code or a model: automation and AI agents. Running phones for clients: agencies and operators.
Can one account run several kinds of fleets?
Yes. Keep them apart with groups, give each teammate only the devices they run, and limit API keys to a list of devices with read or control scope.
Is there a minimum number of phones?
No. Start with one: the first 30 minutes are free, with no card and no top-up. Creating phones is free, and stopped phones cost nothing.
How is a fleet billed?
Per phone: $0.004 a minute while it runs and never more than $0.80 a day, or $12.00 for 30 days running 24/7. Traffic is billed per GB by exit type; your own proxy has no traffic charge. The balance is prepaid, with top-ups from $5 in crypto.
Is there an API for all of it?
Yes. A REST API at https://api.clousd.com/v1 with keys scoped to read or control and to a list of devices. Long operations answer 202 with a job to poll. See the API reference.
Start with one phone. Grow into a fleet.
- The first 30 minutes are free, no card.
- Launch a real phone model in about a minute.
- Add phones, groups and teammates as the work grows.