Skip to main content

Enterprise Docker Image

The Enterprise Docker Image provides enhanced features and capabilities for production deployments. This image is available through our private registry and requires a valid license key to operate.

Prerequisites

Before getting started, you'll need:

  1. Registry Access: Credentials for our private Docker registry
  2. License Key: A valid enterprise license key provided by Browserless
  3. Docker or Docker Compose: Installed on your target system

Registry Access Setup

1. Docker Registry Login

First, authenticate with our private registry using the credentials provided by our team:

docker login registry.browserless.io

When prompted, enter your provided username and password.

2. Pull the Enterprise Image

Once authenticated, pull the latest enterprise image:

docker pull registry.browserless.io/browserless/browserless/enterprise:latest

The image supports multiple platforms (ARM64 and AMD64) and will automatically pull the correct version for your architecture.

Configuration

License Key Setup

The enterprise image requires a license key to operate. Configure this using the KEY environment variable:

Important

Use the KEY environment variable for your license, not TOKEN. The TOKEN variable is used for API authentication, while KEY is used for license validation.

Basic Docker Run

Here's a minimal example to run the enterprise image:

docker run \
-e KEY=your-license-key-here \
-p 3000:3000 \
registry.browserless.io/browserless/browserless/enterprise:latest

Docker Compose Configuration

For production deployments, we recommend using Docker Compose. Here's a complete example:

---
services:
browserless:
image: registry.browserless.io/browserless/browserless/enterprise:latest
container_name: browserless-enterprise
environment:
- KEY=your-license-key-here
ports:
- "3000:3000"
restart: unless-stopped

Environment Variables

The enterprise image supports all standard Browserless environment variables plus enterprise-specific options:

VariableDescriptionDefaultRequired
KEYEnterprise license key-
TOKENAPI authentication token (optional for local networks)-
CONCURRENTMaximum concurrent browser sessions10
DOWNLOAD_DIRDirectory for file downloads/tmp
DATA_DIRUser data directory for browser profiles/tmp
ALLOW_GETAllow GET requests for simple operationsfalse
ENABLE_CORSEnable CORS headersfalse
TZTimezone settingUTC

For a complete list of configuration options, see our Docker Configuration guide.

Connecting to the Enterprise Image

Local Network Access

For applications running on the same network as your Browserless container, you can connect without an API token:

const puppeteer = require('puppeteer-core');

const browser = await puppeteer.connect({
browserWSEndpoint: 'ws://localhost:3000/chromium'
});

const page = await browser.newPage();
await page.goto('https://example.com');
const screenshot = await page.screenshot();
await browser.close();

External Access with Token

For external access or additional security, configure a TOKEN and include it in your connection string:

const puppeteer = require('puppeteer-core');

const browser = await puppeteer.connect({
browserWSEndpoint: 'ws://your-server:3000/chromium?token=your-api-token'
});

Verification

After starting your container, verify it's running correctly:

  1. Health Check: Visit http://localhost:3000/pressure to check system status
  2. API Documentation: Visit http://localhost:3000/docs to view available endpoints
  3. WebSocket Test: Use the connection examples above to test browser automation

Troubleshooting

Common Issues

License Key Errors

  • Ensure you're using the KEY environment variable, not TOKEN
  • Verify your license key is valid and hasn't expired
  • Check that the key is properly formatted without extra spaces or characters

Registry Access Issues

  • Confirm you're logged into registry.browserless.io
  • Verify your registry credentials are still valid
  • Try pulling the image again if authentication fails

Connection Problems

  • For local networks, ensure no TOKEN is required in your connection string
  • For external access, verify the TOKEN environment variable matches your connection string
  • Check that the container port (3000) is properly exposed and accessible

Getting Help

If you encounter issues with the enterprise image:

  1. Check the container logs: docker logs your-container-name
  2. Verify your license key status through your account dashboard
  3. Contact our enterprise support team with your container configuration

Next Steps