Development

Selenium Grid

Selenium Grid on a VPS: a remote, password-protected Chromium browser for the end-to-end tests of your CI pipelines.

In validation

About Selenium Grid

Selenium Grid is the WebDriver server of the Selenium project (Apache-2.0 license): your tests, written in Java, Python, JavaScript, C# or Ruby, open a session on the grid instead of starting a browser on the build machine. This listing installs the official docker-selenium "standalone" image, which bundles the router, the session queue and a Chromium node in a single container. The grid is protected by a username and a password (router basic authentication), accepts two parallel sessions and closes an abandoned session by itself after five minutes. The grid interface shows the running sessions and lets you watch the browser at work. Your GitHub Actions, GitLab CI, Jenkins or Gitea Actions pipelines reach it at its HTTPS address: tests run on a stable browser, always the same one, and your test data stays on your server.

What gets installed

Ready when the VPS starts

Compatible OS
Choice of Linux distributions
Application
Selenium Grid
Tech stack
DockerSelenium GridChromium
Minimum RAM
2 GB minimum
Minimum CPU
2 vCPU
Default port
8129
Access
root over SSH

Key features

  • Standard WebDriver (W3C) endpoint: any Selenium client connects with RemoteWebDriver, without changing the test code.
  • Official docker-selenium "standalone" image: router, session queue and Chromium node in one container, no driver to install.
  • Grid protected by username and password: no session opens without them, and neither does the interface.
  • Two parallel sessions and automatic closing of abandoned sessions after five minutes.
  • Grid web interface: running sessions, node capabilities and a live view of the browser during a test.
  • Works with Selenium, WebdriverIO, Capybara, Robot Framework or Codeception, from GitHub Actions, GitLab CI, Jenkins or Gitea Actions.

When to use this solution?

End-to-end tests in CI

CI runners no longer install Chrome on every build: they open a session on the grid, run the checkout or login journey, then close it.

Check a client's site before launch

An agency runs the same test suite against staging and production, from the same grid, with the same browser.

Automate a task in a browser

A scheduled script logs into a portal, fills in a form or downloads an export on a browser that runs permanently on your server.

Guide

Deploy Selenium Grid on your VPS

  1. Create the VPS and choose the address

    Order an Ubuntu 24.04 VPS with at least 2 GB of RAM and 2 vCPUs (4 GB if you run two sessions continuously). Selenium Grid requires a domain: your pipelines connect to it over HTTPS from outside. It installs on a subdomain of one of your domains, or on the VPS's free subdomain (selenium-grid.{dns_slug}.servorbit-dns.com), HTTPS included. No need to buy a domain name.

  2. Install Selenium Grid from the Marketplace

    In your client area, select Selenium Grid, choose the address and click Install. The script deploys the official docker-selenium image with Chromium, protects the grid with the admin user and a generated password, then configures the nginx reverse proxy over HTTPS. The grid is ready in less than a minute.

  3. Sign in for the first time

    Open https://your-domain/ui/: the browser asks for credentials. Enter the admin user and the password shown in your client area. The interface shows the Chromium node and its two free session slots.

  4. Connect your tests

    In your tests, replace the local browser with a RemoteWebDriver pointing to https://admin:PASSWORD@your-domain (or /wd/hub for an older client). Keep the password in your CI secrets, never in the repository. Ask for the "chrome" browser: the Chromium node answers to that name.

  5. Watch a session live

    During a test, open the grid interface, click the session and then the camera icon: you watch the browser at work. The password asked is the same as the grid's.

Proof

What we promise, and how to check it

  • The recommended size, for every application

    The memory required and the VPS that covers it, on every card.

    Check it: the “Recommended VPS” line of each card

  • Root access, on your server

    You administer the system over SSH; your data stays on your VPS.

    Check it: the “What is installed” section of each page

  • You pay for the VPS, not the software

    The applications are open source: your only cost is the VPS that runs them.

    Check it: in the cart, no line for the application

Frequently asked questions

Questions about Selenium Grid

← Back to DevelopmentAll applications
The runner no longer installs a browser and its driver on every build, and all your suites test the same browser, at the same version. The grid runs permanently: a build that starts opens a session right away, and several projects can share it.

Activate Selenium Grid on your infrastructure.

Dedicated Cloud VPS — IPv4 included, server in Europe, support included. Your data never leaves your server.

All applications

Selenium Grid also runs on a dedicated server, when models or data outgrow a VPS. See dedicated servers