GitHub Actions Postpones Self-Hosted Runner Fees After Backlash

GitHub announced on December 16, 2025, that it would introduce a $0.002 per minute cloud platform charge for self-hosted runner usage in private repositories starting March 1, 2026. The announcement triggered immediate and intense backlash from the developer community, leading to one of the fastest policy reversals in GitHub's history.

Community Revolt

The proposed charge would have applied to organizations using their own hardware to run GitHub Actions workflows. Developers argued that charging for infrastructure they already own and maintain was unreasonable, especially since the hardware, electricity, and maintenance costs are borne entirely by the users themselves. Community discussions on GitHub quickly amassed thousands of comments, with developers questioning the rationale for a platform fee on self-hosted compute.

Rapid Reversal

Just 24 hours after the announcement, GitHub indefinitely postponed the billing change, acknowledging they "missed the mark with this change by not including more of you in our planning." The company stated it would take more time to meet and listen closely to developers, customers, and partners before proceeding with any changes to self-hosted runner pricing.

What Proceeded and What's Next

While the self-hosted runner charge was shelved, GitHub proceeded with reducing hosted-runner prices by up to 39% on January 1, 2026. However, observers note that a postponement is not a cancellation—the economics that drove the original proposal haven't disappeared. Organizations relying heavily on self-hosted runners should monitor GitHub's future pricing announcements and consider evaluating alternative CI/CD platforms as a contingency measure.