Browserless on Railway
A headless Chrome browser server you drive from Playwright or Puppeteer over WebSocket, on Railway.
Browserless runs headless Chrome as a service. Instead of installing a browser next to your script, you connect to it over WebSocket from Playwright or Puppeteer, or call its HTTP APIs, and the browser runs on the server.
Teams use it for scraping pages that need JavaScript, taking screenshots, generating PDFs, and running browser automation or tests without packaging Chrome into every app. It sits in the same space as hosted browser services, with the option to run it on your own infrastructure.
Browserless is published under SSPL-1.0 or a commercial licence, and its authors state that closed-source commercial use needs a commercial licence. Check the current terms before using it in a product.
What Browserless can do
- Remote headless Chrome over WebSocket
- Playwright and Puppeteer support
- HTTP APIs for screenshots, PDFs and content
- Token-based access control
- Limits for concurrency, queue length and session time
What people use it for
- A shared remote browser for Playwright or Puppeteer scripts
- Scraping and rendering JavaScript-heavy pages
- Screenshot and PDF generation for an app
- Running browser automation without Chrome on your own machine
Videos
Running Browserless on Railway
The Railway template deploys a single browserless service built from the repository omtera/browserless, described as using Chrome rather than Chromium. Connection endpoints, the access token, queue limits, concurrency and session timeouts are set through environment variables. The sources give no measured resource figures; browser sessions use memory and CPU while they run, so concurrency and timeout settings are the main cost levers.
Browserless templates on Railway
Tracklayer templates are listed first. Other Browserless templates follow, ordered by total deployments on Railway. How this works.
Deployment numbers as of 2026-11-20.
Questions about Browserless
How do I connect to it?
Open the browserless service's Variables tab for the endpoint and token settings, then point Playwright or Puppeteer at the service's WebSocket URL with the token. The template description does not list exact variable names.
Can I use it commercially?
Browserless is offered under SSPL-1.0 or a commercial licence, and its authors say closed-source commercial use needs a commercial licence. Read the current upstream terms or ask a lawyer before using it in a commercial product.
Should I expose it publicly?
Only with a token set. The template lists token-based security among its variables, so confirm a token is configured before adding a public domain, or keep it on Railway's private network for services in the same project.
What drives the cost?
Memory and CPU while browser sessions run. Lower the concurrency, queue and session timeout variables to cap usage.
Is there a template for Chrome instead of Chromium?
The listed template is described as Browserless V2 with Chrome rather than Chromium, built from the omtera/browserless repository.
Guides
Tracklayer maintains the templates marked as such; Browserless is a trademark of its owners and this site is not affiliated with them.
