One account. One phone.
Give every account a cloud phone of its own: a real model, its own identity, its own network exit and storage that persists. Then run the whole fleet from one place, with your team, on a schedule.
GB · Mobile
US · MobileGB · Residential
DE · ISPDE · ResidentialUS · DatacenterWhat every phone brings.
Accounts stay separate because their phones are separate. Every phone arrives with all of this, and keeps it between runs.
A real model
150+ models from 11 brands, each built from a snapshot of the real phone: fingerprint, sensors, graphics and screen.
Its own identity
A serial, IMEI, phone number and Wi-Fi details of its own. A new identity is one call, or set just the fields you need.
Its own network exit
Mobile, residential, ISP or datacenter in the country you choose, or your own proxy. Rotate the address on demand or on a schedule.
Its own locale
SIM country, time zone, language, keyboard and store follow the exit, so every phone is consistent with its market.
Your team, on the right phones.
Two roles, set per person. Owners run the account; operators run the phones they are given and nothing else.
- OwnersBilling, API keys, the team, and creating or deleting phones.
- OperatorsStart, stop and restart, apps, groups, snapshots, network and ADB, on the devices assigned to them.
- Invite by emailA teammate joins on their first sign-in; their access is the list of devices you give them.
- 2FA and trusted browsersSign-in protected with an authenticator app, on browsers you trust.
Do it once, for the whole fleet.
Pick a group and act on every phone in it: start or stop, install an app, change the network, or run a chain of steps with a random stagger between phones. Put it on a weekly schedule and it runs by itself.
Ready recipes for Instagram, TikTok, Facebook, Threads, YouTube, Reddit, X and Snapchat; generic steps for everything else. Recipes per app
Accounts and media in one place.
Resources stores the accounts, each linked to its phone, and a Media library of photos and videos that publish steps take from. Paste accounts in bulk in the layout you already have; passwords and 2FA keys are stored encrypted.
Set up once. Clone the rest.
Get one phone exactly right, snapshot it before anyone signs in, and clone as many new phones from it as you need. Each clone gets its own identity.
- Restore any timeRoll a phone back to a snapshot in one step.
- Nightly backupsSnapshot phones every night on a schedule.
- Stopped phones are freeA phone waiting for its next run keeps its state and costs nothing.
Cost at scale.
Every phone is billed on its own: per minute while it runs, or monthly when it never stops. Below about 100 minutes a day per phone, per minute is cheaper; above that, the monthly plan wins.
| Phones | 30 min a day | 1 h a day | Always on |
|---|---|---|---|
| 10 phonesone account each | $36.00per minute | $72.00per minute | $120.00monthly plan |
| 50 phonesone account each | $180.00per minute | $360.00per minute | $600.00monthly plan |
| 100 phonesone account each | $360.00per minute | $720.00per minute | $1,200.00monthly plan |
| 500 phonesone account each | $1,800.00per minute | $3,600.00per minute | $6,000.00monthly plan |
For 30 days, Android 12–14, before traffic. Android 15 costs 10% more, 16 and 17 cost 25% more. Creating phones is free.
Guides by app.
How separation, recipes and costs work for each of the apps teams run most.
Multiple TikTok accounts
Mobile exits and a SIM country per market, warm-ups and posts on a schedule.
Read the guideMultiple Instagram accounts
Bulk-add accounts, sign them in by recipe, post from one Media library.
Read the guideMultiple Reddit accounts
A clean residential, mobile or static exit per account, and a sign-in recipe.
Read the guideMultiple Telegram accounts
One number per phone, sessions that persist, a wall of live screens.
Read the guideMultiple Facebook accounts
Accounts and pages kept apart, sign-in through Instagram, six recipes.
Read the guideMultiple YouTube channels
A phone per channel, uploads from one library on a weekly calendar.
Read the guideQuestions, answered.
Something else? Write to support and a person answers, usually within a working day.
Why one account per phone?
Because a phone is where an account’s identity lives: the model, serial and IMEI, the network exit, the SIM country and the storage. With one account per phone nothing is shared between accounts, and each one stays consistent from day to day.
Can operators see all our phones?
No. An operator sees and runs only the devices assigned to them. Billing, API keys, the team and creating or deleting phones stay with owners.
How do accounts get into Resources?
One by one, or in bulk: paste a list with one account per line in the layout you have (login, password, email, email password, 2FA key and more), pick the separator, and link each account to its phone.
What does a phone cost when it is not running?
Nothing. Stopped phones are free and keep their apps, logins and files. Creating a phone is free too; see pricing.
Can I use my own proxies?
Yes, SOCKS5 or HTTP, per phone, with no traffic charge from us. Check a proxy before attaching it: IP, country, city, ISP, mobile or hosting, and response time.
Does multi-accounting on Clousd change platform rules?
No. Clousd keeps accounts organised, separate and consistent; it does not change what any app allows. Run each account within the terms of the app it belongs to.
Start with one account and one phone.
- The first 30 minutes are free, no card.
- Give the first account its phone, exit and country.
- Add phones, groups and teammates as the fleet grows.