# GitHub Actions pricing

Last confirmed on the vendor's page: 2026-10-02. Source: https://github.com/features/actions. Confidence: medium.

| Plan | Per month | Unit | Billing | On the vendor's page |
| --- | --- | --- | --- | --- |
| Free | Free |  |  |  |
| Free (private) | Free |  |  |  |

## Hidden costs and limits

- macOS runner minutes cost 10x more than Linux ($0.062/min vs $0.006/min).
- Windows runners cost $0.010/minute, 67% more than Linux. Teams with .NET or Windows-native builds pay significantly more than the headline Linux rates suggest
- Artifact and cache storage is shared with GitHub Packages. Heavy Docker image publishing or large build artifacts eat into your storage quota, triggering $0.07/GB/month overage charges
- Included minutes are shared across the entire organization, not per-user. A single developer with a misconfigured workflow can burn through the team's entire monthly allocation in hours
- Larger hosted runners (4-core, 8-core, 16-core+) are always billed, even for public repositories. Only standard 2-core runners are free for public repos
- Self-hosted runners are free to use in Actions, but you bear the infrastructure cost: EC2/VM hosting, maintenance, security patching, and scaling. GitHub does not manage self-hosted runners
- Concurrent job limits exist: Free gets 20 concurrent jobs, Team/Pro get 60, and Enterprise gets 180+. CPU-heavy monorepos can hit these limits and queue builds, slowing deployment velocity
- Cache storage has a 10GB limit per repository regardless of plan. Large monorepo builds that exceed this limit see cache eviction and slower builds

## Cite

Toolradar, verified 2026-10-02, https://toolradar.com/tools/github-actions/pricing

Full page: https://toolradar.com/tools/github-actions/pricing. JSON: https://toolradar.com/tools/github-actions/pricing.json. Report an error: https://toolradar.com/openapi.json