Hacker ApprovedDepartments

GitHub Actions self-hosted runners

Ranked 3 of 9 ci runners by recommenders

Recommended for running CI jobs on your own machines, often much faster than GitHub's cloud runners and easy to set up. Critics point to hangs, CPU-hungry sleep loops, and weak support outside Linux.

Recommended for running CI jobs on your own machines, often much faster than GitHub's cloud runners and easy to set up. Critics point to hangs, CPU-hungry sleep loops, and weak support outside Linux.

34 people gave an opinion

recommend it
9
criticize it
25
approval share
26%
Each figure is one person. RecommendsCriticizes

Recommended in 6 of 13 months

  1. November 2025: not recommended
  2. December 2025: recommended
  3. January 2026: recommended
  4. February 2026: recommended
  5. March 2026: not recommended
  6. April 2026: not recommended
  7. May 2026: not recommended
  8. June 2026: not recommended
  9. July 2026: recommended
  10. August 2026: recommended
  11. September 2026: recommended
  12. October 2026: not recommended
  13. November 2026: not recommended (month in progress)

Why it doesn’t carry the badge

  • 9 people recommend itNeeds 10 or more, not met.
  • 0.3 recommenders for every criticNeeds 2 to 1 or better, not met.
  • Recommended in 6 of 13 monthsNeeds 4 or more, met.

The same three rules apply to every product, and the badge can’t be bought. How the badge works

What people say about it

The reasons people give, with the number of comments that give each one. Open a reason to read what they said.

Why people recommend it

Each mark is one comment

  • Faster than GitHub cloud runners

    “the builds are over 10x faster than relying on their cloud runners”

    Comment from 16 Dec 2025 in “Pricing Changes for GitHub Actions”

    “tests will run faster than on any hosted platform”

    Comment from 22 Sep 2026 in “AI coding has made CI a bottleneck, so we reworked ours to keep up”

    “It's a much faster way to iterate.”

    Comment from 17 Jan 2026 in “I Hate GitHub Actions with Passion”
  • Easy to set up

    “Github's self-hosted runners are actually surprisingly easy to set up and use”

    Comment from 6 Aug 2026 in “GitHub Is Experiencing Difficulties”

    “self hosted github runners to skip the setup”

    Comment from 23 Sep 2026 in “AI coding has made CI a bottleneck, so we reworked ours to keep up”

What people warn about

Each mark is one comment

  • Hangs and CPU-burning sleep loops

    “they are still using a poor man's sleep that uses up a core in the CPU instead of just using sleep, but progress!”

    Comment from 11 Dec 2025 in “Days since last GitHub incident”

    “Gh actions runners had a dubious implementation of sleep that would cause runners to hang on 100% usage for weeks/months.”

    Comment from 10 Jan 2026 in “AI is a business model stress test”

    “didn't they have a bug in the action runners that would basically cycle the CPU infinitely”

    Comment from 18 Dec 2025 in “GitHub postponing the announced billing change for self-hosted GitHub Actions”
  • Proposed fees for self-hosted use

    “Think if some company had a $15K/month bill in self-runners, they'll now also get a $15k/month additional bill from GitHub.”

    Comment from 18 Dec 2025 in “GitHub postponing the announced billing change for self-hosted GitHub Actions”

    “Rather than wholesaling charging they should have the self hosted runners implement hooks for that as well.”

    Comment from 18 Dec 2025 in “GitHub cancels Actions price change for self-hosted runners”

    “Charging for self-hosted runners is like a corkage fee but you still need to open the bottle yourself.”

    Comment from 23 Mar 2026 in “GitHub appears to be struggling with measly three nines availability”
  • Weak support outside Linux

    “The GitHub Actions runner does not work on FreeBSD, NetBSD, OpenBSD, and illumos, all of which are operating systems we either have existing support for, or intend to start supporting properly soon.”

    Comment from 27 Nov 2025 in “Migrating the main Zig repository from GitHub to Codeberg”

    “Maintaining Windows and macOS self hosted GH (or GL) runners is a hassle I really don't want to deal with anymore”

    Comment from 12 Oct 2026 in “Incident with Actions, Pull Requests and Issues”

    “the ones for macOS and Windows seemingly did something that made them a hell lot slower than even running VMs”

    Comment from 29 Apr 2026 in “HashiCorp co-founder says GitHub 'no longer a place for serious work'”
  • Heavy manual setup, no cleanup

    “you need 1 runner registration per concurrent job. And each runner needs its own user.”

    Comment from 16 Dec 2025 in “Pricing Changes for GitHub Actions”

    “it literally just runs commands on the host and does not handle provisioning/cleanup”

    Comment from 14 Jan 2026 in “I Hate GitHub Actions with Passion”

    “The config directory for each runner is normally based on its install path (insane)”

    Comment from 17 Dec 2025 in “Pricing Changes for GitHub Actions”

Other ci runners people recommend

The four most recommended other ci runners, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.

GitHub Actions self-hosted runners compared with 4 alternatives
ProductRecommendCriticizeApprovalMonthsOwnedBadge
Blacksmith runners222151%8——
WarpBuild12286%8—Approved
GitHub Actions self-hosted runnersThis page92526%6——
RunsOn8373%8——
Namespace80100%5——
See all 9 ci runners, ranked

What people said

35 of the 37 comments that mention it, newest first. Each links to the original comment.

“even those go down for these kinds of outages”

CriticizesComment from 19 Oct 2026 in “Degraded availability for GitHub Actions, GitHub Pages and Webhooks”

“Maintaining Windows and macOS self hosted GH (or GL) runners is a hassle I really don't want to deal with anymore”

CriticizesComment from 12 Oct 2026 in “Incident with Actions, Pull Requests and Issues”

“self hosted github runners to skip the setup”

RecommendsComment from 23 Sep 2026 in “AI coding has made CI a bottleneck, so we reworked ours to keep up”

“tests will run faster than on any hosted platform”

RecommendsComment from 22 Sep 2026 in “AI coding has made CI a bottleneck, so we reworked ours to keep up”

“all the limitations and quirks that came with it”

CriticizesComment from 19 Sep 2026 in “Btrfs/ZFS/bcachefs under workloads classic benchmarks skip”

“GH runner based benchmark is far from perfect due to noisy neighbours etc.”

CriticizesComment from 19 Sep 2026 in “Btrfs/ZFS/bcachefs under workloads classic benchmarks skip”

“Going to be GitHub self hosted runners all over again”

CriticizesComment from 11 Sep 2026 in “OpenAI Agents API”

“they also don't work because either they aren't started by GitHub or can't download the code”

CriticizesComment from 17 Aug 2026 in “Incident with Github.com”

“Github's self-hosted runners are actually surprisingly easy to set up and use”

RecommendsComment from 6 Aug 2026 in “GitHub Is Experiencing Difficulties”

“Oh that is pretty gross, thanks for sharing.”

CriticizesComment from 6 Aug 2026 in “GitHub Actions Is Down”

“It took literally 18 months for them to merge a bugfix that is trivially obvious to see is correct.”

CriticizesComment from 30 Apr 2026 in “Ghostty is leaving GitHub”

“the ones for macOS and Windows seemingly did something that made them a hell lot slower than even running VMs”

CriticizesComment from 29 Apr 2026 in “HashiCorp co-founder says GitHub 'no longer a place for serious work'”

“That's going to be a pain of a migration.”

CriticizesComment from 31 Mar 2026 in “GitHub backs down, kills Copilot pull-request ads after backlash”

“the docker image for GH Actions is made by "myoung34"”

CriticizesComment from 24 Mar 2026 in “GitHub appears to be struggling with measly three nines availability”

“Charging for self-hosted runners is like a corkage fee but you still need to open the bottle yourself.”

CriticizesComment from 23 Mar 2026 in “GitHub appears to be struggling with measly three nines availability”

“It seems to work for my tests at least.”

RecommendsComment from 13 Feb 2026 in “AWS Adds support for nested virtualization”

“It's a much faster way to iterate.”

RecommendsComment from 17 Jan 2026 in “I Hate GitHub Actions with Passion”

“it literally just runs commands on the host and does not handle provisioning/cleanup”

CriticizesComment from 14 Jan 2026 in “I Hate GitHub Actions with Passion”

“It has saved me hours of troubleshooting”

RecommendsComment from 12 Jan 2026 in “Launch a Debugging Terminal into GitHub Actions”

“Gh actions runners had a dubious implementation of sleep that would cause runners to hang on 100% usage for weeks/months.”

CriticizesComment from 10 Jan 2026 in “AI is a business model stress test”

“monetization of GH self-hosted runner (now suspended after backlash”

CriticizesComment from 29 Dec 2025 in “Self-hosting is being enshittified”

“Rather than wholesaling charging they should have the self hosted runners implement hooks for that as well.”

CriticizesComment from 18 Dec 2025 in “GitHub cancels Actions price change for self-hosted runners”

“it just doesn't make sense for the consumers”

CriticizesComment from 18 Dec 2025 in “GitHub postponing the announced billing change for self-hosted GitHub Actions”

“This pricing change would have cost more than the servers we're running on.”

CriticizesComment from 18 Dec 2025 in “GitHub postponing the announced billing change for self-hosted GitHub Actions”

“Think if some company had a $15K/month bill in self-runners, they'll now also get a $15k/month additional bill from GitHub.”

CriticizesComment from 18 Dec 2025 in “GitHub postponing the announced billing change for self-hosted GitHub Actions”

“didn't they have a bug in the action runners that would basically cycle the CPU infinitely”

CriticizesComment from 18 Dec 2025 in “GitHub postponing the announced billing change for self-hosted GitHub Actions”

“their runners are not as indispensable to developers as they thought”

CriticizesComment from 18 Dec 2025 in “GitHub postponing the announced billing change for self-hosted GitHub Actions”

“Per machine. Definitely more than one machine here.”

CriticizesComment from 17 Dec 2025 in “Pricing Changes for GitHub Actions”

“The config directory for each runner is normally based on its install path (insane)”

CriticizesComment from 17 Dec 2025 in “Pricing Changes for GitHub Actions”

“you need 1 runner registration per concurrent job. And each runner needs its own user.”

CriticizesComment from 16 Dec 2025 in “Pricing Changes for GitHub Actions”

“the builds are over 10x faster than relying on their cloud runners”

RecommendsComment from 16 Dec 2025 in “Pricing Changes for GitHub Actions”

“they are still using a poor man's sleep that uses up a core in the CPU instead of just using sleep, but progress!”

MixedComment from 11 Dec 2025 in “Days since last GitHub incident”

“upstream just cannot even be bothered to accept the relevant patches”

CriticizesComment from 27 Nov 2025 in “Migrating the main Zig repository from GitHub to Codeberg”

“The GitHub Actions runner does not work on FreeBSD, NetBSD, OpenBSD, and illumos, all of which are operating systems we either have existing support for, or intend to start supporting properly soon.”

CriticizesComment from 27 Nov 2025 in “Migrating the main Zig repository from GitHub to Codeberg”

“The current self-hosted runner gets hung every so often”

CriticizesComment from 18 Nov 2025 in “GitHub: Git operation failures”

Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.