Direct answer

Workers are operator-provisioned processes that execute eligible browser work.

Each worker connects outbound over WebSocket with an individual credential bound to one workspace and advertises the capabilities it can perform.

01

How dispatch works

The backend considers connected, session-ready workers in the run's workspace. An idle matching worker receives either a Playwright test assignment or a bounded discovery frontier item.

02

Who controls capacity

You control where worker processes run and how many exist. BernOps concurrency settings limit consumption of that capacity; they do not start workers, reserve replicas, or supply infrastructure isolation.

EARLY ACCESS

Bring browser operations into focus.

Join the waitlist