Your tests stay Playwright, Selenium and pytest. We don't replace them. We make them enterprise-ready, and you own your code, your evidence and your history.

Hybrid QA: run local first, add cloud only if you choose.

What Nexus StudioQA runs today, what is planned, and the switch that blocks the cloud. Each part carries its status.

By the Nexus StudioQA team, Verdict System LLC.

Last updated:

The short answer

Nexus StudioQA is hybrid and local first. Your tests run on machines you control today: your PC, Docker or a Linux server over SSH. An optional hosted runtime, Nexus Cloud, is Planned and not available. Isolated mode, In progress, is the switch that blocks Nexus Cloud, AI providers, ticketing, chat, webhooks and update downloads, while the license check and your app under test still connect.

What exists, by status

Available means you can use it in the build you download. Planned and In progress mean it is not in that build.

PartStatusWhat it means
Runs on your machinesAvailableYour PC, a mini PC, Docker or a Linux server over SSH. Tests, evidence and history stay there.
Same tests everywhereAvailableStandard Playwright, Selenium and pytest files, with no proprietary format to leave.
License checkAvailable, always onThe one connection the Studio makes on its own. It carries no test data and has no offline mode.
Isolated modeIn progressEnforced in the engine and covered by tests. The Studio switch and an independent network capture of a full run are not done yet.
Nexus CloudPlannedAn optional hosted runtime you would choose per run. Not available yet and not yet for sale. We may change or drop this feature.

There are no cloud runners today, and a license bought today does not include Nexus Cloud. This page quotes no cloud price, no included minutes and no release date, because none exist.

The off switch: Isolated mode

With Isolated mode on, the license check, the application you are testing and local services still connect. The outside services in the last two rows are blocked with a message that names the host.

ConnectionIsolated mode offIsolated mode on
The application under testConnectsConnects
License checkConnectsConnects
A local service on this machine, such as a local Ollama modelConnectsConnects
A cloud AI provider, Jira, Slack, Teams, Telegram, a webhook or an update downloadConnects only when you set it up or click itBlocked
Nexus Cloud (Planned)Connects only for a run you send to itBlocked

An administrator can lock it

A machine policy file can turn Isolated mode on and lock it, so a user cannot turn it off. A policy file that exists but cannot be read counts as on.

What it does not do

It does not remove the license check. The signed license lease is the only source of truth, and there is no offline mode, so a machine that never goes online is not a fit.

What is not measured yet

The table is how the engine is written and tested, not a measured result. A network capture of a full run, covering DNS, browsers and package downloads, has not been done, so this site does not claim that nothing else connects.

What it covers

What Nexus StudioQA itself sends. It cannot control what your application under test, your browser or your operating system connect to.

What is not built yet

The Studio screen that flips the switch. Today the engine reads the policy file or an environment variable.

Why hybrid, and why local first

Teams with sensitive test data want control. Teams with a large suite sometimes want capacity they do not own. Hybrid keeps both options without choosing for you.

  • Local is the default

    A run starts on your machine unless you say otherwise. Nothing is sent anywhere for a run you did not choose to send.

  • Cloud, if it comes, is a per-run choice

    Nexus Cloud is planned as an option for a single run, with the same tests and the same Evidence Locker. It is not planned as a replacement for your own machines.

  • No lock-in either way

    Your tests are plain Playwright, Selenium or pytest files. They run without the Studio, on your machine, your server or another vendor's grid.

  • You can block the cloud

    Isolated mode exists for the day a policy, a customer or an auditor says no cloud. It is the reason the cloud can be optional.

Questions people ask

  • Is Nexus StudioQA hybrid?

    Yes, in this order: local first, with an optional hosted runtime planned and a switch to turn the cloud off. Today only the local part is available.

  • Can I switch the cloud off completely?

    That is the purpose of Isolated mode, which is In progress. It blocks Nexus Cloud, AI providers, ticketing, chat, webhooks and update downloads, and leaves the license check and your app under test connected. Today there is no cloud to switch off.

  • Does Isolated mode work with no internet?

    No. The license check stays on by design, and without a successful check the Studio keeps working for 7 days, shows a notice for 4 more, then turns read-only until it reconnects.

  • Will my tests ever run in your cloud without my choice?

    No. Nexus Cloud is planned as an opt-in option for each run, and local stays the default. It is Planned, so nothing runs there today.

  • Do I need Nexus Cloud?

    No. Everything the Studio does today runs on your machines, and a license bought today does not include Nexus Cloud.

  • How is this different from BrowserStack or Sauce Labs?

    They run your tests in their cloud. Nexus StudioQA runs them on your machines and is priced per machine. If Nexus Cloud ships, it would be an addition to that, not the starting point.

Start local.

Try every feature free on your PC. No card needed.