Documentation menu
Dashboard & analytics
Managed runners
Team & notifications
Billing & plans
Workflow files
Runner usage and free minutes
How managed runner minutes are metered, what the free tier covers, where usage appears, and what happens when free minutes run out.
In short
- Billed per minute, rounded up per job: small $0.0025 to xlarge $0.0200; custom runners at the xlarge rate.
- Free minutes reset on the 1st of each month (2,000/4,000/6,000 small-equivalent minutes by plan); only overage is billed.
- One-off jobs from the Latchkey CLI or an agent meter identically, from the same free-minute pool; their spend shows as a CLI jobs line on the Cost page.
- Warnings land at 80% and 100% either way: card-less workspaces block new jobs when exhausted, subscriptions keep running and meter the overage.
The Billing page of the acme workspace on a Scale subscription. The bill reads Plan $49.00 plus Runner minutes and Extra seats, both zero, equals Estimated total $49.00, with the plan charged Nov 18 and the runner minutes Nov 1. Runner usage this calendar month shows free minutes 4,200 of 6,000 small-equivalent minutes, the size weights small 1×, medium 2×, large 4× and xlarge 8×, and minutes by runner size with each size's rate. Batches of jobs finish and the bar fills by weight; at 81% a notice says runners keep running past the allowance and further minutes meter at each size's rate. At 6,000 of 6,000 the bar passes the marker, the free minutes are marked used up, and the notice gives the estimated overage so far, starting at 15 cents for the last job's 15 large minutes. By the end, 4,800 minutes have run, counted as 7,080 small-equivalent minutes; the line under the meter reads 1,080 small-equivalent min past your free allowance, and 675 minutes are billed for $2.70, and the bill reads $49.00 plus $2.70 plus zero for seats equals $51.70.
How metering works#
- Usage is billed per minute, rounded up per job. A 90-second job on
latchkey-smallis 2 minutes. - Each size has its own rate: small $0.0025, medium $0.0050, large $0.0100, xlarge $0.0200 per minute. Custom-configuration runners bill at the xlarge rate.
- Only time your job actually holds the runner is billed. A Latchkey CI job can set
timeout-minutesup to 180 (30 by default), and a Latchkey on GH runner runs for up to 4 hours from its start, or up to 8 when the job is still running at 4. - Self-healing carries no separate fee: extra runtime during a heal bills at the runner's standard per-minute rate.
- Flaky-test re-runs in learn-only mode are billed as runner minutes.
- One-off jobs from the Latchkey CLI or the MCP
run_jobtool meter the same way: same per-minute rates, same free-minute pool, rounded up per job. They default to a 30 minute timeout, extendable to 3 hours, and queue time is never billed. - Latchkey on GH runners carry the labels
self-hosted,LinuxandX64as well as their own, so in a monitored repository an idle one can take a job whoseruns-onnames no other label; such a job can then count toward Runners at once, bill at the rate of that runner's size, show on the Runs page as a Latchkey on GH job and, when it fails, count toward the "Pipeline is broken" notification. - Overage is charged on its own invoice on the 1st of each month (UTC), for the month just ended, separate from your plan's invoice.
Rounding happens per job, not per month, which matters when jobs are short: a 61-second job bills as 2 minutes, so a workflow that fans out into many one-minute jobs consumes minutes noticeably faster than its total wall-clock time suggests. If that ever becomes visible on your gauge, consolidating very short jobs is the lever.
The free tier#
| Plan | Free small-equivalent runner minutes per month |
|---|---|
| Developer | 2,000 |
| Launch | 4,000 |
| Scale | 6,000 |
| Enterprise | Custom |
Free minutes reset on the first of each calendar month. Minutes within the free tier cost nothing; only usage beyond it is billed at the per-minute rates. Free runner minutes are counted in small-equivalent units: a minute on latchkey-small counts as one, medium as two, large as four, and xlarge or a custom runner as eight, and the included allowance on every plan is unchanged.
A worked example#
The numbers below are illustrative; the rates and allowances are the real ones. Say a team on Launch (4,000 free small-equivalent minutes) runs 6,000 minutes of latchkey-small in a month, where one minute weighs one:
| Line | Amount |
|---|---|
Minutes metered on latchkey-small | 6,000 |
| Launch free tier | First 4,000 small-equivalent minutes at no cost, which is 4,000 minutes on latchkey-small |
| Billable minutes | 6,000 - 4,000 = 2,000 |
| Overage at $0.0025/min | 2,000 x $0.0025 = $5.00, on the runner minutes invoice on the 1st |
A bigger machine spends the allowance faster as well as costing more per minute. The same 6,000 minutes on latchkey-medium ($0.0050/min) weigh 12,000 small-equivalent minutes, so the 4,000-minute allowance covers 2,000 of them and the remaining 4,000 come to $20.00 of overage; on latchkey-large ($0.0100/min) the allowance covers 1,000 minutes and the remaining 5,000 come to $50.00. The calculator below runs the same arithmetic with your own numbers.
Estimate your cost#
Where to see usage#
- The Billing page shows a free-tier progress bar, this calendar month's total and billable minutes, and the estimated runner cost so far.
- The Runners page shows usage as it happens: how many runners are busy against your limit, the last hour by minute, what each size costs, and this month's free minutes.
- The Cost page tracks Latchkey runner spend, with a meter of the free minutes used this calendar month.
- Jobs started from the Latchkey CLI or an agent appear on the Cost page as their own CLI jobs line; follow individual jobs from the CLI itself (
latchkey status,latchkey logs).
Running out of free minutes#
- Workspaces without a card on file are warned at 80%, at most once a day, and again at 100%, once per calendar month, when Latchkey stops running jobs and holds new ones until a plan starts or the minutes reset.
- With a subscription on file: you are warned at 80% and again at 100%, at most once per calendar month per threshold, and jobs keep running while the overage is metered to your invoice, up to the spend limit an owner or admin can set on the Billing page.
- On a card-less trial: once free minutes are exhausted, Latchkey stops running jobs and holds new managed-runner jobs until you subscribe or the minutes reset. Held jobs stay queued on GitHub (no error in the GitHub UI), and the month's "Free tier running out" notification says so; no "Managed runner blocked" notification follows it.
The timeline at a glance#
Treat the 80% warning as the decision point rather than the 100% one: a fifth of the tier is still left, which is room to either trim usage (the Cost page shows where the spend is coming from) or accept the overage knowingly. With a subscription on file and no spend limit set, accepting is a perfectly valid answer; it should just be a chosen one.
If launches are blocked#
Held jobs sit in queued on GitHub with no error, and the month's "Free tier running out" notification names the stop. The free-tier gauge (on the Billing page or the Runners page) confirms the state: 100% used on a card-less trial.
New managed-runner jobs are blocked until you subscribe, so adding a subscription is the direct fix; with one on file, usage beyond the free tier simply meters to your invoice instead of blocking.
Free minutes reset on the first of the calendar month. Until then, urgent workflows can point back at GitHub-hosted labels, which keep working side by side with latchkey-* labels the whole time.
Q.01How are runner minutes metered?
Per minute, rounded up per job, from $0.0025 for small to $0.0200 for xlarge; custom runners meter at the xlarge rate. Rounding is per job, so many very short jobs cost more than the raw minutes suggest.
Q.02When do free minutes reset?
On the first of each month, at 2,000, 4,000 or 6,000 small-equivalent minutes depending on plan. Only usage beyond the allowance is billed, so a month that stays inside the allowance costs nothing in runner minutes.
Q.03Do CLI and agent jobs use the same free minutes?
Yes. One-off jobs started from the Latchkey CLI or an AI agent meter identically and draw from the same monthly pool. Their spend appears separately as a CLI jobs line on the Cost page so you can see it without it being hidden inside workflow costs.