# Runners and labels

Each job runs in a fresh VM that serves that job alone and is destroyed when the job ends. Today that VM runs a
Debian image, not yet GitHub's Ubuntu image, so Docker and some setup actions don't work yet: see
[What runs today](https://coreload.com/quickstart/#what-runs-today). 

| `runs-on:` | Machine | Price |
| --- | --- | --- |
| `coreload` | 2 vCPU · 7 GiB | $0.00114 / min |
| `coreload-4vcpu` | 4 vCPU · 12 GiB | $0.00228 / min |
| `coreload-8vcpu` | 8 vCPU · 32 GiB | $0.00418 / min |
| `coreload-16vcpu` | coming | — |
| `coreload-32vcpu` | coming | — |

**Beta pricing: published before we bill anything**

- Put exactly one Coreload label in `runs-on`, on its own. A job that also asks for `self-hosted` or `linux` won't
  start on Coreload.
- Every organization gets the `coreload` label. (coming soon) Until then, use the labels we send you when we
  turn your organization on.
- New organizations start on the smallest size; every offered size for every organization (coming soon).
- A size marked "coming" isn't offered yet.
- Jobs you don't change keep running where they ran before.