Could you give me more details about Genymotion Cloud, like pricing and how to set it up?
**Genymotion Cloud (SaaS) – Pricing & Setup Overview**
| Item | Detail |
|------|--------|
| **What it is** | A cloud‑based Android emulator that runs in the cloud and can be accessed from any browser or CI tool. No local virtualization required. |
| **Core pricing** | **$0.05 per minute per active virtual device** (pay‑as‑you‑go). |
| **Default usage** | Up to 2 virtual devices can run simultaneously in the free trial; after that you pay $0.05/minute/device. |
| **Other plans** | *Unlimited* (predictable monthly/annual fees for continuous use) and *Premium* (custom enterprise‑ready). See the blog for details:
| **Device types** | ARM64 and x86 devices, covering Android 5.1 to 15.0. |
| **Integration** | Native CI/CD support (GitHub Actions, CircleCI, Bitrise, Jenkins, Detox). |
| **Billing** | Credit‑card based, no long‑term commitment. Manage via the “Administration → Billing” panel. |
| **Setup steps** | 1. Sign up at
2. From the dashboard click **Start plan** and choose *Pay As You Go*.
3. Enter billing address & credit‑card info.
4. Click **Start Plan** to activate.
5. Back in the dashboard click **Virtual Devices** → **Start** on the recipe you want. |
| **How it works** | You create a “virtual device” recipe (Android version, device model, etc.). The cloud runs that image on a virtual machine (AWS, GCP, Azure, Alibaba). You then connect to it via the web UI or API. |
| **Why choose Cloud?** | • No need to enable VT‑x/AMD‑V on your PC.
• Run tests from any machine, including CI servers.
• Scale to many devices instantly. |
| **Limitations** | • Requires internet connectivity.
• If you need on‑premise or private‑cloud deployment, see Genymotion for Cloud Providers. |
> **Quick tip:** For most developers, the *Pay As You Go* plan is perfect—just $0.05/minute per device, with no monthly fees, and you can shut down a device anytime to stop billing.
---
**Next step:**
Would you like help creating a Genymotion Cloud account, or do you need guidance on how to integrate the emulator into your CI workflow (e.g., GitHub Actions or Jenkins)?