Microsoft-owned code hosting platform GitHub has announced a new pricing change for its Actions service. Previously, GitHub Actions offered a free control plane: as long as workflows ran on servers not hosted by GitHub’s own runners, users incurred no additional charges.
Many developers took advantage of this model by running workflows on their own servers or through their own AWS accounts, paying only for the underlying infrastructure without owing anything extra to GitHub Actions. This made the service particularly attractive for automation tasks.
Under the revised pricing structure, GitHub Actions will now levy a platform fee of USD 0.002 per minute. This fee applies regardless of whether developers use GitHub-hosted runners or their own infrastructure, and for some users it will inevitably raise operating costs. While the change may appear abrupt, its rationale is not hard to discern: GitHub Actions has been grappling with user churn and revenue pressures. CI workloads have grown larger and more complex, making GitHub-hosted runners increasingly expensive and slower to operate—factors that, in turn, have driven more users away.
This dynamic explains why many developers have migrated to third-party runner providers such as Blacksmith. From GitHub’s perspective, continuing to offer the service in its previous form meant absorbing server and maintenance costs without generating meaningful revenue.
Introducing usage-based fees offers GitHub several advantages: it creates a direct revenue stream, curbs overall consumption of GitHub Actions, allows the company to focus resources on delivering higher-quality service to paying customers, and opens the door to further monetization initiatives in the future.
It is worth noting that GitHub Actions will remain free for public repositories, and pricing for enterprise servers is unaffected by the change. GitHub maintains that the adjustment will not significantly impact most users. At the same time, the company has reduced runner prices in an effort to entice developers back from third-party or self-hosted solutions to GitHub’s own infrastructure.
Related Posts:
- GitLab Patches High Runner Hijacking Flaw (CVE-2025-11702) and Multiple DoS Vulnerabilities
- CVE-2024-31461: Critical Vulnerability Found in Widely-Used Plane Project Management Software
- Plane Project Management Tool Patches Critical SSRF Flaw – CVE-2024-47830 (CVSS 9.3)
- Is Apple Violating EU Law? Regulators Investigate New App Store Fees