Runner pools: each cloud, and each of your computers, is a pool of its own. Drag pools to reorder them; each has its settings (jobs at once, a monthly budget; a computer is removed there).
Machines: pick CPU, memory, disk, architecture and system to get the runs-on label, and see which pools can run it. Use as default sets what plain runs-on: superci gets.
Rules by repository are gone from the page: a workflow picks a pool in its label instead (runs-on: superci/provider=aws).
Machine sizes in the label, in any order: runs-on: superci/cpu=8, ram=32, disk=100, arch=arm64, os=macos, spot=false, or a provider (provider=aws, cloudflare, modal).
A default machine for runs-on: superci, set on the Runners page.
Places in order, each with jobs at once and dollars a month. When every place is full, jobs wait for one.
Your own computers: run superci join with a link from the dashboard. Linux jobs run in Docker, macOS jobs on the Mac.
A computer that goes offline: jobs it had not begun move to the next place.
The dashboard says when your control plane needs an update, and updates it.