Skip to content

Home / Cost calculator

GitHub Actions cost for 5,000 minutes a month

5,000 standard Linux minutes a month cost $12.00 on GitHub-hosted runners and $8.00 on runners.io, which is $4.00 less, before either side's larger sizes, other platforms or anything else on the bill.

This page prices one month of 5,000 minutes on the standard 2 vCPU Linux runner, line by line, with each side’s included amount taken off first. Two things are the same on both sides: a minute is a minute of the same machine, and a month is the minutes you put in. What differs is the rate and the included amount, and the table says exactly how much each is worth at this size.

What do 5,000 minutes cost, line by line?

LineGitHub-hostedrunners.io
Minutes in the month5,0005,000
Included, taken off first3,000 minutes3,000 run-minutes
Minutes billed2,0002,000
Rate for each billed minute$0.006$0.004
The month$12.00$8.00

Before any included amount, the month is $30.00 on GitHub-hosted runners at $0.006 a minute and $20.00 on ours at $0.004. The included amount is then taken off each, and what is left is billed. The arithmetic prices the minutes you give it. GitHub rounds each job up to a whole minute before they are counted, so a month of short jobs bills more minutes than the stopwatch says, and the section on rounding below prices that.

What does the GitHub bill look like on each plan?

GitHub planIncluded compute a monthBill for 5,000 minutes
GitHub Free$12.00$18.00
GitHub Pro or Team$18.00$12.00
GitHub Enterprise Cloud$300.00$0.00

GitHub’s included compute is a dollar amount, set by plan, and it is taken off before anything is billed. The headline figures above use the GitHub Pro or Team row, because the cost calculator does, and so does the first table. A different plan changes the GitHub column and nothing on ours. Free for organizations has the same included amount as Free. The pricing post explains the plans and the rounding, and the dated log of GitHub’s pricing changes says when the rate and the allowances last moved.

What is the allowance doing at 5,000 minutes?

At this size the included amount covers most of the month on our side and on GitHub Pro or Team, and less of it on GitHub Free, so the difference in dollars is small and the question that matters is how much of the allowance you are already using. GitHub's included compute is a dollar amount that resets with the billing cycle, which is why the table below sets each plan against the month and not one figure.

A month this size is also where the habits that cost nothing yet are cheapest to fix: a workflow that runs on every push and on every pull request twice, or a job that never cancels a superseded run, spends minutes you do not notice until the allowance runs out. The post on running less lists those habits, and the calculator will price the month without them.

What is 5,000 minutes in builds, and in a working day?

5,000 minutes is 500 builds of 10 minutes or 250 builds of 20. Spread over 22 working days it is about 227 minutes a day. Spread evenly over a 30-day month it keeps 0.1 runners busy at any moment on average. Those are the figures to check your own month against: if your builds are shorter or your month is lumpier, the minutes come out the same and the number of jobs does not, and the number of jobs is what a plan’s concurrency limit counts. On the standard plan ours is 8 jobs at once, set out on the runner limits page with how long a job may run, and GitHub’s limits for every plan are in the limits post.

What does rounding each job up add at 5,000 minutes?

Each job is rounded up to a whole minute, so every point of the month that is rounding costs one hundredth of the minutes. At this size one per cent is 50 minutes: $0.30 on GitHub-hosted runners and $0.20 on ours. A month of jobs that are all a few seconds over a whole minute can carry far more than one per cent, which is why the number of jobs is worth counting beside the number of minutes. The post on running less lists the changes that remove jobs and minutes at the source.

How is this worked out?

Both sides price the standard 2 vCPU Linux x64 minute, the one machine whose GitHub-hosted rate we hold as a sourced figure; GitHub’s larger runners are not a straight multiple of it, so they are not quoted here. The GitHub rate and included amounts are from GitHub’s own pages, read on 15 November 2026, and listed below. Our rate and included minutes are on the pricing page, and the cost calculator takes your own month, other sizes and other platforms, and prices it the same way. This page is ours and sells our runners; it says so because a cost page that did not would be hard to tell from an independent one.

Price your own month, or read the same page for another size: 10,000 minutes, 25,000 minutes, 50,000 minutes, or 100,000 minutes.

Sources

Run your next build here

Connect GitHub

Card required. You pay only for the minutes your jobs run.

.github/workflows/ci.yml
jobs: test:- runs-on: ubuntu-latest+ runs-on: runnersio-4vcpu-ubuntu-2404 steps: - uses: actions/checkout@v4 - run: make test+ build:+ runs-on: runnersio-32vcpu-ubuntu-2404