Use cases
Give each active project a recognisable Android home for its apps, sign-ins, links, and notes. Begin with one cloud phone for one project, then separate projects when their mobile setups genuinely differ.
Choose the useful size
Essential fits one project with several compatible apps. Plus fits two or three active projects that need different setups; Workspace is for a larger project portfolio with a clear purpose for each device.
Essential · 1 cloud phone · $9.99/month
Place a project’s messaging, task, and research apps on one Android cloud phone you can return to in your browser.
What this setup gives you
Essential · 1 cloud phone · $9.99/month
Keep a single campaign’s Snapchat routine and supporting mobile tools together.
What this setup gives you
Plus · 3 cloud phones · $26.99/month
Use distinct cloud phones when ongoing projects need different app sets or account sessions.
What this setup gives you
Workspace · 25 cloud phones · $63.99/month
Use Workspace when four to 25 active projects each call for their own Android setup.
What this setup gives you
Once a use case has a clear outcome, decide which work deserves its own persistent Android environment and follow the workspace organisation method. Those steps connect the one-, three-, or 25-device examples to a register you can review as projects change.
That external register can name a responsible person, but it does not create built-in user roles, granular permissions, audit logs, or simultaneous shared access. Before planning a handoff, ask support to confirm the available access method and keep credentials outside the project record.