Coreload: GitHub Actions runners Alternatives to GitHub-hosted runners
Each service below runs GitHub Actions jobs in place of GitHub-hosted runners; how each one is set up is on its own pages, linked from its compare page. On Coreload you change a job's runs-on label, and jobs you don't change keep running on GitHub-hosted runners, so you can try one job first.
Coreload
- One VM per job. Each job runs in a fresh VM on bare-metal machines, and the VM is deleted when the job ends.
- Measured, not claimed. We publish what we measured, with the method, the number of runs, the date and the raw data, on the benchmarks page.
- Prices and sizes. See Pricing and Sizes.
- Coreload and GitHub-hosted runners side by side: Coreload vs GitHub-hosted.
Other hosted runner services
Each link opens a page that quotes the provider's own pages, with a link to each page and the date we read it.
- Blacksmith: what Blacksmith publishes, and how to move a job from Blacksmith.
- Namespace: what Namespace publishes.
- Depot: what Depot publishes.
- RunsOn: what RunsOn publishes.
Your own machines
GitHub also lets you register machines you run yourself as self-hosted runners.
Questions
- How do I switch a job from GitHub-hosted runners? Install the GitHub App, then change
runs-onon the job to the label we send you. Jobs you don't change keep running on GitHub-hosted runners. - Which alternative is fastest? It depends on the job and the size. We publish only what we measured, on the benchmarks page, with the method and the raw data.