Skip to main content
Version: v2

Browsers as a Service

Browsers as a Service (BaaS) lets you connect Puppeteer or Playwright to managed browsers over WebSocket. Run your existing automation code by changing the connection URL to point at Browserless—no infrastructure management required.

When to Use BaaS v2​

Use BaaS v2 when you need to:

  • Run existing Puppeteer or Playwright code without changes
  • Maintain full browser control for complex workflows
  • Create multi-step automation sequences
  • Manage persistent browser sessions with state

How It Works​

Connect to Browserless by providing a WebSocket endpoint URL with your API token and optional launch parameters. Use standard Puppeteer connect() or Playwright connectOverCDP() methods. Sessions can be persisted and reconnected, and stealth mode is available via launch parameters.

Key Features​

  • Direct Browser Control: Use Puppeteer or Playwright APIs directly
  • Persistent Sessions: Maintain state across operations and reconnections
  • Stealth Mode: Bypass bot detection with evasion techniques
  • Hybrid Automation: Combine scripts with human interaction via LiveURL
  • Regional Load Balancing: Distribute load across multiple regions

Authentication​

BaaS connections require an API token included in the WebSocket URL. See the Quick Start guide for connection examples.

Next Steps​

Ready to dive deeper into BaaS? Explore these key areas to maximize your browser automation capabilities:

Creating a Session

Learn how to establish browser sessions with Puppeteer or Playwright for your automation needs.

Avoiding bot detection

Learn techniques and strategies to bypass sophisticated bot detection systems and CAPTCHAs.

Using Hybrid Automation

Combine automated scripts with human intervention for complex workflows and debugging scenarios.