Runloft integration
Route jobs between Runloft, your machines and GitHub.
Runloft runs GitHub Actions jobs on its own machines, under your Runloft account. Jobs go to your machines first and to Runloft when they're busy. You change the order from the dashboard, not your workflows.
With routing
Runloft on its own, or in your runner order
Runloft on its own
- Each workflow names a Runloft label, so every job runs on Runloft.
- Your own machines sit idle while Runloft bills you.
- Trying another host means editing every workflow again.
- Each host shows its own job times in its own dashboard.
In your runner order
- Jobs run on your machines first, and on Runloft when your machines are busy.
- GitHub-hosted runners stay as the fallback after Runloft.
- Move Runloft up, down or out from the dashboard. No workflow edits.
- The Performance page compares Runloft's job times with your machines and GitHub-hosted runners.
Setup
How to set up Runloft
-
Set up your Runloft account
Sign in to Runloft with GitHub and install its GitHub App. Runners bigger than 2 vCPU, and Arm, Windows and macOS, run once Runloft turns them on for your account.
-
Add Runloft to your runner order
On the Router page, put Runloft where you want it. A common order is your machines, then Runloft, then GitHub-hosted.
-
Add relays to your jobs
Run
npx relayrunner initin your repo. It adds a relay to each job you pick and keeps the label the job uses today as its fallback.
jobs:
relay-test:
uses: relayrunner/actions/.github/workflows/relay.yml@v1
with:
machine: self-hosted
runloft: runloft-ubuntu-24.04
github: ubuntu-latest
test:
needs: relay-test
runs-on: ${{ needs.relay-test.outputs.runner }}
The relay
Name a Runloft label in the relay.
The relay answers in about a second and uses no minutes. It returns the label of the first runner in your order that can take the job, and the job runs there.
Read how routing works →Details
Runloft at a glance
- What it is
- Hosted runners for GitHub Actions, billed per second.
- Labels
runloft-*- Example
runs-on: runloft-ubuntu-24.04- Relay input
runloft- Links
- Runloft docs Runloft dashboard
Plans
Credit is prepaid from $5. Arm, Windows and macOS are turned on per account on request, and free minutes don't cover Windows or macOS.
| Plan | Monthly | Included |
|---|---|---|
| Pay as you go | No fee | 3,000 Linux min a month |
From Runloft's pricing page, checked Nov 17, 2026.
List prices
| Linux x64 | $0.0015/min per vCPU |
|---|---|
| Linux Arm | $0.0012/min per vCPU |
| Windows | $0.0035/min per vCPU |
| macOS | $0.06/min |
As of November 2026, from Runloft's price page. Runloft bills you directly, so your plan and credits apply.
Common questions
How is this different from using Runloft directly?
Used directly, every job that names a Runloft label runs on Runloft. In a runner order, jobs go to your own machines first and to Runloft only when they're busy, and you can move Runloft up, down or out from the dashboard without editing workflows.
Do I have to change my workflows to use Runloft?
Once. Run npx relayrunner init in your repo and it adds a relay to each job you pick. After that, you move Runloft up or down in the dashboard.
Which jobs go to Runloft?
Jobs whose relay names a Runloft label, when nothing above Runloft in your runner order is free.
Who bills me for Runloft?
Runloft does. Jobs run under your own Runloft account, so your plan, credits and discounts still apply.
Do public repos run on Runloft?
Yes. Your own machines skip public repos' jobs, but hosted providers like Runloft run them.
Which runners does Runloft have?
Every account starts with 2 vCPU Linux x64 runners. Larger sizes, Arm, Windows and macOS runners are turned on per account when you ask Runloft.
Add Runloft to your runner order.
Add relays once. After that, change the order in the dashboard.
-
1. In your repo, add relays to the jobs you want to route
npx relayrunner init -
2. Optionally, turn this computer into a runner
npx relayrunner connect