# GitHub Actions self-hosted runners

9 Hacker News commenters recommended GitHub Actions self-hosted runners and 25 criticized it, November 2025 to November 2026. It was recommended in 6 of 13 months.

**Verdict:** 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.

## Why people recommend it

- Faster than GitHub cloud runners (3 comments): "the builds are over 10x faster than relying on their cloud runners" ([source](https://news.ycombinator.com/item?id=46292716)) "tests will run faster than on any hosted platform" ([source](https://news.ycombinator.com/item?id=49797245)) "It's a much faster way to iterate." ([source](https://news.ycombinator.com/item?id=46654754))
- Easy to set up (2 comments): "Github's self-hosted runners are actually surprisingly easy to set up and use" ([source](https://news.ycombinator.com/item?id=49201440)) "self hosted github runners to skip the setup" ([source](https://news.ycombinator.com/item?id=49818093))

## What people warn about

- Hangs and CPU-burning sleep loops (4 comments): "they are still using a poor man's sleep that uses up a core in the CPU instead of just using sleep, but progress!" ([source](https://news.ycombinator.com/item?id=46234486)) "Gh actions runners had a dubious implementation of sleep that would cause runners to hang on 100% usage for weeks/months." ([source](https://news.ycombinator.com/item?id=46568929)) "didn't they have a bug in the action runners that would basically cycle the CPU infinitely" ([source](https://news.ycombinator.com/item?id=46310702))
- Proposed fees for self-hosted use (5 comments): "Think if some company had a $15K/month bill in self-runners, they'll now also get a $15k/month additional bill from GitHub." ([source](https://news.ycombinator.com/item?id=46310956)) "Rather than wholesaling charging they should have the self hosted runners implement hooks for that as well." ([source](https://news.ycombinator.com/item?id=46312777)) "Charging for self-hosted runners is like a corkage fee but you still need to open the bottle yourself." ([source](https://news.ycombinator.com/item?id=47490591))
- Weak support outside Linux (3 comments): "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." ([source](https://news.ycombinator.com/item?id=46069854)) "Maintaining Windows and macOS self hosted GH (or GL) runners is a hassle I really don't want to deal with anymore" ([source](https://news.ycombinator.com/item?id=50056932)) "the ones for macOS and Windows seemingly did something that made them a hell lot slower than even running VMs" ([source](https://news.ycombinator.com/item?id=47948108))
- Heavy manual setup, no cleanup (3 comments): "you need 1 runner registration per concurrent job. And each runner needs its own user." ([source](https://news.ycombinator.com/item?id=46294656)) "it literally just runs commands on the host and does not handle provisioning/cleanup" ([source](https://news.ycombinator.com/item?id=46617362)) "The config directory for each runner is normally based on its install path (insane)" ([source](https://news.ycombinator.com/item?id=46297598))

## Alternatives hackers recommend

- [Blacksmith runners](https://hackerapproved.com/p/blacksmith.md): 22 recommend
- [WarpBuild](https://hackerapproved.com/p/warpbuild.md): 12 recommend
- [Namespace](https://hackerapproved.com/p/namespace.md): 8 recommend
- [Forgejo Runner](https://hackerapproved.com/p/forgejo-runner.md): 8 recommend
- [RISE RISC-V Runners](https://hackerapproved.com/p/rise-risc-v-runners.md): 7 recommend

## Where to get it

- [Visit the official site](https://docs.github.com/en/actions/concepts/runners/self-hosted-runners)

## Cite as

Hacker Approved, "GitHub Actions self-hosted runners", https://hackerapproved.com/p/github-actions-self-hosted-runners/ (counts from 1,795,640 Hacker News comments, November 2025 to November 2026).