1.2x to 2.1x faster than GitHub-hosted at 2 vCPU, measured on three open-source builds.
Change runs-on: and the same workflow runs on a size you pick for each job, up to 32 vCPU, with caches that survive between jobs.
Card required. 3,000 minutes a month at 2 vCPU are included.
1.2–2.1×
sooner: the same builds on GitHub's 2 vCPU runner and on ours
$0.012
a build here, against $0.034 on GitHub-hosted
32
vCPU at the largest, chosen for each job by its label
Three open-source projects, each at a pinned commit and built by its own command, on GitHub’s 2 vCPU runner and on ours. Each time is the whole job, start to finish. Your own gain depends on the job: a compile or a test suite spread over many files gains from more cores; a job that waits on the network does not.
eslint/eslint @ c27bc92, built with node Makefile mocharust-lang/cargo @ e8cb624, built with cargo build --release --lockedprometheus/prometheus @ d15adb9, built with go test ./tsdb/ -test.tsdb-isolation=falseEach time is the median of at least 21 approved rounds that both runners completed.
A compile or a test suite is limited by cores, and GitHub’s standard runner has 2 vCPU. Here the size is a label: up to 32 vCPU for the jobs that need it, and the default for the rest. The runner size guide says which jobs gain, and the runners page lists every size.
The Actions cache is included at no charge. A Docker layer cache that survives between jobs is an add-on at $0.50/GB-month of what it stores, with a build measured cold and warm.
A queued job is not billed here. If one waits longer than you expect, why jobs wait for a runner lists the causes.
Installing the App moves nothing: no job runs here until a workflow asks for one of our labels. Change runs-on yourself, or pick a repository and we open a pull request that changes it and nothing else. Its checks run on our runners, so you compare times on your own code before you merge. There is no per-seat fee, and a monthly spend cap you set stops new jobs when it is reached; running ones finish. How the migration goes; what each size costs a minute is on the pricing page.
While a job runs, its code and the secrets GitHub hands it are on a machine we operate, as on any runner you do not host yourself. Each job gets its own virtual machine, starting fresh and shared with no other job. Nothing a job leaves on its machine can be seen by another job.
The repositories you choose. GitHub will list read and write permissions, and each write has one use. Administration registers a single-use runner for each job and removes it. Contents, Workflows and Pull requests open the migration pull request. Actions cancels a run we refused, or one holding a job you stopped. Checks and Commit statuses report Terraform plans, if you connect Terraform. Your secrets, environments and branch protection stay on GitHub.
Change the label back and the job runs on GitHub again: the runs-on label is the only change a workflow needs, and your actions, secrets and triggers were never ours to untangle. Uninstall the App on GitHub and we see nothing more. We delete build output and test results 90 days after each job.
Card required. 3,000 minutes a month at 2 vCPU are included.