Monk CI integration
Route jobs between Monk CI, your machines and GitHub.
Monk CI runs GitHub Actions jobs on its own machines, under your Monk CI account. Jobs go to your machines first and to Monk CI when they're busy. You change the order from the dashboard, not your workflows.
With routing
Monk CI on its own, or in your runner order
Monk CI on its own
- Each workflow names a Monk CI label, so every job runs on Monk CI.
- Your own machines sit idle while Monk CI 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 Monk CI when your machines are busy.
- GitHub-hosted runners stay as the fallback after Monk CI.
- Move Monk CI up, down or out from the dashboard. No workflow edits.
- The Performance page compares Monk CI's job times with your machines and GitHub-hosted runners.
Setup
How to set up Monk CI
-
Set up your Monk CI account
Sign up for Monk CI and have an organization owner install its GitHub App on the repos that should use it. It doesn't run personal accounts' repos.
-
Add Monk CI to your runner order
On the Router page, put Monk CI where you want it. A common order is your machines, then Monk CI, 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
monkci: monkci-ubuntu-24.04-2
github: ubuntu-latest
test:
needs: relay-test
runs-on: ${{ needs.relay-test.outputs.runner }}
The relay
Name a Monk CI 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
Monk CI at a glance
- What it is
- Hosted Linux runners for GitHub Actions.
- Labels
monkci-ubuntu-24.04-<vcpus>- Example
runs-on: monkci-ubuntu-24.04-2- Relay input
monkci- Links
- Monk CI docs Monk CI dashboard
Plans
Builds stop when the trial ends. Users are unlimited. GitHub organizations only.
| Plan | Monthly | Included |
|---|---|---|
| Free trial | No fee | 5,000 min for 14 days |
| Pro | $20 | 5,000 min a month |
| Max | $100 | 20,000 min a month |
| Custom | Contact sales | Custom |
From Monk CI's pricing page, checked Nov 17, 2026.
List prices
| Linux x64 | $0.002/min per vCPU |
|---|
As of November 2026, from Monk CI's price page. Monk CI bills you directly, so your plan and credits apply.
Common questions
How is this different from using Monk CI directly?
Used directly, every job that names a Monk CI label runs on Monk CI. In a runner order, jobs go to your own machines first and to Monk CI only when they're busy, and you can move Monk CI up, down or out from the dashboard without editing workflows.
Do I have to change my workflows to use Monk CI?
Once. Run npx relayrunner init in your repo and it adds a relay to each job you pick. After that, you move Monk CI up or down in the dashboard.
Which jobs go to Monk CI?
Jobs whose relay names a Monk CI label, when nothing above Monk CI in your runner order is free.
Who bills me for Monk CI?
Monk CI does. Jobs run under your own Monk CI account, so your plan, credits and discounts still apply.
Do public repos run on Monk CI?
Yes. Your own machines skip public repos' jobs, but hosted providers like Monk CI run them.
Can I use Monk CI with a personal GitHub account?
No. Monk CI 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 Monk CI 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