Cloud browsers, without a vendor account
Run your existing suite on Chromium, Firefox and WebKit in the cloud — no third-party grid to sign up for, and not a line of test code to change.
- Browser engines
- 3Browser enginesChromium, Firefox, WebKit
- Browsers at once
- No limitBrowsers at oncebuy as many as you need
- Vendor accounts
- 0Vendor accountsand no access keys
- Lines changed
- 0Lines changedyour suite runs as-is
How Testver Grid works
- 1
Add it to your plan
Choose how many browsers you want running at once, with your plan or any time from the dashboard.
- 2
Connect, once
Testver swaps your session for a short-lived grid token. No username or access key to enter.
- 3
Choose the grid in the runner
Set Run on to Testver Grid and pick Chromium, Firefox or WebKit.
- 4
Run, and read the evidence
Output streams live; video and logs land in Results next to the verdict.
Everything Testver Grid handles for you
Three real browsers
Chromium, Firefox and WebKit, on machines that are not yours. Your laptop stays usable while your whole pool of browsers is busy.
Nothing to rewrite
Playwright suites run unmodified. Selenium suites that create their driver from the remote address — as most cloud-ready projects already do — run as-is; if yours doesn’t, the AI Assistant adds it in one step.
Video and command log
Every session is recorded, and WebDriver sessions keep an ordered log of every command the test sent. Both open from the run’s report.
Proof it really ran there
Each cloud run carries a verdict from the grid itself. A run that quietly fell back to a local browser is flagged loudly instead of passing silently.
Reaches the app on your machine
Testing something that only exists on localhost still works. Every hop is an outbound connection, so nothing new is exposed on your network.
Watch it happen
Open a live view of a session while it is still running, when you would rather see the failure than read about it afterwards.
Evidence, not just a pass
A cloud run you cannot inspect is a claim. Every session on the grid comes back with the material to check what actually happened — in the same report you already open.
Video of the session
The whole browser session, recorded, and playable from the run that produced it.
Every command, in order
WebDriver sessions keep an ordered log of what the test sent, so a failure can be read rather than guessed at.
Proof it ran in the cloud
The grid itself returns a verdict. A run that quietly fell back to a local browser is flagged, not passed.
Live view while it runs
Watch a session in progress when seeing the failure beats reading about it afterwards.
The specifics, stated up front
- Browsers
- Chromium, Firefox, WebKit
- Frameworks
- Playwright (unmodified) and Selenium-protocol suites — Java, Python, C#, WebdriverIO, Robot Framework. Not Cypress.
- Browsers at once
- As many as you buy — no upper limit; a team shares one pool
- Runs per day
- Unlimited — you pay for concurrency, not volume
- Connected installations
- One per account or team; take-over once the holder is idle
- Session lifetime
- 30 minutes by default, 2 hours maximum
- Price
- An add-on, priced per parallel browser — prepaid with your plan, nothing metered per run
There is no ceiling on browsers at once: buy as many as your suite needs, and add more at any point during your plan’s term.
Testver Grid, answered
Do I need an account with a grid vendor?
No. There is no third-party account, no access key, and nothing to add to your CI secrets. The grid is part of Testver.
Do I have to change my tests?
Not for Playwright: Testver supplies the connection at run time, so the same suite runs locally or on the grid without a config change. Selenium-protocol suites (Java, Python, C#, WebdriverIO, Robot Framework) run as-is when they create their driver from the remote address Testver provides, as most cloud-ready projects already do; if yours builds a local driver, the AI Assistant adds the remote option in one step. Cypress cannot run on the grid.
Can it test an application running on my own machine?
Yes. A cloud browser can reach an app on your localhost, and every hop in that path is an outbound connection — nothing new is opened up on your network.
How do I know the run really used a cloud browser?
Every cloud-selected run gets a verdict from the grid itself. If a run silently fell back to a local browser, it is flagged rather than passing quietly.
What does it cost?
Grid is an add-on, priced per parallel browser — the number of browsers that can run at the same time. Buy as many as you need; there is no upper limit. The add-on is prepaid for the rest of your plan’s term and renews with the plan, and runs themselves are never metered or billed. The pricing page lists the current price.
How do I get access?
Buy the parallel browsers you need — on the pricing page together with your plan, or later from the Grid page or Billing → Add-ons in your dashboard. Once the add-on is active, Grid appears in your dashboard: press Connect in Testver and choose it in the runner. Administrators can also grant access to an individual account.
Can my whole team use it?
Yes. On a team plan, the browsers you buy form one shared pool with one connected Testver installation — the team owner’s, or a member the owner names platform manager. Runs from that installation use the pool in parallel, and everyone on the team sees the usage.
Keep your framework. Add AI and a premium toolset.
Set up in minutes. Self-host on your own hardware. Describe a test in plain English and get working code in your own framework — in a fraction of the time.