GitHub Actions is free in public repositories on GitHub’s standard runners. In private and internal repositories, jobs on GitHub’s runners are billed by the minute once a monthly allowance, which depends on your plan, runs out. Jobs on self-hosted runners are not billed today. Prices below are from GitHub’s documentation as of November 2026.

Price per minute

RunnerPrice per minute
Linux, 1 core$0.002
Linux, 2 cores (x64)$0.006
Linux, 2 cores (arm64)$0.005
Windows, 2 cores$0.010
macOS, 3 or 4 cores$0.062

A macOS minute costs about ten times a 2-core Linux one. Larger runners are priced by size and architecture, and unlike standard runners they are billed in public repositories too.

What each plan includes

Each plan includes a monthly amount of compute, in dollars rather than minutes, shared with larger runners where you use them. On the standard 2-core Linux runner that works out to:

PlanIncluded each monthLinux minutes at $0.006
Free$122,000
Pro$183,000
Team$183,000
Enterprise Cloud$30050,000

The same allowance covers Windows and macOS at their own rates, so $18 buys about 290 macOS minutes.

How minutes are counted

GitHub rounds each job up to the next whole minute. A workflow with three jobs that each take 40 seconds is billed as three minutes, not two. Jobs that run in parallel are each billed for their own time. Splitting a suite across more jobs can finish sooner, but each job repeats its setup and is rounded up on its own, so it usually costs more.

A worked example: a team pushes 20 times a working day, and each push runs three parallel Linux jobs of 6 minutes. That is 18 billed minutes a push, 360 a day, and about 7,920 over 22 working days. At $0.006 a minute that is $47.52, leaving $29.52 to pay if the Team plan’s $18 is not used elsewhere.

Storage

Artifacts share an allowance with GitHub Packages: 500 MB on Free, 1 GB on Pro, 2 GB on Team and 50 GB on Enterprise Cloud. Beyond it, storage is $0.25 per GB a month, counted by the hour. The Actions cache gets 10 GB per repository on every plan. If you raise a repository’s cache limit above that, the extra is $0.07 per GB a month.

Self-hosted runners

A self-hosted runner is a machine you register with GitHub to run jobs instead of GitHub’s own. GitHub’s documentation lists self-hosted runner usage as free. On December 17, 2025 GitHub postponed a change that would have started billing it. Check the current terms before you plan around it.

What you pay instead is the server and the time to look after it, which comes down to two jobs:

Ephemeral runners help with the second: each accepts one job and then unregisters. The machine itself is not wiped, so something has to start a fresh machine or container for each job and remove it afterwards.

Running them on your own server

When a queued job carries every label a FlatRun subscription names, FlatRun registers a single-use runner in a fresh Firecracker microVM or Docker container on your server, and the runner exits when the job ends. The setup guide covers the GitHub App and the labels.

Sources: GitHub Actions billing, Actions runner pricing.