> For the complete documentation index, see [llms.txt](https://docs.devicecloud.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devicecloud.dev/readme.md). # Welcome to DeviceCloud DeviceCloud is a third-party Maestro Cloud alternative. Reasons to switch: * Cheap unit-based pricing * Up to 100 parallel runs * Twice as fast as Maestro Cloud for half the cost * Google Play APIs * Tablets and iPads * Fast support response times (via Discord or Slack Connect) ## Try it The CLI is intentionally designed to mimic the Maestro Cloud API, so in most cases the migration is one line: ```bash # before maestro cloud --apiKey # after dcd cloud ``` Start with the [Quick Start](/getting-started/quickstart.md) to install the CLI and run your first flow. ## Quick links ### Get started * [Quick Start](/getting-started/quickstart.md) - install the CLI and run your first flow * [Authentication](/getting-started/api-keys.md) - `dcd login` locally, API key in CI * [Flows & Workspaces](/getting-started/flows-and-workspaces.md) - run a single file, a directory, or a whole workspace * [Devices & OS Versions](/getting-started/devices-configuration.md) - every supported device, Android API level and iOS version ### Run in CI * [CI/CD Integration](/ci-cd-integration/overview.md) - supported providers, and the features that matter in a pipeline * [GitHub Actions](/ci-cd-integration/github-actions.md) - drop-in replacement for the Maestro Cloud action * [GitHub Checks](/ci-cd-integration/github-checks.md) - report pass/fail straight onto the pull request * [Artifacts & Downloads](/test-artifacts-and-reports/artifacts.md) - pull logs, screenshots, videos and reports ### Configure your runs * [Device Matrix](/configuration/device-matrix.md) - run your suite across several devices in one upload * [Maestro Versions](/configuration/maestro-versions.md) - pin a Maestro version, or track `latest` * [Environment Variables](/configuration/environment-variables.md) - inject config and secrets into your flows ### Automate with AI & code * [MCP Server](/ai-agents-and-mcp/overview.md) - let Claude, Cursor and other MCP clients run your tests * [CLI Reference](/cli-reference/overview.md) - every `dcd` command and flag * [REST API](/rest-api/overview.md) - uploads, results and flows over HTTP ### Pricing & plans * [Test Run Billing](/billing/test-run-billing.md) - what a single test run costs * [Subscriptions](/billing/subscriptions.md) - the Pro, Max and Enterprise plans * [Concurrency & Parallel Runs](/getting-started/concurrency-and-parallel-runs.md) - how many of your tests run at once ## FAQ ### Is DeviceCloud really a drop-in replacement for Maestro Cloud? For most projects, yes. The CLI mimics the Maestro Cloud API, so you change `maestro cloud` to `dcd cloud` and drop the `--apiKey` flag. On GitHub Actions you swap a single `uses:` line and most inputs carry over unchanged; the migration guide lists the few Maestro-specific ones (such as `project-id` and `device-model`) to remove or replace. See [Quick Start](/getting-started/quickstart.md) and [Migrating from Maestro Cloud](/ci-cd-integration/github-actions.md#migrating-from-maestro-cloud). ### How much does it cost? DeviceCloud bills per test run i.e. a single top-level flow on a single device and are charged at $0.11 for standard iOS and $0.09 for standard Android. iPad, Pixel 10 Pro Fold, Google Play, tablet and `m4`/`m1`/`gpu1` runner flows are charged at the advanced rate of $0.15. New accounts get $20 of free credits. See [Test Run Billing](/billing/test-run-billing.md). ### How many tests can I run in parallel? It depends on your plan: Pro runs up to 5 iOS and 5 Android tests at once, and Max up to 20 of each. Enterprise concurrency is arranged to fit your requirements. Once you hit your maximum, further tests queue and start automatically as capacity frees up. See [Concurrency & Parallel Runs](/getting-started/concurrency-and-parallel-runs.md) and [Subscriptions](/billing/subscriptions.md). ### Which devices and OS versions can I run on? Android runs cover a range of Google Pixel phones plus a generic tablet, and iOS runs cover recent iPhones and the iPad Pro. Not every device supports every OS version, and older devices and versions are retired over time, so check [Devices & OS Versions](/getting-started/devices-configuration.md) for the current devices, Android API levels and iOS versions. ### Which Maestro versions are supported? We always support the latest version of Maestro with backwards compatibility up to v2.0.4. Runs default to v2.2.0, and you can use `--maestro-version latest` to always use the most up to date version. We periodically remove support for older versions, and these will be announced with plenty of warning. See [Maestro Versions](/configuration/maestro-versions.md). ### Do I need an API key, or can I just log in? Both work. Run `dcd login` once for local use and our CLI will store your session, so you never pass a key on a command. For CI or any headless environment, you can generate and set `DEVICE_CLOUD_API_KEY` or pass `--api-key`. When more than one credential is present, precedence is the `--api-key` flag, then the environment variable, then the stored session. See [Authentication](/getting-started/api-keys.md). ### How do I run DeviceCloud in my CI? There are first-class integrations for GitHub Actions, Bitrise, Bitbucket Pipelines and EAS Workflows. Any other provider can call the CLI directly with `npx --yes @devicecloud.dev/dcd@latest cloud ` and gate the build on the [exit code](/advanced/exit-codes.md). See [CI/CD Integration](/ci-cd-integration/overview.md). ### How do I get videos, logs and test reports? Pass `--download-artifacts ALL` (or `FAILED`) to a `dcd cloud` run, or fetch them after the fact with `dcd artifacts --upload-id --download-artifacts ALL`. Each result in the console also has a download menu for its logs, reports, app binary and workspace. Reports are available as `junit`, `html`, `html-detailed` and `allure` via `--report`. See [Artifacts & Downloads](/test-artifacts-and-reports/artifacts.md) and [Report Formats](/test-artifacts-and-reports/report-formats.md). ### Is there a time limit on a test? Yes. Every flow has a 10-minute execution limit. A flow that is still running when it reaches the limit is stopped and marked as failed, with a "Test run timed out after 10 minutes" error. Failed tests can be retried up to twice, giving a maximum of three total runs, free of charge. See [Quick Start](/getting-started/quickstart.md#limits) and [Retry Strategies](/advanced/retry-strategies.md). ### Can I allow-list DeviceCloud in our firewall? Yes. Test runner egress comes from a published set of IP ranges, and the same list is served from an unauthenticated endpoint — `GET https://api.devicecloud.dev/ip-addresses` so your tooling can poll it rather than watching a docs page. See [IP Addresses](/security-and-compliance/ip-addresses.md). ### Can AI agents drive DeviceCloud? Yes. The `@devicecloud.dev/dcd` package ships `dcd-mcp`, a Model Context Protocol server that lets Claude, Cursor, VS Code and other MCP clients list devices, submit runs, check status and download artifacts. It's in beta, and the one billable tool can be hidden entirely with `--read-only`. See [MCP Server](/ai-agents-and-mcp/overview.md). ### How do I get support? Every account gets community and team support via [Discord](https://discord.gg/gm3mJwcNw8), and you can also email . We aim to respond within four hours for urgent queries and three days for non-urgent. Max and Enterprise customers both receive priority email support and Enterprise customers have direct access to the team via Slack Connect. Support hours are 8am–8pm UK time, Monday to Friday. See [Service Level Agreements](/legal/service-level-agreements.md). {% hint style="info" %} Question not answered here? Ask in our [Discord](https://discord.gg/gm3mJwcNw8) or email and we'll be happy to help. {% endhint %}