Skip to main content

Enterprise Docker Overview

The Enterprise Docker image lets you run Browserless on your own infrastructure. You get full control over where your data lives, how your containers scale, and what network policies apply. The image supports the same APIs, WebSocket connections, and browser automation features as all other Browserless deployment options.

Self-hosting is a good fit when you need data sovereignty, air-gapped environments, or custom network configurations that a managed deployment cannot provide. If you prefer Browserless to manage infrastructure for you, see Private Deployment.

Self-Hosting Features​

Running your own containers means you control the full stack:

  • Deployment Guide: Pull the Enterprise image, configure your token, and start running browsers in minutes.
  • Configuration Reference: Tune concurrency, timeouts, queue behavior, health checks, and security settings through environment variables.
  • NGINX Load Balancing: Distribute traffic across multiple Browserless containers with sticky sessions and health-check routing.
  • Extending the Image: Install custom fonts, packages, or browser extensions by building on top of the base image.
  • Webhooks: Receive HTTP callbacks when sessions are queued, rejected, timed out, or hit errors.
  • OpenTelemetry: Export traces, metrics, and logs to any OTLP-compatible backend for observability.

Getting started​

Pull the Enterprise image and start a container:

docker run --rm -p 3000:3000 -e TOKEN=YOUR_API_TOKEN_HERE ghcr.io/browserless/chromium

Connect your automation code to ws://localhost:3000/chromium?token=YOUR_API_TOKEN_HERE and you're running. See the Deployment Guide for full setup and configuration details.