Nexus StudioNexus Studio docs
Short guides for what happens around your tests: installing and activating the Studio, choosing where it runs, paying for it, and what to do when a message appears.
Guides
Getting started
Download the installer, check it, activate this machine and run a first test.
Hardware and where to run it
Windows 11 x64 and 16 GB of RAM at least. The Studio on your own PC, nothing else required; a mini PC that stays on, if you want one; each workspace's suites on this machine, in Docker, or on a VPS over SSH; real Android phones over USB.
CI/CD
The GitHub Actions or GitLab CI file the Studio writes, where the job runs, secrets, JUnit XML and evidence.
License and billing
The 30-day trial, the plans and their machines, your key, the license check, read-only mode, renewals, canceling, refunds and deleting your account.
Troubleshooting
The messages the Studio's License screen and the sign-in page show: what each one means and what to do.
Security and privacy
What leaves your machine, what your account keeps and for how long, cookies, and how to download your data.
How verdicts are decided
The order the engine checks a run in, and why a timeout, a block or a healed selector never reads as a bug in your application.
Problems it solves
Three questions QA teams ask, each answered with how the Studio handles it and where it stops.
Common questions
- The Studio says it is read-only
- I lost my license key
- A payment failed
- How do I delete my account?
- The sign-in link does not work
Not here? In your account, Help has an email button that includes your account details, or write to [email protected].