Browserless V2 w/ Chrome not Chromium

Deploys Browserless V2 as a single service built from the repository omtera/browserless, described as using Chrome rather than Chromium. Gives you a remote headless browser to drive from Playwright or Puppeteer code over WebSocket.

What you get

  • One Railway service named browserless, built from the repository omtera/browserless
  • A headless Chrome browser server, described as Chrome rather than Chromium
  • Token-based access control through environment variables
  • WebSocket and Playwright support, with connection endpoints configured through variables
  • Settings for queue limits, concurrency and session timeouts
  • Variables for choosing public or private access

Good for

  • A remote browser for Playwright or Puppeteer scripts so Chrome does not run locally
  • Rendering and scraping pages that need JavaScript
  • Giving other services in the same Railway project a shared browser to connect to

Services in this template

  • browserless · from omtera/browserless

Questions people ask

How do I connect to it?

The template's description says connection endpoints, token security and WebSocket and Playwright support are set through environment variables. Open the browserless service's Variables tab to find the endpoint and token settings; the sources available here do not give exact variable names.

Is it protected by a token?

The description lists token-based security among the configured variables. Check the Variables tab after deploying to confirm a token is set before exposing the service on a public domain.

What drives the cost?

The sources give no measured figures. On Railway's usage billing, a browser server's cost follows its memory and CPU while sessions run, so the queue limit, concurrency and session timeout variables are the main levers to review.

Is data kept across redeploys?

The sources do not mention a volume. Treat browser sessions as temporary unless you confirm otherwise in the service settings.

Who maintains it, and what licence applies?

The marketplace lists Tracklayer as the template's creator, and the service builds from omtera/browserless. The sources do not state licence terms. Browserless is published with licence conditions that can apply to commercial use, so check the upstream project's current terms before relying on it commercially.

Full template README

These environment variables configure a secure Browserless server with Chrome for headless browsing. They define connection endpoints, token-based security, WebSocket/Playwright support, queue limits, concurrency, session timeouts, and public/private access.

Guides for this template

View Browserless V2 w/ Chrome not Chromium on railway.com

Similar templates

TemplateCategoryDeploymentsDeploys
Chatwoot
A customer communication platform
Other5,871
Ubuntu-Linux
Ubuntu terminal accessible via web browser
Other4,926
Ubuntu SSH + Claude
ARA TM —SSH server with root access + Claude Code pre-installed.
Other4,682
Debian-Linux
Debian terminal accessible via web browser.
Other2,883
Code Server
VS Code in the browser
Other2,787
Kali Linux (Web Terminal)
Instant Kali Linux browser terminal powered by ttyd
Other2,632