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