Nexus StudioYou do not work on Windows
The Studio is a Windows 11 desktop app, with 16 GB of RAM as the minimum. Only the engine can run your suites on a Linux server, in Docker or over SSH.
Compare Nexus Studio with the other ways to test.
We compare kinds of tools, not brands. Each kind does something well, and for some jobs it is the better choice. This page says which.
Four kinds of tools, side by side
These are general descriptions of each kind. A specific product can differ, so check a vendor's own documentation before you decide. The Studio tour shows every screen of Nexus Studio.
| Kind of tool | Where it is strongest | Where Nexus Studio differs |
|---|---|---|
| Cloud browser and device grids | Running one test across a wide range of browser, operating system and device combinations, at a scale one office cannot match, with no machines for you to look after. | Nexus Studio runs on machines you control, and by default tests and evidence stay on your own disks. It covers Chromium, Firefox and WebKit and real Android phones over USB, not a catalog of combinations. |
| Low-code and proprietary recorders | Letting people who do not write code build tests by clicking in a visual editor, often with hosting and reports in the same product. | The Nexus Recorder writes standard Playwright or Selenium code, with no AI in the loop. The files are yours to read, edit and keep, so there is no format to migrate out of. |
| Test management tools | Planning and tracking testing across a team: requirements, test cases, manual test runs, assignments and dashboards. | Nexus Studio runs automated tests and keeps the proof: 14 verdicts, evidence for every failure and a SHA-256 chain of custody. It has no screens for requirements or manual test cases, and with Jira switched on a failed run files a ticket. |
| Raw Playwright or Selenium, no platform | Open source and fully under your control. With a CI service and engineers who maintain the rest, it can be all a team needs. | Nexus Studio runs the same frameworks and adds what they leave to you: verdicts that separate a defect from a slow network, a Recorder, scheduled runs with alerts, evidence for every failure, and CI/CD set up on screen. |
When another kind of tool is the better choice
Each of these needs something Nexus Studio does not set out to be.
A cloud grid
Pick one when you must cover hundreds of browser and operating system combinations, need iPhones and iPads on physical devices, or have no machine of your own to run tests on.
A low-code recorder
Pick one when your testers never read code and want an editor that stays no-code, or when you want a vendor to host and maintain the tests for you.
A test management tool
Pick one when your main need is planning, requirements traceability and manual test runs. It does a different job from Nexus Studio, and the two can be used together.
Raw Playwright or Selenium
Pick it when your engineers already have reporting and CI they trust, when you work on macOS or Linux, or when you do not want a paid layer on top of the framework.
When Nexus Studio is not the right fit
Said plainly, and each point is true of the product today.
You need iPhones as physical devices
Real phones on USB are Android only. iPhone and iPad are covered through WebKit emulation, not on a physical device.
You need hundreds of browser combinations
It tests Chromium, Firefox and WebKit as Playwright ships them, on Windows. It does not run a catalog of browser, version and operating system combinations.
You want someone else to host the runs
There are no cloud runners. You provide the machines: your PC, a mini PC, Docker on your machine, or a VPS you rent and reach over SSH.
Your machines never go online
The Studio checks its license online 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.
Your tests are in another framework
The Test Adapter imports Playwright and Selenium tests in JavaScript, TypeScript or Python. Cypress, WebdriverIO, Robot Framework, Java and C# are not supported.
You need to manage manual test cases
The Studio runs and judges automated tests. It has no screens for requirements, test plans or manual test cases.
You need SSO or a SOC 2 report today
Nexus Studio has no SSO and no SOC 2 report yet. It is a small company, and it says so.
Who it is for
Three kinds of buyer get the most out of it.
A QA lead
You answer for quality and need a verdict you can defend. 14 verdicts separate a real defect from a slow network, a bot challenge or a dead browser. A retry that passes is FLAKY, never a quiet pass. The Executive Report says go, caution or no-go. What a failure leaves behind
A small business with no QA team
Nobody writes tests today. Record one by clicking, or describe it to the AI tool you already use, then run it on a schedule with Watch, which alerts only when a state changes. The Individual plan covers 1 machine and includes every feature. Pricing
A company with data requirements
Your rules keep test data, test credentials and screens of staging in your own hands. Tests, evidence and history stay on machines you own, and the only connection to us is the license check. Enterprise includes review of your security questionnaire, MSA and DPA. Trust and Own your infrastructure
Run it against your own app.
Free for 30 days, with every feature, on your machines. No card needed.