01What is Maestro Deck?
Maestro Deck is an open-source desktop client for the Maestro mobile end-to-end testing format. It lets you author, inspect, and run Maestro YAML flows against iOS and Android targets from your local machine.
02Is Maestro Deck free?
Yes. Maestro Deck is released under the Apache-2.0 license. There are no paid tiers, no per-seat fees, and no usage caps. You can use it commercially and redistribute it.
03Is Maestro Deck open source?
Yes. The full source is available on GitHub at github.com/BlueShork/maestro-deck under the Apache-2.0 license. Issues, pull requests, and discussions are public.
04How is Maestro Deck different from Maestro Studio?
Maestro Studio is mobile.dev’s proprietary, cloud-tethered desktop tool. It requires a mobile.dev account, ships telemetry by default, and is sold per seat. Maestro Deck is open source, runs entirely on your machine, requires no account, and is free.
05Does Maestro Deck work with existing Maestro flows?
Yes. Maestro Deck reads and writes the same YAML format used by mobile.dev’s Maestro CLI and Studio. Existing flows in your .maestro/ directory open without modification.
06Does it bundle the Maestro CLI?
No. Maestro Deck calls the Maestro CLI you already have installed. This guarantees your flows run against the exact same CLI version locally and in CI, eliminating a common source of drift.
07Can I self-host Maestro Deck?
Maestro Deck is a desktop application, so by default it runs locally on your laptop — there is no separate server to host. There is no cloud component required to operate it.
08Does it support iOS and Android?
Yes. Both platforms are first-class. Maestro Deck works with iOS simulators, physical iPhones and iPads, Android emulators, and physical Android devices.
09How do I run Maestro Deck flows in CI/CD?
Flows authored in Maestro Deck are plain Maestro YAML, so any CI provider that can run the Maestro CLI can run them. See the CI guide at /docs/guides/ci-cd-integration for GitHub Actions, GitLab CI, and CircleCI examples.
10Which operating systems does the desktop app support?
macOS, Linux, and Windows.
11How do I install Maestro Deck?
Follow the installation guide at /docs/installation. The short version is a single shell command that downloads the binary for your platform.
12Does Maestro Deck require a Maestro CLI install?
Yes. Maestro Deck delegates flow execution to the Maestro CLI, so the CLI must be installed and on your PATH. The installation guide walks through both.
13Can I view the history of flow executions?
Yes. Each run is recorded locally with its logs, screenshots, and per-step timing. Runs are stored on disk so they survive restarts.
14Can Maestro Deck run flows in parallel?
Yes. The runner can drive multiple devices in parallel, sharded by tag or file. See /docs/guides/parallel-execution for setup and pitfalls.
15Does it collect telemetry?
No. Maestro Deck does not phone home. There is no analytics endpoint and no usage reporting.
16What is the license?
Apache-2.0. You can use it commercially, modify it, and redistribute it, including as part of a closed-source product, as long as you keep the license notice.
17How do I report a bug or request a feature?
Open an issue on GitHub at github.com/BlueShork/maestro-deck/issues. Bug reports with a minimal reproduction (a flow YAML and the OS / CLI versions) get fixed faster.
18Is there a hosted or cloud version?
A hosted dashboard called MaestroDeck Cloud is in development for teams that want shared run history and a managed device farm. The desktop client itself stays free and open source regardless.
19Can I migrate from Maestro Studio without rewriting flows?
Yes. Because both tools use the same YAML format, migration is opening your existing .maestro/ folder in Maestro Deck. See /docs/migration/from-studio for the step-by-step.
20Who maintains Maestro Deck?
Maestro Deck is built and maintained by the BlueShork team and external contributors. It is not affiliated with mobile.dev.