Skip to content

Workers

A worker is a machine that runs DevBoxes for ClusterCode. It connects outbound to the orchestrator over WebSocket and executes DevBox operations locally using Podman.

This is Bring Your Own Machine: any computer you already own — a spare laptop, a desktop under a desk, a $6/mo VPS — becomes AI compute for your cluster. No GPU bills, no per-token compute margin, and machines you’ve already paid for finally earn their keep. Prefer not to run hardware? Cloud workers give you the same API on rented machines.

The Workers page lists every machine connected to your orchestrator, with live CPU, memory, disk, and DevBox counts:

console.clustercode.io Workers
The Workers page showing three connected self-hosted workers, each card listing tenant, CPU, memory, disk, DevBox count, last heartbeat, and status. The Workers page showing three connected self-hosted workers, each card listing tenant, CPU, memory, disk, DevBox count, last heartbeat, and status.

Self-hosted workers are machines you control — your laptop, a spare desktop, a cloud VM, a NAS. You install the CLI, register the machine, and it becomes a worker.

Advantages:

  • Full control over hardware and network
  • No per-minute compute costs
  • Works behind NAT and firewalls (outbound connection only)
  • Use existing machines you already own

Requirements:

  • Node.js 22+
  • Podman installed and running
  • Network access to the orchestrator (outbound WebSocket)

Cloud worker is ClusterCode’s managed compute offering. Instead of running workers on your own machines, Cloud worker provides cloud workers that are always on, always available.

Advantages:

  • No hardware to maintain
  • Always-on availability
  • Scales with your plan
  • Supports both Linux and Windows DevBoxes

When to use Cloud worker:

  • You don’t have spare machines
  • You need Windows DevBoxes
  • You want zero infrastructure management
  • You need workers in specific geographic regions

See the Cloud worker guide for setup details.

Worker Agent (your machine)
│ WebSocket (outbound, authenticated)
Orchestrator (cloud or on-premises)
│ Sends DevBox operations
Worker Agent executes via Podman

Workers phone home — they initiate the connection outbound. This means:

  • No port forwarding required
  • Works behind corporate firewalls
  • Works behind NAT routers
  • No static IP needed on the worker

If the connection drops, the agent reconnects automatically.

Resource FreeStarterProEnterprise
Self-hosted workers (BYOM) 2 5 25 100 20×
Concurrent DevBoxes 4 10 50 200 20×

/ 20× mark limits where Pro is exactly 5× Starter and Enterprise 20×.

See Plans & Limits for the full breakdown.