Welcome to DeviceCloud
DeviceCloud is a third-party alternative to Maestro Cloud. It runs your Maestro flows on cloud iOS simulators and Android emulators.
Why teams switch:
- Per-test-run pricing, with $20 of free credits to start
- Parallel runs: up to 20 iOS and 20 Android tests at once on the Max plan, and more on Enterprise
- Google Play APIs, tablets, iPads and foldables
- Fast support, through 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:
# before
maestro cloud --apiKey <apiKey> <appFile> <flowFile>
# after
dcd cloud <appFile> <flowFile>Start with the Quick Start to install the CLI and run your first flow.
Quick links
Get started
- Quick Start — install the CLI and run your first flow
- Authentication —
dcd loginlocally, API key in CI - Flows & Workspaces — run a single file, a directory, or a whole workspace
- Devices & OS Versions — every supported device, Android API level and iOS version
Run in CI
- CI/CD Integration — supported providers, and the features that matter in a pipeline
- GitHub Actions — drop-in replacement for the Maestro Cloud action
- GitHub Checks — report pass/fail straight onto the pull request
- Artifacts & Downloads — pull logs, screenshots, videos and reports
Configure your runs
- Device Matrix — run your suite across several devices in one upload
- Maestro Versions — pin a Maestro version, or track
latest - Environment Variables — inject config and secrets into your flows
Automate with AI & code
- Agent Devices — give your AI agent a cloud iOS or Android device to drive, with a person on hand when it gets stuck (beta)
- Connect an AI Agent — let Claude Code, Cursor and other MCP clients run your tests
- CLI Reference — every
dcdcommand and flag - REST API — uploads, results, flow analytics, device sessions and IP addresses over HTTP
Pricing & plans
- Test Run Billing — what a single test run costs
- Subscriptions — the Pro, Max and Enterprise plans
- Overage — usage beyond your plan's included credits, and the Overage Limit
- Concurrency & Parallel Runs — 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 and Migrating from Maestro Cloud.
How much does it cost?
DeviceCloud bills per test run: one top-level flow on one device, from $0.09 a run. Tablets, foldables, Google Play images and the m4 and m1 runner types cost the advanced rate, and new accounts get free credits to start. The Pro and Max plans include a set amount of usage each month, and usage beyond that is billed as overage, up to a limit you control. See Test Run Billing.
How many tests can I run in parallel?
It depends on your plan. On the standard runners, Max runs up to 20 iOS and 20 Android tests at once, and 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 and Subscriptions.
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 for the current devices, Android API levels and iOS versions.
Which Maestro versions are supported?
We always support the latest version of Maestro, and several older ones. Runs default to v2.10.0, and --maestro-version latest always uses the newest version we support. We announce removals of older versions well in advance, in Deprecations & Removals. See Maestro Versions.
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.
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 <appFile> <flowFile> and gate the build on the exit code. See CI/CD Integration.
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 <uuid> --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 and html via --report (html-detailed and allure are deprecated). See Artifacts & Downloads and Report formats.
Is there a time limit on a test?
Yes. Every flow has a 10-minute execution limit, and a flow that is still running when it reaches the limit is stopped and marked as failed. A flow that needs longer can opt into extended runtime. A failed test can be retried for free, see Retry Strategies.
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.
Can AI agents drive DeviceCloud?
Yes. dcd mcp, the Model Context Protocol server built into the CLI, lets Claude Code, Cursor, VS Code, Codex and other MCP clients list devices, run cloud tests, check status and download artifacts. --read-only hides the one billable tool. Agent Devices (closed beta) also give an agent a cloud device to drive, through DeviceCloud's hosted MCP server. See Connect an AI Agent.
How do I get support?
Every account gets community and team support via Discord, and you can also email support@devicecloud.dev. We aim to respond to urgent queries within four hours, during our support hours. Max and Enterprise customers both receive priority email support and Enterprise customers have direct access to the team via Slack Connect. See Service Level Agreements for response times and support hours.
INFO
Question not answered here? Ask in our Discord or email support@devicecloud.dev and we'll be happy to help.
