1.4.0: Authentication and local storage

Source: Dev.to

Release 1.4.0 Overview

BlitzBrowser 1.4.0 adds a built‑in authentication layer and enables local‑disk storage of user data by default.

• Previously, persisting user data required an S3‑compatible provider (e.g., AWS, Cloudflare R2, RustFS).
• Now you can mount a local directory into the Docker container, eliminating the need for external storage for local development, integration tests, or simple deployments.

Local Storage

Mount a volume at /blitzbrowser/user-data inside the container to have user data persist across restarts.

services:
  blitzbrowser:
    image: ghcr.io/blitzbrowser/blitzbrowser:latest
    ports:
      - "9999:9999"
    volumes:
      - ./user-data:/blitzbrowser/user-data
    shm_size: "2gb"
    restart: always

Built‑in Authentication

API Access (BlitzBrowser)

All CDP and HTTP connections must include a valid API_KEY. You can provide it in either of the following ways:

• HTTP header
  x-api-key: ${API_KEY}
• Query parameter
  apiKey=${API_KEY}

Dashboard Access

Users must supply an AUTH_KEY to log in. The dashboard uses the BLITZBROWSER_API_KEY environment variable to communicate with the API.

For complete setup instructions, refer to the dashboard and BlitzBrowser configuration documentation.