Documentation · Getting started

What runners.io is

One product with two execution engines — managed GitHub Actions runners and Terraform-compatible runs — on one meter and one bill.

One product with two execution engines, sold on one meter and one bill.

• CI runners. Managed GitHub Actions runners. You change the runs-on: label in a workflow and the job runs on our runners instead of GitHub's. Everything else about the workflow is unchanged: your actions, your secrets, your environments, your OIDC, your matrix builds, your status checks.

• Infrastructure runs. A hosted platform that speaks the Terraform Enterprise API. You point a cloud block at tf.runners.io and plan and apply execute on our infrastructure, with the state stored and versioned here.

The two halves share an account, an organisation, a usage meter and an invoice. You can use either on its own.

tf.runners.io is an API host and nothing else. It answers the paths the Terraform CLI and the tfe provider use, and turns everything else away — there is no site there to visit. Anything you would look at with your eyes is on the dashboard.

We would rather tell you before you try than after.

• Linux on x64 only. No ARM, no Windows, no macOS.

• No nested virtualisation. There is no /dev/kvm inside a job, so an Android emulator or a nested hypervisor will not run. Docker containers are unaffected and work normally.

• No GPUs.

• No SSH-into-a-failed-job.

• No policy-as-code for infrastructure runs, and drift detection is not available yet.

The comparison pages keep the current version of this list beside what everyone else offers, and are checked against their documentation rather than their pricing pages.

• Quickstart — a first job on our runners, step by step.

• Connect your account — the GitHub App for CI, and the token for infrastructure runs.

• Runner labels — the exact strings a runs-on: accepts.

• Moving from GitHub-hosted runners

• Moving from HCP Terraform