Selenoid is a powerful implementation of Selenium hub using Docker containers to launch browsers.

Start browser automation in minutes by downloading Configuration Manager binary and running just one command:

$ ./cm selenoid start --vnc --tmpfs 128

That's it! You can now use Selenoid instead of Selenium server. Specify the following Selenium URL in tests:

http://localhost:4444/wd/hub

No need to manually install browsers or dive into WebDriver documentation. Available images:

New images are added right after official releases. You can create your custom images with browsers.

New rich user interface showing browser screen and Selenium session logs:

• Any browser session can be saved to H.264 video (example)
• An API to list, download and delete recorded video files

• Any browser session logs are automatically saved to files - one per session
• An API to list, download and delete saved log files

Suitable for personal usage and in big clusters:

• Consumes 10 times less memory than Java-based Selenium server under the same load
• Small 6 Mb binary with no external dependencies (no need to install Java)
• Browser consumption API working out of the box
• Ability to send browser logs to centralized log storage (e.g. to the ELK-stack)
• Fully isolated and reproducible environment

Maintained by a growing community:

• Detailed documentation
• Telegram support channel
• Support by email
• StackOverflow tag
• YouTube channel

Complete reference guide (including building instructions) can be found at: http://aerokube.com/selenoid/latest/

Selenoid was initially created to be deployed on hardware servers or virtual machines and is not suitable for Kubernetes. Detailed motivation is described here. If you still need running Selenium tests in Kubernetes, then take a look at Moon - our dedicated solution for Kubernetes.