CAPABILITYWorkspace-bound workers

Your browser capacity, attached to the right workspace.

A worker connects outbound to BernOps, advertises implemented capabilities, and executes one assignment at a time. Dispatch filters connected capacity by workspace before selecting a worker.

Join the waitlist
LIVE MODELCAPACITY / WS-01
runner-01ready / test
runner-02ready / test
explorer-03busy / discovery
runner-04offline
workspace / northstar3 / 4
00 / CONTROL SURFACE
01

MODULE / 01

No cross-workspace scheduling pool

Each worker uses its own workspace-bound credential. Eligible projects can share that workspace capacity, but assignments do not cross the credential boundary.

  • Credential digest and revocation state are durable
  • Live worker capacity is process-local
  • Capabilities gate discovery and test work
02

MODULE / 02

Concurrency is a ceiling

Workspace, project, and job limits decide whether pending work may consume connected capacity. They do not create worker processes or reserve replicas.

03

MODULE / 03

Infrastructure stays explicit

Operators decide where and how many workers run and provide any required container or VM isolation. BernOps coordinates eligible work; it does not claim autoscaling or workload isolation.

CONTINUE MAPPING

Playwright automationApplication discovery / BetaAutomation observability

EARLY ACCESS

Bring browser operations into focus.

Join the waitlist