Self-host Browserless with Levelrail
A headless Chrome browser exposed as an HTTP/WebSocket API for scraping and PDF rendering.
- Authorbrowserless
- LicenceSSPL-1.0 OR LicenseRef-Browserless-Commercial
- Memory1 GiB
- Archarm64
- Services1
How to self-host Browserless
-
Pull the images
One image is pulled on your server.
Show images
ghcr.io/browserless/chromium:v2.8.0
-
Create the app
One service starts in a single Compose app, on port 3000.
-
Fill in the secrets
1 secret is generated and stored encrypted, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
Browserless requirements
- Memory
- About 1 GiB
- Architectures
- amd64 image published, arm64 image published
- Ports
- 3000
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- SSPL-1.0 OR LicenseRef-Browserless-Commercial, source available
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
- Host ports. It publishes port 3000 on the host, so open them in the VPS firewall only if you want that.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Browserless. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the Browserless docs page.
Deploy Browserless your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Browserless from the CLI
levelrail-cli templates deploy browserless --name my-browserless Deploy Browserless with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/browserless/deploy Browserless configuration
Browserless services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| browserless | ghcr.io/browserless/chromium:v2.8.0 | 3000 | none |
Browserless environment variables
| Variable | Service | Value |
|---|---|---|
| TOKEN | browserless | Generated at deploy |
Ports and volumes
- Ports
- 3000
- Volumes
- none
Browserless FAQ
How much memory does Browserless need?
The catalog lists about 1 GiB of memory for Browserless.
Does Browserless run on arm64?
For Browserless, an arm64 image is published; amd64 is image published.
What licence is Browserless under?
Browserless is licensed under SSPL-1.0 OR LicenseRef-Browserless-Commercial, which is source-available, so read the terms before commercial use.
Does Browserless need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which ports does Browserless use?
Browserless listens on port 3000 inside the stack.
Can I deploy Browserless on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id browserless for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image ghcr.io/browserless/chromium:v2.8.0 is what you deploy there.