BerryBox integration
Route jobs between BerryBox, your machines and GitHub.
BerryBox runs GitHub Actions jobs on its own machines, under your BerryBox account. Jobs go to your machines first and to BerryBox when they're busy. You change the order from the dashboard, not your workflows.
With routing
BerryBox on its own, or in your runner order
BerryBox on its own
- Each workflow names a BerryBox label, so every job runs on BerryBox.
- Your own machines sit idle while BerryBox 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 BerryBox when your machines are busy.
- GitHub-hosted runners stay as the fallback after BerryBox.
- Move BerryBox up, down or out from the dashboard. No workflow edits.
- The Performance page compares BerryBox's job times with your machines and GitHub-hosted runners.
Setup
How to set up BerryBox
-
Set up your BerryBox account
Sign up for BerryBox, install its GitHub App on your organization, add credit and turn on the sizes you want in team settings. It runs organizations' private repos only.
-
Add BerryBox to your runner order
On the Router page, put BerryBox where you want it. A common order is your machines, then BerryBox, 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
berrybox: berrybox-2vcpu-ubuntu-2404
github: ubuntu-latest
test:
needs: relay-test
runs-on: ${{ needs.relay-test.outputs.runner }}
The relay
Name a BerryBox 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
BerryBox at a glance
- What it is
- Hosted Linux runners for GitHub Actions, billed per second.
- Labels
berrybox-<vcpus>vcpu-ubuntu-2404- Example
runs-on: berrybox-2vcpu-ubuntu-2404- Relay input
berrybox- Links
- BerryBox docs BerryBox dashboard
Plans
Credit is prepaid, $20 at a time. Private repositories in GitHub organizations only.
| Plan | Monthly | Included | At once |
|---|---|---|---|
| Pay as you go | No fee | None | 16 vCPU |
| Build | $100 | $100 a month | 64 vCPU |
From BerryBox's pricing page, checked Nov 17, 2026.
List prices
| Linux x64 | $0.001/min per vCPU |
|---|---|
| Memory-heavy | $0.0015/min per vCPU |
As of November 2026, from BerryBox's price page. BerryBox bills you directly, so your plan and credits apply.
Common questions
How is this different from using BerryBox directly?
Used directly, every job that names a BerryBox label runs on BerryBox. In a runner order, jobs go to your own machines first and to BerryBox only when they're busy, and you can move BerryBox up, down or out from the dashboard without editing workflows.
Do I have to change my workflows to use BerryBox?
Once. Run npx relayrunner init in your repo and it adds a relay to each job you pick. After that, you move BerryBox up or down in the dashboard.
Which jobs go to BerryBox?
Jobs whose relay names a BerryBox label, when nothing above BerryBox in your runner order is free.
Who bills me for BerryBox?
BerryBox does. Jobs run under your own BerryBox account, so your plan, credits and discounts still apply.
Do public repos run on BerryBox?
No. BerryBox only runs jobs from private repositories, so a public repo's jobs go to the next runner in your order.
Can I use BerryBox with a personal GitHub account?
No. BerryBox only runs jobs for repositories owned by a GitHub organization. Jobs from a personal account's repos go to the next runner in your order.
Add BerryBox 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