Documentation menu
Dashboard & analytics
Managed runners
Team & notifications
Billing & plans
Workflow files
Cost analysis
See what your Latchkey runner minutes cost as the bill charges them, track your free minutes, and find the repositories that spend the most.
In short
- Spend is what the bill charges for runner minutes in the selected dates; minutes a free allowance covered are not charged.
- Highest spend and Repository costs find the repositories that cost the most; Free minutes follows your Latchkey plan minutes.
- The CLI jobs line holds jobs started from the Latchkey CLI or the run_job MCP tool, which belong to no repository.
- The Latchkey runners strip and Free minutes always reflect the current calendar month, regardless of the date filter.
The Cost page answers "where does our CI money go?" for the jobs that ran on Latchkey runners.
The Cost overview of the acme workspace on the Scale plan, with 6,000 free small-equivalent minutes this calendar month. Spend reads zero billed over 30 days, nothing billed the week before, and Highest spend reads No repository was charged in the selected dates. As batches of jobs finish, Free minutes used climbs from 3,960 to 4,580, 5,140, 5,620 and 6,000 of 6,000 while Free minutes left falls from 2,040 to 0, and the 20-block meter fills, its last four blocks turning amber past 80%; Spend and the estimated cost this calendar month stay at zero. Once the allowance is spent, the next jobs bill at their size's rate: Spend and the estimated cost climb to 40 cents, 87 cents and $1.21, Highest spend lists acme/api at 75 cents, acme/web at 24 cents and acme/worker at 22 cents, and the line under the meter reads 484 small-equivalent min past your free allowance.
The page is organized into three sections: Cost overview (the headline KPIs), Cost analysis (the charts you drill into), and Latchkey runner costs (what each of your managed runner configurations cost). Cost overview links View billing, which opens the Billing page, and Latchkey runner costs links View runners, which opens the Runners page. Before any of that is useful, though, you need to know what the headline counts.
What Spend counts#
Spend is what the bill charges for runner minutes in the selected dates, at each runner size's price. Minutes a free allowance covered are not charged, so a workspace inside its allowance reads $0 while its jobs still run. Every cost figure on the page is read from your Latchkey billing records.
Cost overview section#
- Spend, with its change week over week: Spend over the last 7 days with runs against the 7 before them. Until the range holds 14 days with runs the change reads "too few billed days to compare", and when those earlier 7 days cost nothing it reads "nothing billed the week before" (in Pro).
- Highest spend: your top 3 repositories by Spend for the selected dates, each linking to the repository on GitHub. Only repositories that were charged appear; when none was, the card reads "No repository was charged in the selected dates."
- Latchkey runners, this calendar month: three figures, Estimated cost this calendar month, Free minutes left and Free minutes used, in small-equivalent minutes (a plan with no free allowance shows Minutes used instead). When runner usage does not load, each reads "Unavailable" instead of a figure.
- Free minutes: a block meter of the free small-equivalent minutes your plan includes this calendar month, beside the small-equivalent weights by runner size (in Pro); past the allowance, a line under the meter counts them, for example "484 small-equivalent min past your free allowance". When runner usage does not load, the meter is not drawn and the panel reads "Unavailable" with "runner usage did not load".
Cost analysis section#
- Cost over time: Spend by day over your selected date range.
- Repository costs: Spend per repository, with a Top 5 / Bottom 5 switch.
A reading tip for this section: on Cost over time, a stretch at $0 is a stretch your free minutes covered; the line starts to rise once they run out.
Latchkey runner costs section#
If you run jobs on managed runners, this section appears with a per-configuration cost table: Configuration (in Pro, with the runner label you use in workflow files, such as latchkey-small), Type (Preset or Custom, in Pro), Jobs, Avg duration, and Cost, each configuration's minutes at list price for the selected period, before free minutes. When free minutes were used, a footer shows "Free tier applied: X / Y small-equivalent min" (in Pro) and "Saved $Z", what those free minutes would have cost, so the table's figures can add up to more than Spend. The Latchkey runners strip and Free minutes in Cost overview always reflect the current calendar month, independent of the date-range filter.
CLI jobs line#
If your team runs one-off jobs from the Latchkey CLI or the MCP run_job tool, that spend appears as its own CLI jobs line, with the period's spend and job count. These jobs belong to no repository and no workflow, so this line is the money the repository breakdown cannot place; they are counted in Spend. The line hides while a repository or workflow filter is active, and it disappears entirely in periods with no CLI jobs.
Filters on this page#
The page draws the repository, workflow and date filters, as Command & Control and Performance do. Every figure on this page is a Latchkey runner's. Show decimals, under Display in the Account and help menu, switches dollar figures between cent precision and rounded whole dollars. The exceptions to the date filter: the Latchkey runners strip and Free minutes always reflect the current calendar month.
Export#
Export, in the title bar, downloads the page's figures as a CSV file named for the first and last days it covers, one row per figure under the columns Panel, Name, Figure, Value and Unit. It carries every repository the page read, not only the bars and ranked rows the panels draw, each day of Cost over time, the Latchkey runners strip once runner usage loads, the CLI jobs line when it shows, and the Runner costs table. Pressed before the runner costs have loaded, Export loads them first and then downloads. It is unavailable while the costs or runner usage load.
Which chart answers which question#
| You want to know | Look at |
|---|---|
| Is CI spend trending up or down? | Spend and its week-over-week trend badge |
| Which repositories cost the most? | Highest spend, then Repository costs with the Top/Bottom switch |
| When exactly did the spike happen? | Cost over time, with the date range narrowed around it |
| What will the invoice look like? | Estimated cost this calendar month, in the Latchkey runners strip |
| How close are we to using up free minutes? | The Free minutes meter |
| What is each runner size costing us? | The Runner costs table under Latchkey runner costs |
| What did our one-off CLI and agent jobs cost? | The CLI jobs line |
Using this page to actually cut cost#
A suggested routine when spend needs to come down. Nothing here is enforced by the product; it is simply the order in which the charts answer each other's questions:
Start with Spend and its week-over-week badge. If the trend is flat, you are optimizing a stable bill; if it is climbing, you are chasing a change, and the rest of the pass is about finding when and where.
Open Highest spend and Repository costs. CI spend is usually concentrated: a small number of repositories tend to carry most of the bill, so effort spent on the top of this chart pays off far more than anywhere else.
Use the repository and workflow filters to zoom into one candidate, and read Cost over time for the selected range. This usually pinpoints the day a spike started and the workflow responsible.
Check AI Insight: nightly analysis surfaces quantified cost findings, and when Latchkey can make the change for you, such as downsizing an oversized runner, the finding offers it as a pull request you approve. If the issue is free-tier exhaustion rather than waste, see Runner usage and free minutes and Managing billing.
Metric reference#
| Metric | What it tells you |
|---|---|
| Spend | What the bill charges for runner minutes in the selected dates, at each runner size's price; minutes a free allowance covered are not charged |
| Week over week | Percent change in Spend, the last 7 days with runs vs the 7 before them; a dash until the range holds 14 days with runs, or while those earlier 7 days cost nothing |
| Highest spend | Your top 3 repositories by Spend for the selected dates; only repositories that were charged appear |
| Free minutes | "X / Y min used" meter of your plan's free small-equivalent minutes this calendar month |
| Cost over time | Spend by day over the selected dates |
| Free tier applied: X / Y min | Latchkey free minutes applied against your plan's included minutes, and their dollar value, in the runner-costs table footer |
| CLI jobs | Spend and job count for jobs started from the Latchkey CLI or the run_job MCP tool; they belong to no repository, so they show here and inside Spend, not in the repository breakdown |
To model spend before it lands on this page - a new repo, a bigger runner, more jobs - use the GitHub Actions cost calculator on Learn, or browse the CI cost guides for pricing mechanics across providers.
Q.01Why do the Latchkey runners strip and Free minutes ignore my date filter?
The Latchkey runners strip and Free minutes always reflect the current calendar month, whatever range the filter is set to. They answer what you owe and what is left this month, which is a calendar-month question, not a date-range one. The other charts on the page do follow the filter.