← All integrations

Latchkey integration

Route jobs between Latchkey, your machines and GitHub.

Latchkey runs GitHub Actions jobs on its own machines, under your Latchkey account. Jobs go to your machines first and to Latchkey when they're busy. You change the order from the dashboard, not your workflows.

Get started with GitHub

With routing

Latchkey on its own, or in your runner order

Latchkey on its own

  1. Each workflow names a Latchkey label, so every job runs on Latchkey.
  2. Your own machines sit idle while Latchkey bills you.
  3. Trying another host means editing every workflow again.
  4. Each host shows its own job times in its own dashboard.

In your runner order

  1. Jobs run on your machines first, and on Latchkey when your machines are busy.
  2. GitHub-hosted runners stay as the fallback after Latchkey.
  3. Move Latchkey up, down or out from the dashboard. No workflow edits.
  4. The Performance page compares Latchkey's job times with your machines and GitHub-hosted runners.

Setup

How to set up Latchkey

  1. Set up your Latchkey account

    Sign up for Latchkey and install its GitHub App on your organization. Its runners don't take personal accounts' repos, and its $5 plan covers one repo.

  2. Add Latchkey to your runner order

    On the Router page, put Latchkey where you want it. A common order is your machines, then Latchkey, then GitHub-hosted.

  3. Add relays to your jobs

    Run npx relayrunner init in your repo. It adds a relay to each job you pick and keeps the label the job uses today as its fallback.

.github/workflows/ci.yml
jobs:
  relay-test:
    uses: relayrunner/actions/.github/workflows/relay.yml@v1
    with:
      machine: self-hosted
      latchkey: latchkey-small
      github: ubuntu-latest
  test:
    needs: relay-test
    runs-on: ${{ needs.relay-test.outputs.runner }}

The relay

Name a Latchkey 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

Latchkey at a glance

What it is
Hosted Linux runners for GitHub Actions.
Labels
latchkey-small, -medium, -large, -xlarge
Example
runs-on: latchkey-small
Relay input
latchkey
Links

Plans

Launch has a 30-day trial. Minutes count as latchkey-small minutes. Extra seats are $5 each. GitHub organizations only.

Plan Monthly Included Jobs at once, repos, seats
Developer $5 2,000 min a month 20 jobs, 1 repo, 1 seat
Launch $19 4,000 min a month 40 jobs, 10 repos, 3 seats
Scale $49 6,000 min a month 80 jobs, 40 repos, 5 seats
Enterprise Contact sales Custom Custom

From Latchkey's pricing page, checked Nov 17, 2026.

List prices

latchkey-small $0.0025/min
latchkey-medium $0.005/min
latchkey-large $0.01/min
latchkey-xlarge $0.02/min

As of November 2026, from Latchkey's price page. Latchkey bills you directly, so your plan and credits apply.

Common questions

How is this different from using Latchkey directly?

Used directly, every job that names a Latchkey label runs on Latchkey. In a runner order, jobs go to your own machines first and to Latchkey only when they're busy, and you can move Latchkey up, down or out from the dashboard without editing workflows.

Do I have to change my workflows to use Latchkey?

Once. Run npx relayrunner init in your repo and it adds a relay to each job you pick. After that, you move Latchkey up or down in the dashboard.

Which jobs go to Latchkey?

Jobs whose relay names a Latchkey label, when nothing above Latchkey in your runner order is free.

Who bills me for Latchkey?

Latchkey does. Jobs run under your own Latchkey account, so your plan, credits and discounts still apply.

Do public repos run on Latchkey?

Yes. Your own machines skip public repos' jobs, but hosted providers like Latchkey run them.

Can I use Latchkey with a personal GitHub account?

No. Latchkey 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 Latchkey to your runner order.

Add relays once. After that, change the order in the dashboard.

  1. 1. In your repo, add relays to the jobs you want to route
    npx relayrunner init
  2. 2. Optionally, turn this computer into a runner
    npx relayrunner connect