Lizard integration
Route jobs between Lizard, your machines and GitHub.
Lizard runs each GitHub Actions job in its own Firecracker VM, under your Lizard account. Jobs go to your machines first and to Lizard when they're busy. You change the order from the dashboard, not your workflows.
With routing
Lizard on its own, or in your runner order
Lizard on its own
- Each workflow names a Lizard label, so every job runs on Lizard.
- Your own machines sit idle while Lizard 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 Lizard when your machines are busy.
- GitHub-hosted runners stay as the fallback after Lizard.
- Move Lizard up, down or out from the dashboard. No workflow edits.
- The Performance page compares Lizard's job times with your machines and GitHub-hosted runners.
Setup
How to set up Lizard
-
Set up your Lizard account
Sign up for Lizard, open GitHub Actions in its dashboard and connect your organization. Its runners don't take personal accounts' repos.
-
Add Lizard to your runner order
On the Router page, put Lizard where you want it. A common order is your machines, then Lizard, 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
lizard: lizard-medium-ubuntu-2404
github: ubuntu-latest
test:
needs: relay-test
runs-on: ${{ needs.relay-test.outputs.runner }}
The relay
Name a Lizard 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
Lizard at a glance
- What it is
- Linux runners for GitHub Actions on Lizard's Firecracker VMs, billed per second.
- Labels
lizard-small, -medium, -large-ubuntu-2404- Example
runs-on: lizard-medium-ubuntu-2404- Relay input
lizard- Links
- Lizard docs Lizard dashboard
Plans
Plans cover all of Lizard (apps, databases, Sandboxes), and usage past the plan's is pay as you go, per second. The trial needs a card, and once a size's trial jobs are used, jobs of that size are skipped until Pro. GitHub organizations only.
| Plan | Monthly | Included | Jobs at once |
|---|---|---|---|
| Trial | No fee | 50 small, 20 medium, 10 large jobs | 5 jobs, 7 days |
| Pro | $19 | $19 usage a month | 5 jobs |
| Pro 5x | $99 | $99 usage a month | 20 jobs |
| Pro 20x | $499 | $499 usage a month | 20 jobs |
| Enterprise | Contact sales | Custom | Custom |
From Lizard's pricing page, checked Nov 18, 2026.
List prices
| lizard-small | $0.00027/min |
|---|---|
| lizard-medium | $0.00054/min |
| lizard-large | $0.00108/min |
As of November 2026, from Lizard's price page. Lizard bills you directly, so your plan and credits apply.
Common questions
How is this different from using Lizard directly?
Used directly, every job that names a Lizard label runs on Lizard. In a runner order, jobs go to your own machines first and to Lizard only when they're busy, and you can move Lizard up, down or out from the dashboard without editing workflows.
Do I have to change my workflows to use Lizard?
Once. Run npx relayrunner init in your repo and it adds a relay to each job you pick. After that, you move Lizard up or down in the dashboard.
Which jobs go to Lizard?
Jobs whose relay names a Lizard label, when nothing above Lizard in your runner order is free.
Who bills me for Lizard?
Lizard does. Jobs run under your own Lizard account, so your plan, credits and discounts still apply.
Do public repos run on Lizard?
Yes. Your own machines skip public repos' jobs, but hosted providers like Lizard run them.
Can I use Lizard with a personal GitHub account?
No. Lizard 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.
What happens when Lizard's trial jobs run out?
The trial runs 50 small, 20 medium and 10 large jobs. Once a size's jobs are used, Lizard skips jobs of that size until you start Pro. On Pro, usage past the plan's included amount is billed as you go, and jobs past its 5 at once wait in Lizard's queue.
Add Lizard 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