GitHub Actions Pricing Changes 2026
2026 brought one pricing change that stuck and one that did not: significant hosted-runner rate cuts on 1 January, and a self-hosted platform charge that GitHub announced in December 2025 and shelved within 48 hours after community backlash. Here is what actually changed, what was reversed, and how it affects your CI/CD cost structure.
1 January 2026: Hosted runner rate cuts
On 1 January 2026, GitHub reduced the per-minute rate on every hosted runner type, by up to 39% depending on the machine. The free tier (2,000 minutes/month Free plan, 3,000 minutes Team plan) was unchanged. The four most-used rates, before and after:
| Runner type | Pre-Jan 2026 | Post-Jan 2026 | Change |
|---|---|---|---|
| Linux 2-core (x64) | $0.006 | -25% | |
| Windows 2-core (x64) | $0.010 | -38% | |
| macOS 3/4-core (M1/Intel) | $0.062 | -23% | |
| Linux 64-core (arm64) | $0.098 | -39% |
Current published rates for larger runners (per the same GitHub pricing reference, June 2026):
The self-hosted platform charge that never happened
On 16 December 2025, GitHub announced a $0.002/min Actions cloud platform charge, billed from 1 March 2026 on all workflows in private repositories, including jobs running on self-hosted runners. The stated rationale: the Actions control plane (scheduling, log streaming, secret management, audit trails) costs GitHub money regardless of where compute runs. GitHub said 96% of customers would see no change to their bill.
The developer community disagreed, loudly. Charging a per-minute meter on hardware customers already own and operate read as a tax on the most cost-conscious users. Within 48 hours, GitHub reversed course: "We're postponing the announced billing change for self-hosted GitHub Actions to take time to re-evaluate our approach." The 1 March 2026 date came and went with no charge.
What stands today (June 2026)
- Self-hosted runner usage is free, on public and private repos
- GitHub's billing docs state Actions usage is free for self-hosted runners
- The January hosted-runner price cuts remain in force
- Public repo workflows remain free on hosted runners too
What to watch
- Postponed is not cancelled: GitHub is "re-evaluating"
- No replacement model or timeline announced as of June 2026
- GitHub committed to consulting developers before another attempt
- Long-term self-hosted ROI plans should note the model could change
Self-hosted break-even (no platform fee)
With the platform charge shelved, self-hosting Linux saves you the full $0.006/min versus hosted. The January cuts did move the goalposts: hosted got cheaper, so break-evens are higher than in 2025. Break-even for common runner setups:
| Self-hosted server | Monthly cost | Saving per minute (vs hosted Linux) | Break-even (min/mo) |
|---|---|---|---|
| Hetzner CCX13 ($14/mo) | $14 | $0.006 | 2,333 |
| DigitalOcean Premium AMD ($24/mo) | $24 | $0.006 | 4,000 |
| AWS t3.medium ($30/mo) | $30 | $0.006 | 5,000 |
| AWS t3.large ($60/mo) | $60 | $0.006 | 10,000 |
| AWS c6i.2xlarge ($250/mo) | $250 | $0.006 | 41,667 |
For interactive scenario modelling with your specific build pattern, use the CICD Calculator.
What this means for your CI/CD strategy
Sub-2,000 minutes/month teams: nothing changes. You stay in the free tier across Free and Team plans.
2,000-15,000 minutes/month teams: hosted is more cost-attractive than before the cuts. A typical $30/mo VPS now breaks even at ~5,000 minutes (it was 3,750 at 2025 rates), so the marginal case for self-hosting weakened slightly. Most teams in this band should stay hosted.
15,000-50,000 minutes/month teams: the case for hybrid (hosted for long-tail jobs + self-hosted for hot paths) remains compelling, and there is no platform fee eroding it.
50,000+ minutes/month teams: self-hosted ROI is strong, but the operational cost of running runners (admin time, capacity planning, security patching) becomes the dominant variable, not the per-minute rate.
macOS builders: the macOS cut to $0.062/min (-23%) helps, but Mac CI remains roughly 10x Linux. A 15-minute iOS build costs $0.93 hosted. High-volume Mac teams still come out ahead on self-hosted Mac mini hardware, which pays for itself within months at a few thousand macOS minutes per month.
Frequently asked questions
What changed in GitHub Actions pricing in January 2026?
On 1 January 2026, GitHub reduced hosted runner per-minute rates by up to 39%. Linux 2-core dropped from $0.008 to $0.006/min (-25%). Windows 2-core dropped from $0.016 to $0.010/min (-38%). macOS 3/4-core dropped from $0.080 to $0.062/min (-23%). The deepest cut was on arm64 larger runners: Linux 64-core arm64 fell from $0.160 to $0.098/min (-39%). The free tier (2,000 minutes/month on Free, 3,000 on Team) was unchanged.
Did the March 2026 self-hosted runner platform fee happen?
No. On 16 December 2025 GitHub announced a $0.002/min Actions cloud platform charge that would have applied to all workflows on private repositories, including self-hosted runners, from 1 March 2026. Community reaction was immediate and overwhelmingly negative, and within 48 hours GitHub postponed the change, stating it was taking time to re-evaluate its approach. The 1 March 2026 date came and went with no charge. As of June 2026, self-hosted runner usage on GitHub Actions remains free and GitHub's billing documentation confirms this.
Why did GitHub propose the self-hosted platform charge?
GitHub framed the proposed fee as paying for the Actions control plane (job scheduling, log streaming, secret management, audit trails) that GitHub provides regardless of where compute happens. GitHub claimed 96% of customers would have seen no change to their bill. The developer community saw it differently: a per-minute charge on compute you already own and operate. The backlash was strong enough that GitHub shelved the plan within two days of announcing it.
Could GitHub reintroduce a self-hosted runner charge later?
Possibly. GitHub said it is postponing the change 'to re-evaluate our approach', not cancelling the idea outright, and committed to consulting developers before any future monetisation attempt. As of June 2026 there is no announced timeline or replacement model. Teams doing self-hosted ROI analysis today should use the current reality (no fee) but be aware the model could change with notice.
What is the self-hosted break-even after the January 2026 cuts?
With no platform fee, the formula is simple: server monthly cost / $0.006 per hosted Linux minute. A $30/month t3.medium breaks even at roughly 5,000 minutes/month. A $5/month Hetzner VPS breaks even near 850 minutes. Note the January cuts made hosted runners cheaper, which pushed break-evens higher than they were in 2025 (when hosted Linux cost $0.008/min and a $30 server broke even at 3,750 minutes).
Are larger and GPU GitHub-hosted runners still cost-effective?
GitHub's published per-minute rates after the January 2026 cuts: Linux x64 4-core $0.012, 8-core $0.022, 16-core $0.042, 32-core $0.082, 64-core $0.162. arm64 equivalents run cheaper (Linux 64-core arm64 $0.098). GPU Linux 4-core is $0.052/min. For jobs that scale with compute (large test suites, ML training), larger runners can be cost-effective because total wall-clock minutes drop. Self-hosted comparisons should use equivalent EC2/Azure/GCP instance pricing.
How do the 2026 changes affect cost optimisation strategy?
Two practical implications. First, hosted runners are more attractive than before for sub-10,000-minute teams because per-minute rates dropped across the board. Second, self-hosting still pays at volume and carries no platform fee, so the 2025-era self-hosted playbook still works; the break-even just moved up because hosted got cheaper. macOS remains the big-ticket item at $0.062/min: a 15-minute iOS build costs $0.93, so high-volume Mac CI still favours self-hosted Mac mini hardware.
Related guides
Want to model your specific build pattern interactively? Use the CICD Calculator.