InstaBox integration
Route jobs between InstaBox, your machines and GitHub.
InstaBox runs GitHub Actions jobs on its own machines, under your InstaBox account. Jobs go to your machines first and to InstaBox when they're busy. You change the order from the dashboard, not your workflows.
With routing
InstaBox on its own, or in your runner order
InstaBox on its own
- Each workflow names a InstaBox label, so every job runs on InstaBox.
- Your own machines sit idle while InstaBox 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 InstaBox when your machines are busy.
- GitHub-hosted runners stay as the fallback after InstaBox.
- Move InstaBox up, down or out from the dashboard. No workflow edits.
- The Performance page compares InstaBox's job times with your machines and GitHub-hosted runners.
Setup
How to set up InstaBox
-
Set up your InstaBox account
Sign up for InstaBox and connect GitHub from the CI page of its dashboard. The Free plan runs instabox-medium only.
-
Add InstaBox to your runner order
On the Router page, put InstaBox where you want it. A common order is your machines, then InstaBox, 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
instabox: instabox-medium
github: ubuntu-latest
test:
needs: relay-test
runs-on: ${{ needs.relay-test.outputs.runner }}
The relay
Name a InstaBox 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
InstaBox at a glance
- What it is
- Linux runners for GitHub Actions on InstaBox's sandboxes.
- Labels
instabox-*- Example
runs-on: instabox-medium- Relay input
instabox- Links
- InstaBox docs InstaBox dashboard
Plans
Usage is $0.004 per vCPU-hour plus $0.00225 per GiB-hour, billed per second, on top of the plan.
| Plan | Monthly | Included | At once |
|---|---|---|---|
| Free | No fee | None | 1 machine, instabox-medium only |
| Pro | $20 | $20 a month | 100 machines, up to 8 vCPU |
| Builder | $100 | $100 a month | 200 machines, up to 16 vCPU |
| Team | $500 | $500 a month | 500 machines, up to 32 vCPU |
| Enterprise | Contact sales | Custom | Custom |
From InstaBox's pricing page, checked Nov 17, 2026.
List prices
| instabox-small | $0.00028/min |
|---|---|
| instabox-medium | $0.00057/min |
| instabox-large | $0.00113/min |
| instabox-xlarge | $0.00227/min |
| instabox-2xlarge | $0.00453/min |
As of November 2026, from InstaBox's price page. InstaBox bills you directly, so your plan and credits apply.
Common questions
How is this different from using InstaBox directly?
Used directly, every job that names a InstaBox label runs on InstaBox. In a runner order, jobs go to your own machines first and to InstaBox only when they're busy, and you can move InstaBox up, down or out from the dashboard without editing workflows.
Do I have to change my workflows to use InstaBox?
Once. Run npx relayrunner init in your repo and it adds a relay to each job you pick. After that, you move InstaBox up or down in the dashboard.
Which jobs go to InstaBox?
Jobs whose relay names a InstaBox label, when nothing above InstaBox in your runner order is free.
Who bills me for InstaBox?
InstaBox does. Jobs run under your own InstaBox account, so your plan, credits and discounts still apply.
Do public repos run on InstaBox?
Yes. Your own machines skip public repos' jobs, but hosted providers like InstaBox run them.
Which runners does InstaBox's free plan run?
Only instabox-medium (4 vCPU). Other sizes need a paid plan, and InstaBox leaves jobs for them queued until you have one.
Add InstaBox 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