Per machine
| Setting | What it does |
|---|---|
| Pause | The machine takes no new jobs. Stages already serving finish their run. |
| Power share | 5 to 100 percent of the machine: the threads a CPU stage may use, and the memory each backend lends unless set below. Half by default. |
| Backends and memory | Which of its GPU, graphics card and RAM it lends, each with an amount in GiB if you want a fixed one. A graphics card lends only what you set, since its memory cannot be measured from the worker. |
| Hours | Always, or only between two hours of the machine’s own clock — overnight, say. Outside them it takes nothing. |
| Job kinds | Model stages (and the probes before them), and research shards: batch generation that runs whole small models on the CPU. Stages only, by default. |
| Jobs at once | 1 to 8. A machine serves one stage per backend at a time in any case. |
| Community pool | Offers the machine, within this share, to other organizations’ community keys. Model stages only. Off by default; free during the beta. |
| Network | Which of your networks it belongs to. Keys reach the machines of their own network. |
The machine’s card shows what it lends right now, how many jobs it served and for how long — including for the community — and its state: ready, serving, paused, outside its hours or offline.
Who may change what
Compute follows the organization’s roles. Owners and admins connect and remove machines, change their settings, create and revoke join codes and keys, create networks and cancel jobs. Viewers see machines, networks and jobs, but not keys or codes. A platform owner sees no other organization’s machines unless they belong to it.
Audit
Every change is recorded in the organization’s audit trail: a machine joining (with the code’s creator), each settings change and which fields it touched, keys and codes created and revoked, machines removed, jobs cancelled.
On iPhone and iPad
The Hostwatch app lists your machines with their state and what they lend. Pause or resume one, move its power share, switch its backends and job kinds, set its hours or offer it to the community pool, and create a join code to show on the machine you are setting up.
What the worker does with them
Settings reach the worker with its heartbeat, every fifteen seconds. It applies them before its next lease: new probes and stages use the new threads and memory, and jobs it no longer takes stay in the queue for other machines. Hostwatch enforces the same limits on its side — a paused machine is never handed a job, and a coordinator cannot address work to a machine that does not take that kind.