GitHub Actions costs, ranked by Job group.
See what changed and the evidence worth checking.
Last 7 days · Compared with the previous four-week median. Select a Job to inspect it.
Ubuntu · 42 executions in the last 7 days
+$8.20 (+64.1%) above the baseline
More executions and longer average duration coincide with the increase. Check the runs before drawing a conclusion.
A cost total tells you where to look. The runs help you decide what to check.
Keep the Job, its runner and its execution history together. Separate what the data shows from what still needs an explanation.
Explore the Job previewThree of 42 executions · Ubuntu · Illustrative data
| Execution | Trigger | Duration | Est. cost |
|---|---|---|---|
| #1842Oct 9 · 14:08 UTC | Pull request | 68 min | $0.544 |
| #1841Oct 9 · 11:32 UTC | Push | 61 min | $0.488 |
| #1838Oct 8 · 16:45 UTC | Pull request | 65 min | $0.520 |
42 runs, up from a median of 32. Average duration: 62.5 min, up from 50 min.
Review triggers and the longer runs. Neither observation establishes why the Job changed.
A quick public scan first. A place for your private repositories when you are ready.
See the five highest-cost Job groups from the last 30 days, basic evidence and up to two simple suggestions.
Start a free public scanLog in, install the read-only GitHub App and choose your repository. Your Free workspace includes basic results and manual refresh.
Create your free workspaceMonitor up to ten private repositories. Open full Job evidence, review weekly summaries and receive high-priority anomaly emails.
See what Pro includesYou choose the repositories. We read repository metadata, Actions metadata and workflow files to estimate resource use.
No business source, secrets or full logs. No automatic YAML edits or repair pull requests.
Choose the depth you need. Every plan keeps estimated costs clearly labelled.
Public scans and a basic private workspace.
Full analysis across up to 10 private repositories.
Pro starts after you connect GitHub, choose repositories and activate a subscription. Historical views build with available data; retention is not an initial 180-day import.
Clear boundaries make the numbers more useful.
No. We estimate gross resource-use costs from GitHub-hosted runner type and execution duration. Your final bill can differ because of allowances, discounts and billing rules. Public repositories typically do not incur GitHub-hosted runner charges.
It identifies a Job worth checking. Changes in execution count, duration or runner use can coincide with higher estimates. The evidence supports your investigation; it does not establish a root cause or guarantee savings.
Yes. After logging in and connecting GitHub, the Free workspace supports one private repository with basic results and manual refresh. Pro unlocks full analysis, more private repositories and continuous monitoring.
Comparisons and recommendations are reduced when history or data coverage is insufficient. The product shows that limitation rather than inventing a baseline. Longer historical views become available as data is collected.
No. The GitHub App is read-only. Pro can provide eligible, copyable YAML suggestions with supporting evidence, but you review and apply any changes yourself. We do not create repair pull requests.
Self-hosted infrastructure costs are outside the current estimate model. Actions Cost Guard focuses on GitHub-hosted runners and makes unsupported coverage visible.
See the Job groups behind the estimate.
Decide what deserves a closer look.