# Fast GitHub Actions runners on AMD Zen 5

Change one line of your workflow. Every job gets its own fresh VM on a desktop-class AMD Zen 5 CPU.

[Install the GitHub App](https://github.com/apps/coreload-ci) · [Read the quickstart](https://coreload.com/quickstart/)

```diff
 jobs:
   test:
-    runs-on: ubuntu-latest
+    runs-on: coreload
```

Beta: install the App, and we turn your organization on by hand and send you its label.

- **AMD Zen 5 desktop CPUs.** High clocks and strong single-thread speed, which is what most CI steps wait on.
- **A fresh VM for every job.** It never serves a second job, and its disk and memory are deleted when the job ends.

## How it works

1. **Install the GitHub App.** Pick the repositories it may serve. During the beta, we turn your organization on by hand
   and send you its label; jobs wait until then.
2. **Change one line.** Set `runs-on:` to the label we send you on the jobs you want faster. Jobs you don't change keep
   running where they ran before.
3. **Each job gets its own VM.** A fresh VM starts for the job, runs it, and is deleted when it ends.

## Sizes, one label each

| `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**

New organizations start at 2 vCPU.

## Security and isolation

- **One VM per job.** Each job runs in a fresh VM that never serves a second job or a second customer. Its disk and
  memory are deleted with it when the job ends.
- **We don't store your secrets.** A secret your workflow passes to a job is visible inside that job's VM while it
  runs, so pass short-lived, least-privilege credentials.
- **The App asks for little.** It registers single-use runners in its own runner group, and has no access to your
  repository contents, issues, pull requests or secret values.
- **Where jobs run.** On bare-metal machines, each job in a fresh VM.

[Read the security model](https://coreload.com/docs/security/)

## Pricing

Coreload is in beta. Pricing is published before we bill anything.

## Questions

- **How do I switch from GitHub-hosted runners?** Install the GitHub App, then change `runs-on` on a job to the label we
  send you. Jobs you don't change keep running where they ran before.
- **How do I switch from Blacksmith?** Change `runs-on` from your Blacksmith label to the label we send you, matching
  sizes by vCPU; new organizations start at 2 vCPU. Install the GitHub App first, then follow the
  [migration guide](https://coreload.com/migrate/blacksmith/).
- **What is a vCPU on Coreload?** One CPU of the job's VM, on an AMD Zen 5 desktop machine. We will state whether it is
  a hardware thread or a core when the per-size benchmark is published.
- **Which sizes are there?** The sizes in the [size table](https://coreload.com/sizes/). New organizations start at 2 vCPU.
- **Where do my jobs run?** On bare-metal machines, each job in a fresh VM that is deleted when the job ends.
- **Personal accounts?** Not yet: organizations only, private repositories only.
- **What does it cost?** Pricing is published before we bill anything.

## On the roadmap (coming soon)

Coming soon: not available yet.

- One label, `coreload`, for every organization, with no manual turn-on.
- 4 and 8 vCPU for every organization, then 16 and 32 vCPU, in the same shapes as Blacksmith.
- An Ubuntu 24.04 image like GitHub's, with Docker.
- A Coreload cache next to the machines, with nothing to set up: dedicated machines first, then the shared pool.
- Per-second billing from a prepaid balance.
- A public status page.
- A per-size speed comparison against Blacksmith, with a benchmark you can run.

## Run your next job on Coreload

[Install the GitHub App](https://github.com/apps/coreload-ci) · [Read the quickstart](https://coreload.com/quickstart/)