Migrate to Latchkey in 10 Minutes

No pipeline rewrite, no new YAML to learn. Connect, swap a label, done.

Latchkey runs your existing GitHub Actions workflows on managed runners with self-healing built in. Setup is a connect-and-relabel flow you can finish over a coffee.

The 10-minute migration

1. Sign up and install the Latchkey GitHub App on your org or repo.
2. Pick the runner sizes you want (small / medium / large).
3. Change runs-on: to the Latchkey label on one workflow.
4. Push and watch the job run on a Latchkey runner - same logs, lower cost.
5. Roll out to the rest of your workflows by label.

jobs:
  test:
    runs-on: latchkey-small   # was: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - run: ./run-tests.sh

What you get immediately

• Managed runners at roughly 69% lower per-minute cost than GitHub-hosted.
• Built-in dependency and Docker layer caching.
• Self-healing: transient and mechanical failures are detected, fixed, and retried automatically.
• A dashboard for cost, performance, and healing analytics.

Key takeaways

• No workflow rewrite - just a label swap.
• About 10 minutes from signup to first job.
• Self-healing and lower cost from the first run.

Frequently asked questions

Related guides