Nexus StudioSomething does not work
Report a problem lists what to include and what never to send, with an email template.
[email protected]Support and longevity.
What you can count on after you buy: how fast we answer, how long each release is supported, and what you keep if we ever stop.
Our support commitment
An 8-hour first-response target, any day of the week
Write to [email protected] and we aim to send a first response within 8 hours, any day and any hour. While the team is small this is a target, not a contractual service level.
1 year of support for every release
Each release gets fixes and security updates for 1 year from the day it is published.
Updates are manual and never silent: the Studio tells you a new version exists and downloads nothing until you choose Update now. How updates work
If the vendor disappears
Your tests are files in a folder on your own disk, written in the frameworks your team already knows: Playwright, Selenium and pytest. API tests are the one exception. This is what it takes to run each kind without Nexus Studio, so you can leave whenever you want.
| Your test | To run it without Nexus Studio |
|---|---|
| Playwright, Python | No change to the file. It is a plain pytest-playwright test and runs with pytest alone. |
| Selenium, Python | No change to the file. It is pytest with a driver fixture, and the workspace's conftest.py falls back to a plain WebDriver when the engine is not the one running it. |
| Playwright, JavaScript and TypeScript | Point the fixture import at the top of the file back at @playwright/test. A visual checkpoint, if you added one, needs replacing. |
| Selenium, JavaScript | Add a few lines that start a driver. The code is selenium-webdriver, inside a run() function. |
| API tests | They use the Studio's own JavaScript format and would need rewriting for another runner. |
- You can check it before you pay. In the 30-day trial, record one test, choose Open the code and read the file. What the files look like
- Your tests, evidence and history are files in your workspace folder, and they stay readable whatever the state of your license.
- The Studio itself checks its license online. If our license server stopped answering, an activated Studio would keep working for 7 days, show a notice for 4 more, then turn read-only: your evidence stays readable and no new run starts. The framework tests above keep running with their own runners.
- You can cancel at any time in your account, under Plan & billing. You keep access until the end of the period you paid for, and nothing renews after it.
Your data stays on your machines
Your tests and evidence leave your machines only when you send them yourself, for example to an AI provider you connect. On its own, the only connection from the product to us is the license check, plus the installer of an update when you choose to download it.
- Activation sends your license key once, with a machine hash and a nonce. Each later check sends a machine hash, a nonce and a token.
- It never sends test names, results, screenshots, videos, reports, history or the addresses of the applications you test.
- We never receive your test data. We keep your email, billing status and license records.
- Jira, Slack, Telegram or an AI provider, if you set them up, are reached straight from your machine, never through us.
What the product sends, in the Privacy policy · Security and privacy · Subprocessors
License and working offline
The license is checked online. A short gap in the connection does not stop your work.
- The Studio checks its license when it starts and every 24 hours.
- It keeps working for 7 days without a successful check, shows a notice for 4 more, then turns read-only until it reconnects. Evidence stays readable; new runs wait for a connection.
- The 30-day trial needs no card, and the 30 days start when you first activate the Studio.
- A new version is announced inside the license check, signed. The Studio downloads the installer only when you choose Update now.
Who stands behind it
Nexus Studio is made by Verdict System LLC, a Wyoming limited liability company. Legal notices go to Verdict System LLC, 30 N Gould St, Ste N, Sheridan, WY 82801, United States, and the terms are governed by the laws of the State of Wyoming.
- It is a small company, and it says what it does not do yet: no SSO, no SOC 2 report, a Studio for Windows only, and iPhones covered through WebKit rather than on a device.
- Nexus Studio is a desktop application for automated QA testing. It has no connection with Nexus Studios, the creative studio in London, or with any other company of a similar name.
The quality of the product itself
Our release gate is 5,586 tests: 2,765 for the engine and 2,821 for the Studio.
- 5,586
- tests in our release gate: 2,765 engine, 2,821 Studio
- 0
- copies of your test data on our servers
How to ask for help
Plans, invoices, questionnaires
Plans, Enterprise contracts, purchase orders and security questionnaires go to sales.
[email protected]Found a security vulnerability? Do not report it to support: follow the security policy.
Check it on your own app.
Free for 30 days, with every feature, on your machines. No card needed.