> ## Documentation Index
> Fetch the complete documentation index at: https://docs.coreload.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Runners and labels

> How Coreload runs GitHub Actions jobs: a fresh VM for every job, the runs-on labels, and what the runner image includes.

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://docs.coreload.com/quickstart.md#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 |

**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.
* Use the labels we send you when we
  turn your organization on.
* New organizations start on the smallest size.
* A size with no price in the table isn't offered.
* Jobs you don't change keep running where they ran before.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.