After GitHub Actions' 2026 price drop, when do self-hosted runners still make sense?
Decide whether to keep private-repo CI on GitHub-hosted runners or move back to self-hosted now that hosted rates dropped on January 1, 2026 and self-hosted runs add a $0.002/min cloud platform fee from March 1, 2026.
Blockers
- GitHub-hosted runner rates were reduced effective January 1, 2026.
- A $0.002/min Actions cloud platform fee applies to self-hosted runner usage in private repositories beginning March 1, 2026.
Who this is for
- cost-sensitive
- small-team
- enterprise
Candidates
Keep most private-repo CI on standard GitHub-hosted runners
As of 2026-03-19, this is the default managed GitHub Actions option for Linux, Windows, and macOS. GitHub-hosted rates were reduced effective January 1, 2026, with current baseline prices documented at $0.006/min for Linux 2-core x64, $0.005/min for Linux 2-core arm64, $0.010/min for Windows 2-core x64 or arm64, and $0.062/min for standard macOS. GitHub states the new $0.002/min Actions cloud platform charge is already included in these hosted rates. Private-repo usage can still consume included monthly minutes on plan quotas, such as 3,000 minutes on GitHub Team and 50,000 on GitHub Enterprise Cloud.
When to choose
Best for low-ops plus cost-sensitive teams whose main reason for self-hosting was avoiding hosted per-minute prices. Choose this when your workflows fit GitHub-hosted runner shapes and you do not need persistent access to private network resources or custom machine images that only exist in your own environment.
Tradeoffs
You get lower operational burden, predictable official images, and no separate infrastructure to patch or autoscale. You give up some machine customization and may still pay more than your own raw compute for long-running Linux-heavy jobs after included minutes are exhausted.
Cautions
As of 2026-03-19, larger runners are always billed separately and cannot use included minutes. If your current self-hosted setup depends on private network access, custom images, or machine specs with no suitable GitHub-hosted equivalent, GitHub's migration guide says to inventory those blockers first and exclude those workflows from migration.
Keep or move private-repo CI to self-hosted runners only when environment control is the real requirement
As of 2026-03-19, self-hosted runners for private repositories are no longer purely 'bring your own compute and GitHub orchestration is free' for current pricing decisions. GitHub announced that the new $0.002/min Actions cloud platform charge applies to self-hosted runner usage in private repositories beginning March 1, 2026, and that billable self-hosted usage can consume the same included plan quota. Standard runner usage in public repositories remains free, and GitHub Enterprise Server is not affected by this pricing change. This means self-hosting now mainly wins on environment control, private connectivity, or hardware specialization, not on avoiding GitHub Actions metering entirely.
When to choose
Best for compliance, private-network, custom-hardware, or bespoke image requirements that GitHub-hosted runners cannot satisfy cleanly. Choose this when a workflow must stay close to internal systems or needs runner shapes, labels, or preinstalled toolchains that would be awkward to reproduce on managed runners.
Tradeoffs
You retain full control over hardware, networking, and software images. You now pay both your own infrastructure cost and GitHub's $0.002/min platform fee for affected private-repo runs, so the pure cost case is weaker than it was before March 1, 2026.
Cautions
As of 2026-03-19, this pricing change has already occurred. GitHub's migration guidance also makes clear that some workflows should remain self-hosted, especially those that access private APIs, databases, internal registries, or lack a suitable GitHub-hosted runner match; do not assume a cost-only comparison is enough.
Adopt a hybrid policy: GitHub-hosted by default, self-hosted only for exception workloads
As of 2026-03-19, the pricing structure now pushes teams toward a split model instead of an all-or-nothing runner strategy. GitHub-hosted standard runners got cheaper on January 1, 2026, while self-hosted private-repo runs picked up the $0.002/min platform fee on March 1, 2026. GitHub's own migration guide explicitly supports a mixed fleet and recommends identifying workflows that target self-hosted runners, why they do so, and which ones must remain because of private networking, custom dependencies, or missing hosted equivalents. This makes hybrid the safest default for teams with a few hard blockers but many ordinary CI jobs.
When to choose
Best for monorepos or enterprise estates with mixed workload shapes and a need to lower ops overhead without breaking specialized pipelines. Use GitHub-hosted for commodity build and test jobs, and reserve self-hosted runners for workflows with clear environmental or compliance blockers.
Tradeoffs
This captures much of the hosted price reduction while preserving self-hosted flexibility where it matters. The downside is policy complexity, because you must manage runner selection, labels, quotas, and governance across two execution models.
Cautions
Do not migrate blindly by repository alone. GitHub recommends inventorying labels, runner groups, custom images, private network dependencies, and workflows with no suitable GitHub-hosted runner before changing `runs-on` targets.
Try with your AI agent
$ npm install -g pocketlantern $ pocketlantern init # Restart Claude Code, Cursor, or your MCP client, then ask: # "After GitHub Actions' 2026 price drop, when do self-hosted runners still make sense?"