Skip to content
Latchkey home
Documentation menu

What is Latchkey?

Latchkey is a standalone CI/CD platform built for coding agents: it runs your workflow files on fresh VMs, heals transient failures mid-run, and shows what each run cost and why it failed. Teams that keep their GitHub Actions workflows can run them on Latchkey's managed runners.

free trial
30 days
no credit card required
per runner minute
$0.0025
58% under GitHub-hosted
free minutes/month
2,000+
small-equivalent, every plan
to start Latchkey CI
1 file
under .latchkey/workflows/

In short

  1. Latchkey is standalone CI/CD built for coding agents: Latchkey CI runs your workflow files, Latchkey on GH runs GitHub Actions jobs on managed self-healing runners, and the dashboard shows the work Latchkey runs.
  2. Connects through a GitHub App. A personal account runs Latchkey CI; Latchkey on GH (Latchkey's managed runners in GitHub Actions) needs a GitHub organization.
  3. Your first workspace starts a 30-day Launch trial with no credit card; runners from $0.0025/min with 2,000+ free small-equivalent minutes monthly.
app.latchkey.dev / acme / overview

The Command & Control page at the Pro level, as an owner sees it. The title bar holds the date window set to 30d, Export, and Apply all 1. AI Insight: Self-heal · last 30 days, Autonomous, 39 failures healed on the runner, 1,240 min of re-runs avoided and $3.10 not spent at list rate, the healed failures by category (network 18, memory 9, disk 4, missing tools 6, config drift 2), and 2 failures left for you beside Outcome report. Beside it, Insight · ready to apply, with a 5 open findings chip: 1 finding ready to apply, the line 1 ships as a pull request now. 2 need an engineer: self-heal could not fix them., the open findings by pillar (Cost 0, Security 1, Reliability 4, Adoption 0), and Refreshed nightly beside Review 5 findings. Below it, Pipeline performance: workflow health 84% successful, down 4 pts on the prior 30 days, on a meter with its 50% threshold; 322 total runs, up 18%; average duration 4m 12s, 9% faster; mean time to recovery 3m, down 1m. While a workflow runs, a network failure that self-heal fixed raises the healed count to 40 and the run total to 323, without a reload.

FIG. 1.1-AThe dashboard's home page: what self-heal fixed on your runners, the findings that wait for your yes, and how your pipelines are doing. It refreshes by itself while workflows run. Only an owner or admin of the workspace sees Apply all.

Latchkey runs your CI in two ways:

Either way, the dashboard and AI Insight read run data only from the work Latchkey runs: Latchkey CI runs, CLI jobs and Latchkey on GH jobs. Runs on other runners never reach them, so installing the app alone shows no run data.

You can start either way. Latchkey CI starts with one committed file. Latchkey on GH is adopted one job at a time by changing a single runs-on: line, and GitHub-hosted labels (ubuntu-latest and friends) keep working side by side while you migrate. Coding agents drive both, and run one-off jobs from the terminal, through the Latchkey CLI and the MCP server.

How Latchkey connects to GitHub#

01
Install the GitHub App
On an organization, or a personal account for Latchkey CI
02
Pick repositories
Only repos you enable are monitored
03
Commits and jobs arrive
Pushes, pull requests and queued jobs reach Latchkey by webhook
04
Latchkey runs the work
Runs and costs fill the dashboard as Latchkey runs your jobs

There are no agents to install in your repositories and no changes to your existing workflows until you choose to make them.

"No agents" is worth spelling out. Latchkey learns about your pipelines from workflow events delivered to the GitHub App and from reading the workflow YAML under .github/workflows/. Nothing is installed in your repositories, and your CI keeps running exactly as before. Latchkey reads more than workflow files, though: when you enable a repository it indexes the repository's docs and CI config and scans its file layout, and when a step fails on a Latchkey runner, self-heal reads the step's output and can read the job's files. When a pull request runs on Latchkey CI, Latchkey also reads the list of files the pull request changes. Security and GitHub permissions lists everything Latchkey reads and what each read is for.

How Latchkey compares to GitHub-hosted runners alone#

This comparison is about the runners: what changes when a job moves from a GitHub-hosted runner to a Latchkey runner.

GitHub-hosted runners alone
  • 2 vCPU Linux runners at the $0.006/min list price
  • A transient failure (a registry timeout, an OOM kill, a full disk) stays red until a human notices and clicks re-run
  • Free minutes are whatever your GitHub plan includes
The same jobs on Latchkey runners
  • From $0.0025/min (latchkey-small), 52 to 58% less per runner minute than GitHub-hosted
  • Self-healing detects and fixes transient failures during the run, so the build goes green without a human re-run
  • 2,000+ free small-equivalent minutes every month: 2,000 on Developer, 4,000 on Launch, 6,000 on Scale
  • One job per runner, with no inbound access, destroyed after the job

Adoption is incremental by design: because both label families keep working side by side, you can move one job, watch it for a week, and expand from there. Run your first job walks through the one-line change, and the Managed runners overview has the full size and price table.

What it costs to try#

Your first workspace starts with a 30-day free trial of the Launch plan, with no credit card: new workspaces begin on Launch automatically. During the trial, choosing Developer, Launch or Scale under Plans on the Billing page and pressing Confirm opens Stripe Checkout, which asks for a card and charges the plan's first month when you finish. The paid plan starts then, Launch included, and the rest of the trial is not carried over. Developer needs a workspace with one member. Plans start at $5/month, and every plan includes free managed-runner minutes each month, counted in small-equivalent units (2,000 on Developer, 4,000 on Launch, 6,000 on Scale). There is one free trial per person; subscribing or changing plans later does not restart it. See Plans and the free trial for details.

What you need#

  • A GitHub account: a personal account runs Latchkey CI, and Latchkey on GH needs a GitHub organization account.
  • For an organization, the owner role on it, because the GitHub App asks for organization permissions and GitHub lets only an owner install such an app. If you are not an owner, ask one to install it.
  • A tablet, laptop or desktop screen for the dashboard. A screen narrower than 768 px shows a notice after sign-in that a larger screen is needed. Notifications by email, Slack, and push keep you covered away from your desk.

Choose your path#

Q.01What is Latchkey?

A standalone CI/CD platform, built for coding agents. You commit a workflow file, and Latchkey queues it, runs every job on a fresh Linux VM, heals transient failures mid-run, keeps the logs and run pages, and reports back to your pull request as checks. Your coding agents drive the same CI through a CLI and an MCP server. Teams that want to keep their GitHub Actions workflows can use Latchkey on GH, Latchkey's managed runners for GitHub Actions. The dashboard shows the work Latchkey runs: what it cost, how long it took and why it failed.

Q.02Do I need a GitHub organization to use Latchkey?

Not for Latchkey CI: a personal account connects and runs it; select the repository in the dashboard, then commit a workflow file under .latchkey/workflows/ and push. Latchkey on GH does need the GitHub App on an organization; if you work in a personal account, create a free organization and transfer the repository into it before installing.

Q.03What does it cost to try Latchkey?

Your first workspace starts with a 30-day free trial of the Launch plan, with no credit card required. During the trial, choosing Developer, Launch or Scale under Plans opens Stripe Checkout, which asks for a card and charges the plan's first month when you finish. Developer needs a workspace with one member. Runners start at $0.0025 per minute, and each plan includes at least 2,000 free small-equivalent runner minutes a month. The trial itself never charges you: until you choose a plan, Latchkey stops starting jobs once the trial's free minutes or its 30 days run out.