← Back to the site
English

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

Verify a download

Last updated 2026-10-21 · what you can check yourself, and where

Every claim on this page is one you can test. Where a check needs a tool, the command is here. For support and what you keep if we disappear, see Support and longevity; to report a vulnerability, see Security.

Code signature

The Windows installer is signed with an Authenticode code-signing certificate issued to Verdict System LLC, the company that publishes Nexus Studio. SSL.com, the certificate authority, validated the organization before issuing it. A valid signature shows who signed the file and that it has not changed since. It does not say the software is free of defects.

To check it in PowerShell, in the folder you downloaded the installer to:

Get-AuthenticodeSignature ".\Nexus Studio_2.0.0_x64-setup.exe" | Format-List Status, StatusMessage, SignerCertificate

Or without PowerShell: right-click the file, choose Properties, open the Digital Signatures tab, select the signature and press Details. Windows says there whether the signature is valid and who signed it. The tab does not exist on an unsigned file.

SHA-256

The SHA-256 of each installer is published on the Download page and in /release.json. The build also writes a checksums.txt next to the installer, with its file name, SHA-256 and size. To compute yours:

Get-FileHash ".\Nexus Studio_2.0.0_x64-setup.exe" -Algorithm SHA256

Compare the Hash it prints with the published one, or with the line in checksums.txt. Capitals do not matter. If they differ, delete the file and download it again from this site. The signature and the hash answer different questions: the hash says your copy is the same file we published; the signature says who published it.

Payments

Payments run on Stripe's hosted checkout and billing portal. Your card number and billing address go from your browser to Stripe, and never to our servers; we never see or store a card. Stripe tells us your customer and subscription IDs, the payment status and the date you have paid until. Details are in Subprocessors.

Security scans of this site

Anyone can run these two public scans against sentinel-nexusstudio.com and read the current result, which can change as the scanners or our configuration do:

A grade describes how this site is configured. It is not a statement about the installer or the Studio. Our vulnerability contact is also machine-readable in security.txt.

Subprocessors

The providers that process account data for us, what each one receives and where, are listed and dated in Subprocessors. That page is the single source: we do not repeat the list here.

Where your data stays

Nexus Studio runs on your machines. Your tests and evidence stay there and reach us only if you send them. The one connection the product makes to us on its own is the license check; it sends the license key once, when you activate, plus a hash of the machine, a nonce and the token, and the host name, operating system and Studio version, cut to 64 characters, so the portal can name the machine. It never sends test data. What we keep, and for how long, is in the Privacy Policy; how the Studio handles data on disk is in Security and privacy.