Run all your Selenium tests in parallel

Spin up 100s of browsers in seconds

Join the beta

Run all your Selenium tests in parallel

Spin up 100s of browsers in seconds

Join the beta

Run all your Selenium tests in parallel

Spin up 100s of browsers in seconds

Join the beta

Run all your Selenium tests in parallel

Spin up 100s of browsers in seconds

Join the beta

Fast

Browsers are memory hogs, so your computer can run a limited number of parallel tests. Break free from those limitations and run all your tests in parallel.

Simple

Many end-to-end testing tools use Selenium under the hood. You don't need to rewrite existing tests to improve your tests' performance.

Predictable

When browsers are shared across tests, one test can make others fail randomly. We start a new browser for every test so your tests are isolated.

Pricing

Pay as you go

$0.003
per second
Unlimited parallelism1
No unexpected bills2
No recurring costs
Chrome browsers
Sign Up

Enterprise

Volume discounts

All pay as you go features
SAML integration
Phone support
Invoicing
Contact Sales
1 The default limit of 50 can be raised at no extra cost
2 Your balance is paid upfront and reduced by usage until it runs out

FAQ

What am I paying for?

This is a drop-in replacement for your Selenium Grid. You get an API token and endpoint to configure the Selenium library of your choice.

Which browsers do you support?

We support headless Chrome. Browsertron isn't designed for cross browser testing; its goal is the quickest first pass in Chrome. If your application doesn't work in Chrome (~60% of global browser usage), there's no need to wait for your cross browser tests.

Which programming languages do you support?

Most popular languages have an official Selenium library. However, to support running hundreds of tests at once, you'll need a test runner that can handle it. We've published examples for Pytest and Jest.

How granular is the pricing?

We charge per second, rounded to the nearest second, with a minimum of one second per test. The timer begins after a browser is created, so you're not charged while a test is starting.

How long can my tests be?

There's a 290 second timeout for each test. It's important that you close or quit each Selenium session to avoid unnecessary charges.

Get up to speed

Testing is expensive when developers wait for tests or switch contexts while tests are running. Some teams skip end-to-end tests at their customers' expense, but your customers deserve better. Test quickly and reliably on every commit with Browsertron.