Ubicloud integration
Route jobs between Ubicloud, your machines and GitHub.
Ubicloud runs GitHub Actions jobs on its own machines, under your Ubicloud account. Jobs go to your machines first and to Ubicloud when they're busy. You change the order from the dashboard, not your workflows.
With routing
Ubicloud on its own, or in your runner order
Ubicloud on its own
- Each workflow names a Ubicloud label, so every job runs on Ubicloud.
- Your own machines sit idle while Ubicloud 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 Ubicloud when your machines are busy.
- GitHub-hosted runners stay as the fallback after Ubicloud.
- Move Ubicloud up, down or out from the dashboard. No workflow edits.
- The Performance page compares Ubicloud's job times with your machines and GitHub-hosted runners.
Setup
How to set up Ubicloud
-
Set up your Ubicloud account
Sign up for Ubicloud and install its GitHub App on your organization.
-
Add Ubicloud to your runner order
On the Router page, put Ubicloud where you want it. A common order is your machines, then Ubicloud, 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
ubicloud: ubicloud-standard-2
github: ubuntu-latest
test:
needs: relay-test
runs-on: ${{ needs.relay-test.outputs.runner }}
The relay
Name a Ubicloud 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
Ubicloud at a glance
- What it is
- Hosted runners for GitHub Actions.
- Labels
ubicloud, ubicloud-*- Example
runs-on: ubicloud-standard-2- Relay input
ubicloud- Links
- Ubicloud dashboard
List prices
| Standard | $0.00063/min per vCPU |
|---|---|
| Premium | $0.001/min per vCPU |
As of November 2026, from Ubicloud's price page. Ubicloud bills you directly, so your plan and credits apply.
Common questions
How is this different from using Ubicloud directly?
Used directly, every job that names a Ubicloud label runs on Ubicloud. In a runner order, jobs go to your own machines first and to Ubicloud only when they're busy, and you can move Ubicloud up, down or out from the dashboard without editing workflows.
Do I have to change my workflows to use Ubicloud?
Once. Run npx relayrunner init in your repo and it adds a relay to each job you pick. After that, you move Ubicloud up or down in the dashboard.
Which jobs go to Ubicloud?
Jobs whose relay names a Ubicloud label, when nothing above Ubicloud in your runner order is free.
Who bills me for Ubicloud?
Ubicloud does. Jobs run under your own Ubicloud account, so your plan, credits and discounts still apply.
Do public repos run on Ubicloud?
Yes. Your own machines skip public repos' jobs, but hosted providers like Ubicloud run them.
Add Ubicloud 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
