Development
Selenium Grid on a VPS: a remote, password-protected Chromium browser for the end-to-end tests of your CI pipelines.
In validation
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
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.
An agency runs the same test suite against staging and production, from the same grid, with the same 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
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.
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.
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.
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.
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
The memory required and the VPS that covers it, on every card.
Check it: the “Recommended VPS” line of each card
You administer the system over SSH; your data stays on your VPS.
Check it: the “What is installed” section of each page
The applications are open source: your only cost is the VPS that runs them.
Check it: in the cart, no line for the application
Open-source continuous integration and delivery server: Jenkinsfile pipelines, over 2,000 plugins, builds triggered by your Git repositories.
DevelopmentYour own GitHub, self-hosted in minutes. Full Git platform with CI/CD (Gitea Actions), package registry and team permissions — without usage-based billing.
DevelopmentSelf-hosted SMTP test server that captures emails without delivering them. Web interface to inspect them, REST API, and built-in spam scoring.

Dedicated Cloud VPS — IPv4 included, server in Europe, support included. Your data never leaves your server.
Selenium Grid also runs on a dedicated server, when models or data outgrow a VPS. See dedicated servers