Skip to main content
BCTRL provides cloud infrastructure for automation. Instead of managing browsers and desktops locally, they run on our infrastructure and you control them via SDK.

Mental Model

BCTRL separates where automation runs from how you control it:

Infrastructure Layer (Where)

The compute resources that run your automation:
  • Cloud Browsers - Remote Chrome instances with anti-detection
  • Cloud Computers - Full Windows and Linux virtual machines
  • Local Desktop - Your own machine (for development/testing)

Control Layer (How)

The tools you use to automate:
  • Web Drivers - Playwright, Puppeteer, Selenium for browser control
  • Desktop Control - Mouse, keyboard, and screen capture
  • AI Agents - Stagehand and CUA for natural language automation

Architecture Diagram

┌─────────────────────────────────────────────────────────────┐
│                     Control Layer                           │
│  ┌──────────────┐  ┌──────────────┐  ┌──────────────┐      │
│  │  Playwright  │  │   Desktop    │  │  AI Agents   │      │
│  │  Puppeteer   │  │    Mouse     │  │  Stagehand   │      │
│  │  Selenium    │  │   Keyboard   │  │  CUA         │      │
│  └──────────────┘  └──────────────┘  └──────────────┘      │
└─────────────────────────────────────────────────────────────┘

                        BCTRL SDK

┌─────────────────────────────────────────────────────────────┐
│                  Infrastructure Layer                       │
│  ┌──────────────┐  ┌──────────────┐  ┌──────────────┐      │
│  │    Cloud     │  │    Cloud     │  │    Local     │      │
│  │   Browsers   │  │  Computers   │  │   Desktop    │      │
│  └──────────────┘  └──────────────┘  └──────────────┘      │
└─────────────────────────────────────────────────────────────┘

Infrastructure Layer

The infrastructure layer provides the compute resources where automation executes.

Cloud Browsers

Remote Chrome instances with anti-detection. Perfect for web scraping and browser automation at scale.

Cloud Computers

Full Windows and Linux VMs. Run any desktop application, install software, and automate complex workflows.

Local Desktop

Connect to your own machine for development and testing. Same API, local execution.

Control Layer

The control layer provides the tools and APIs you use to automate the infrastructure.

Web Drivers

Use Playwright, Puppeteer, or Selenium with the exact same API you already know. Your code works unchanged.

Desktop Control

Direct mouse movements, keyboard input, and screen capture. Control any application like a human would.

AI Agents

Stagehand for web and CUA for desktop. Use natural language to describe what you want to automate.

Request Flow

  1. You call SDK method - e.g., await page.goto('https://example.com')
  2. SDK sends HTTP request - To Control Plane with session ID and command
  3. Control Plane routes - Finds the host agent running your session
  4. Host Agent executes - Runs the command on the actual browser/desktop
  5. Response returns - Back through the chain to your code

Key Concepts

ConceptDescription
SessionA browser or desktop instance you control
ProfileBrowser fingerprint configuration
PageA browser tab
ContextIsolated browser environment (cookies, storage)
DriverAutomation library (Playwright, Puppeteer, etc.)

Why Remote?

Scale

Run hundreds of browsers or desktops without managing infrastructure

Anti-Detection

Built-in fingerprinting for browsers

No Local Resources

Browsers and VMs don’t consume your CPU/RAM

Global Locations

Run from different geographic locations

Timeouts

OperationDefault Timeout
Standard commands30 seconds
Code execution (exec)60 seconds
AI agents5 minutes
Sessions automatically close after 30 minutes of inactivity (configurable).