CI/CD
GitHub Actions pricing calculator: what your minutes cost
The calculator below works out your GitHub Actions bill under GitHub's own rules: every job rounded up to the whole minute, included usage as a dollar amount, larger runners priced by size. CRACI runs the same workflows about twice as fast, at a lower price per minute, billed per second. A 10-minute build costs about 67% less.
Updated
GitHub Actions pricing calculator
There are two ways in. I know my minutes takes the minutes per runner from your usage report. Estimate from my team builds them from how your team works: developers, pushes, runs, jobs and job length. Both apply GitHub's rules: each job rounded up to the whole minute, included usage as a dollar amount, larger runners only on Team and Enterprise Cloud, and standard runners free in public repositories. Linux jobs from 1 to 32 vCPU move to CRACI at the same size; everything else stays on GitHub-hosted runners, with the included usage applied to it. The estimate covers compute only: storage for artifacts, caches and packages is billed separately and is not modelled. To find your minutes, see how to find your real usage.
| Runner | GitHub minutes | GitHub | CRACI | CRACI, twice as fast | Note |
|---|---|---|---|---|---|
| Linux x64, 2 vCPU | 20,000 | $120.00 | $80.00 | $40.00 |
With the calculator's starting values (GitHub Team, private repositories, 20,000 minutes a month on Linux x64 2 vCPU), GitHub's spend is $120.00 before included usage. The plan's $18.00 of included usage covers 3,000 of those minutes, so the bill is $102.00. The same minutes on CRACI cost $80.00, about 22% less: the price per minute is lower, but CRACI has no included minutes. At about twice the speed they cost $40.00, about 61% less. Nothing stays on GitHub in this example; add a Windows or macOS row and it stays on GitHub-hosted, with the included usage applied to what stays. Enter your average job length and the CRACI figures usually drop further, because CRACI bills the seconds a job runs, not whole minutes.
When CRACI is not the answer
- If your usage fits inside the included usage, or your repositories are public and run on standard runners, GitHub costs you nothing and CRACI will not lower the bill. CRACI has no included minutes; the startup program is the only free route.
- If most of your minutes are macOS or Windows, CRACI cannot run them today: it is Linux only, with Windows and macOS on the roadmap.
- On ARM64, GitHub's list price matches CRACI's at 4 vCPU and is lower from 8 vCPU up.
In those cases the reason to look at CRACI is the build record and the egress policy, not the invoice. To compare every provider's price, not only GitHub's, see the CI runner price comparison.
How GitHub Actions is billed
Every GitHub plan includes Actions usage each month: $12 on GitHub Free, $18 on Pro and Team, and $300 on Enterprise Cloud, which buys 2,000, 3,000 and 50,000 minutes on a standard 2-core Linux runner. Standard GitHub-hosted runners are free in public repositories, and GitHub does not charge per minute for self-hosted runners. Beyond the included minutes, private repositories pay per minute of runner time, and the price depends on the runner's size, operating system and architecture. See what free CI minutes cover, and what they leave out.
As of November 11, 2026, a standard 2-core Linux x64 runner costs $0.006 per minute. Two rules make the bill bigger than the price suggests:
- Every job is rounded up to the whole minute. A 10-second job is billed as a full minute, and a workflow with ten short jobs pays for at least ten minutes.
- Larger runners are billed even in public repositories. On Team and Enterprise Cloud they draw on the included usage at their own, higher rate, so it runs out sooner.
In GitHub's words, included usage is "expressed as a monetary amount, not a fixed number of minutes". The minute figures are what it buys on a standard 2-core Linux runner; every pricier runner uses it up faster. GitHub emails you when included Actions usage reaches 90% and 100%, and a budget can stop metered Actions usage at a limit you set.
GitHub Actions pricing per minute, every runner size
GitHub-hosted runner prices per minute as of November 11, 2026, beyond included minutes. Linux runners from 1 to 32 vCPU can run on CRACI at $0.002 per vCPU-minute, on x64 and ARM64 alike. CRACI is Linux only today; Windows and macOS are on the roadmap.
| Capability | CRACI | GitHub Linux x64 | GitHub Linux ARM64 |
|---|---|---|---|
| 1 vCPU | $0.002 | $0.002 | - |
| 2 vCPU | $0.004 | $0.006 | $0.005 |
| 4 vCPU | $0.008 | $0.012 | $0.008 |
| 8 vCPU | $0.016 | $0.022 | $0.014 |
| 16 vCPU | $0.032 | $0.042 | $0.026 |
| 32 vCPU | $0.064 | $0.082 | $0.050 |
| 64 vCPU | - | $0.162 | $0.098 |
| 96 vCPU | - | $0.252 | - |
| Capability | GitHub Windows x64 | GitHub Windows ARM64 |
|---|---|---|
| 2 vCPU | $0.010 | $0.010 |
| 4 vCPU | $0.022 | $0.014 |
| 8 vCPU | $0.042 | $0.026 |
| 16 vCPU | $0.082 | $0.050 |
| 32 vCPU | $0.162 | $0.098 |
| 64 vCPU | $0.322 | $0.194 |
| 96 vCPU | $0.552 | - |
| Capability | Price per minute |
|---|---|
| macOS macos-latest (M1), 3 vCPU | $0.062 |
| macOS xlarge (M2 Pro), 5 vCPU | $0.102 |
| macOS macos-15-intel, 4 vCPU | $0.062 |
| macOS large (Intel), 12 vCPU | $0.077 |
| GPU Linux, 1x Tesla T4, 4 vCPU | $0.052 |
On Linux x64, CRACI lists a lower price than GitHub from 2 vCPU up. On ARM64, GitHub's list price is lower from 8 vCPU up; per-second billing and faster builds narrow or close that gap on real pipelines.
What a minute costs: CRACI vs GitHub-hosted
| Capability | CRACI | GitHub-hosted | Difference |
|---|---|---|---|
| 2 vCPU Linux x64 | $0.004 | $0.006 | CRACI about 33% less |
| 2 vCPU Linux ARM64 | $0.004 | $0.005 | CRACI 20% less |
| 32 vCPU Linux x64 | $0.064 | $0.082 | CRACI about 22% less |
| Metering | Per second | Each job rounded up to the minute | No rounding on CRACI |
CRACI's list price is lower on standard Linux runners, and it bills per second. The per-minute gap is about 33% on 2 vCPU x64; on real pipelines, most of the saving comes from dropping the rounding. On ARM64, GitHub's list price matches CRACI's at 4 vCPU and is lower from 8 vCPU up: $0.014 against $0.016 a minute at 8 vCPU. For every provider's prices, see GitHub Actions runners compared.
Faster builds use fewer minutes
The price per minute is only half of the bill; the other half is how many minutes a build takes. CRACI runs builds about twice as fast as GitHub-hosted runners, thanks to faster hardware, shorter queue times and caching. A build that takes 10 minutes on a GitHub-hosted 2-core runner takes about 5 on CRACI, and you pay for those 5.
| Capability | CRACI | GitHub-hosted | CRACI saves |
|---|---|---|---|
| Build time | About 5 minutes | 10 minutes | About half the wait |
| One build, 2 vCPU x64 | $0.020 | $0.060 | About 67% |
| One build, 2 vCPU ARM64 | $0.020 | $0.050 | 60% |
| 1,000 builds a month, 2 vCPU x64 | $20 | $60 | About 67% |
Faster builds also cut the cost that never shows up on the invoice: engineers waiting for a green check before they can merge.
Where per-second billing pays off
Lint, type checks, unit test shards and deploy steps often finish in well under a minute. On GitHub-hosted runners each one still costs a full minute. On CRACI you pay for the seconds it ran. The examples below compare jobs of the same length, before any speed-up.
| Capability | CRACI | GitHub-hosted | CRACI saves |
|---|---|---|---|
| 1,000 jobs of 30 seconds | $2.00 | $6.00 | About 67% |
| 1,000 jobs of 70 seconds | $4.67 | $12.00 | About 61% |
| 1,000 builds of 10 minutes | $40.00 | $60.00 | About 33% |
| 1,000 builds of 10 minutes, 32 vCPU x64 | $640 | $820 | About 22% |
The shorter the jobs, the bigger the saving from per-second billing. On long builds the saving comes from speed: about 67% on a 10-minute build, against about 33% from the price per minute alone.
How many GitHub Actions minutes do you use? Find your real numbers
Most teams cannot say how many build minutes their CI uses a month, and a guess is no basis for comparing providers. GitHub records the number in four places. Each shows something different, and each has a catch.
| Source | Where | What it shows | The catch |
|---|---|---|---|
| Billing usage page and usage report | Organization settings, Billing and licensing, Usage; filter to Actions, or request a usage report (CSV) by email | Spend and quantity per day, SKU (runner OS and size) and repository; the detailed report adds the workflow path | Owners and billing managers only. It shows spend: free usage (standard runners in public repositories, self-hosted runners, included usage) appears as a discount, so compare the gross and net amounts |
| Actions usage metrics | Organization Insights, Actions usage metrics; the form below opens the last 30 days | Minutes by workflow, job, repository, runner type and OS | Needs the "View organization Actions metrics" permission. GitHub states the metrics "do not apply minute multipliers", so they are not the bill |
| Billing usage REST API | GET /organizations/{org}/settings/billing/usage, with optional year, month and day | The summarized usage report, for scripts | Organization owners and billing managers, only on GitHub's enhanced billing platform; it takes a personal access token (classic), as fine-grained tokens are not supported; no per-workflow detail |
| Your workflow runs | Run and job history through the GitHub CLI (script below) | Start and end time of every job, which you round yourself | Only the repositories you query; run time, not dollars |
The billing pages show the bill; the metrics page and the run history show where the minutes go. To open your organization's Actions usage metrics for the last 30 days, enter its name:
Count billed minutes from your workflow runs
Without access to billing, count the minutes yourself. This script uses the GitHub CLI to list a repository's workflow runs from the last 30 days, fetches each run's jobs (reruns included), rounds every job up to the whole minute and adds them up by runner label:
# Billed GitHub Actions minutes per runner label, one repository, last 30 days.
# GitHub rounds each job up to the whole minute, so the script does too.
REPO=your-org/your-repo
SINCE=$(date -u -d '30 days ago' +%F) # macOS: date -u -v-30d +%F
gh api --paginate "repos/$REPO/actions/runs?created=>=$SINCE&per_page=100" \
--jq '.workflow_runs[].id' |
while read -r run; do
gh api --paginate "repos/$REPO/actions/runs/$run/jobs?filter=all&per_page=100" \
--jq '.jobs[] | select(.conclusion != "skipped" and .started_at and .completed_at)
| [(.labels | join(",")), ((.completed_at | fromdate) - (.started_at | fromdate))]
| @tsv'
done |
awk -F'\t' '{ jobs[$1]++; secs[$1] += $2; billed[$1] += int(($2 + 59) / 60) }
END { for (l in jobs) printf "%s\t%d jobs\t%d s run\t%d billed min\n", l, jobs[l], secs[l], billed[l] }' The rounding has to happen per job, as GitHub does it, not on the total: a workflow with ten 20-second jobs bills ten minutes, not four. The labels show where each job ran. Jobs on self-hosted or third-party runners, and jobs on standard runners in public repositories, use no paid GitHub minutes, so leave them out of the bill. The runs endpoint returns at most 1,000 runs for a date filter, so split a busy repository into shorter periods. GitHub's per-run timing endpoint used to report billable time, but GitHub says it is closing down, so the script reads job timestamps instead.
No access to billing at all? Ask an organization owner or billing manager for the usage report, use the Actions usage metrics page if you have the permission, or run the script on your three busiest repositories and scale up.
Teams we talk to who keep running out of included minutes sometimes move CI onto laptops, with a coding agent running the pipeline locally. That saves the minutes, but builds get slower, memory and swap run out, and nobody can reproduce or audit what was built. The fix is knowing the number, cutting waste (see nine ways to cut the bill) and moving the heavy Linux jobs to cheaper minutes.
The costs that do not show up per minute
- Reruns. A flaky test that fails one run in ten adds roughly 10% to the bill of the workflow it sits in, and every rerun job is rounded up again.
- Hung jobs. Without
timeout-minutes, a stuck job keeps running until GitHub's limit and is billed for all of it. - Waiting engineers. Slow pipelines cost developer time, which is usually worth far more than the minutes. Right-size runners for the jobs on the critical path, or run them on a faster runner.
- Self-hosted overhead. Self-hosted runners avoid the per-minute price but not the cost: machines sit idle between builds, and someone has to patch, scale and secure them. See managed vs self-hosted runners.
Nine ways to cut the bill
- Find the expensive jobs first. Use the usage report, the metrics page or the script above to see which workflows, runners and repositories use the most minutes, and start there.
- Cancel superseded runs. A
concurrencygroup withcancel-in-progressstops the run for an older commit when a newer one arrives on the same branch. - Skip work that does not apply.
pathsfilters keep a documentation change from running the full test suite. - Cache dependencies. Restoring packages from a cache is faster than downloading them on every run. See how GitHub Actions caching works.
- Set timeouts. A
timeout-minutesvalue on each job stops a hung job from burning minutes until the default limit. - Merge tiny jobs. Under whole-minute rounding, three 10-second jobs cost three minutes; one job that does all three costs one.
- Right-size runners. A larger runner costs more per minute but can cost less per build when it finishes much faster. Measure both.
- Use ARM64 where it is cheaper. On GitHub, a 2-core ARM64 runner is listed below the x64 price.
- Move to a faster, cheaper runner. CRACI runs builds about twice as fast, lists a lower price on standard Linux runners and bills per second, with no change to the workflow beyond
runs-on.
Switching to CRACI
CRACI replaces the runner, not GitHub Actions. Install the CRACI GitHub App, change runs-on to craci, and the job runs on CRACI while the workflow, its actions and its logs stay in GitHub. Sizes run from 1 to 32 vCPU, set with the cracicorp/setup action. Move one workflow first and compare the build time and the bill. For caches, OIDC and fallback, see how to switch runner providers.
CRACI charges only for build minutes: $0.002 per vCPU-minute ($0.004 for a default 2 vCPU runner), metered per second, with no monthly fee and no per-SBOM charge. Startups can get at least 100,000 free build minutes through the startup program. See pricing.
The same runner also records an SBOM of what each job fetched, enforces an egress policy and records provenance data, so the faster, cheaper build comes with a record of what went into it. See CRACI vs GitHub-hosted runners.
GitHub Actions pricing: frequently asked questions
How much does GitHub Actions cost?
Every plan includes Actions usage each month as a dollar amount: $12 on GitHub Free, $18 on Pro and Team, and $300 on Enterprise Cloud, which buys 2,000, 3,000 and 50,000 minutes on a standard 2-core Linux runner. Beyond that, a standard 2-core Linux x64 runner costs $0.006 per minute as of November 11, 2026, and larger runners cost more.
How much does GitHub Actions cost per minute?
As of November 11, 2026, a standard 2-core Linux runner costs $0.006 per minute on x64 and $0.005 on ARM64. Windows costs $0.010 for 2 cores, and macOS starts at $0.062. Larger runners scale with size, up to $0.252 per minute for 96-core Linux x64. GitHub rounds each job up to the whole minute.
Is CRACI cheaper than GitHub-hosted runners?
Yes, for standard Linux runners. CRACI lists $0.004 per minute for 2 vCPU ($0.002 per vCPU-minute), about 33% below GitHub's $0.006 for 2-core x64, bills per second, and runs builds about twice as fast, so each build uses fewer minutes. A build that takes 10 minutes on a GitHub-hosted 2-core runner costs about 67% less on CRACI, or a third of the price.
Why is CRACI faster than GitHub-hosted runners?
Three things together: faster hardware, shorter queue times before a job starts, and caching. CRACI runs builds about twice as fast as GitHub-hosted runners.
Does GitHub round up Actions minutes?
Yes. GitHub rounds each job up to the whole minute, so a job that runs for 10 seconds is billed as a full minute. Pipelines with many short jobs pay the most for rounding.
Does included usage cover larger runners?
On GitHub Team and Enterprise Cloud, yes: larger runners draw on the same included usage as standard runners, at their own per-minute rate. Larger runners are not available on Free or Pro, and they are not free for public repositories.
Is GitHub Actions free for public repositories?
Yes, on standard runners. GitHub states that standard GitHub-hosted runners are free in public repositories.
Are self-hosted runners free?
GitHub does not charge per minute for self-hosted runners, but you pay for the machines, including idle ones, and you are responsible for their operating system, software and security. GitHub warns that self-hosted runners should almost never be used for public repositories.
How do I move a job to CRACI?
Install the CRACI GitHub App and change runs-on to craci in the job. The workflow, its actions and its logs stay in GitHub. Choose a runner size from 1 to 32 vCPU with the cracicorp/setup action.
How many GitHub Actions minutes do I need?
Count them rather than guess. Your billing usage report shows the minutes used per runner. Without billing access, list a repository's workflow runs and jobs with the GitHub CLI and round every job up to the whole minute, as GitHub does. Short jobs inflate the count: ten 20-second jobs bill ten minutes. Then put the figure into the calculator on this page.
How do I see my GitHub Actions usage?
In four places. The Usage page under Billing and licensing in your organization settings, with a downloadable usage report, for owners and billing managers. Actions usage metrics in organization Insights, by workflow, job, repository and runner, which do not apply minute multipliers. The billing usage REST API, for scripts. And your workflow run history through the GitHub CLI, which gives each job's run time to round up yourself.
What happens when I use up my included minutes?
Without a valid payment method on file, GitHub blocks Actions usage once the included usage is consumed. With a payment method, further usage is billed to it, and a budget can stop Actions usage at a limit you set. Larger runners always need a valid payment method. GitHub emails you when included usage reaches 90% and 100%.
Does GitHub charge for minutes on third-party runners?
Not per minute. Third-party runner providers connect to GitHub as self-hosted runners, and GitHub states that Actions usage on self-hosted runners is free. You still pay GitHub for your plan and for storage beyond what it includes, and you pay the runner provider for its minutes.
Cut your GitHub Actions bill
Change runs-on on one workflow, run it on CRACI, and compare the build time and the bill line by line.
Book a demo