Browserless

Browserless allows remote clients to connect and execute headless work, all inside of docker

Overview

Browserless supports the standard, Puppeteer, Selenium and Playwright libraries.

It takes care of common issues such as missing system-fonts, missing external libraries, and performance improvements, along with edge-cases like downloading files and managing sessions. For details, check out the documentation.

If you've been struggling to deploy headless browsers without running into issues or bloated resource requirements, then Browserless was built for you.

Examples

Various minimal code examples for using Browserless on Railway with some common libraries -

https://github.com/brody192/puppeteer-example (Node)

https://github.com/brody192/playwright-example (Node)

https://github.com/brody192/playwright-example-python

https://github.com/brody192/selenium-example (Node)

https://github.com/brody192/selenium-example-python

https://github.com/brody192/chromedp-example (Golang)

Highlights

• Works seamlessly with Puppeteer, Playwright, and Selenium.
• No need to install extra packages, dependencies, or system libraries.
• RAM, CPU and GPU are fully managed to stop browsers devouring resources.
• Scaling and load balancing is handled for you to absorb any traffic surges.
• Chrome's zombie processes are cleared away to stop servers from clogging up.

Features

• Parallelism and queueing are built-in and configurable.
• Fonts and emoji's working out-of-the-box.
• Works with most headless libraries.
• Configurable session timers to keep things running smoothly.
• Error tolerant: if Chrome dies it won't.

Learn More

• Browserless