GitHub Runner Under the Desk: More CI for Less

A self-hosted GitHub Actions runner on a machine in your office costs about three months of cloud, and the IRS writes it off over five years. Keeping ten of them patched, clean and registered is work GitHub leaves to you. A Jaah node does it from a tab, on the machine that already runs your coding agents.

Every engineer who has set up a self-hosted GitHub Actions runner remembers how easy it was: an afternoon, on a machine bought for the purpose and parked under a desk. The second runner gets talked about less. The machine is the cheap part; the upkeep after it is a chore that never ends, and a tenth runner needs a machine that does its own upkeep.

One runner, one afternoon

GitHub’s documentation, as it reads in October 2026, makes it three tasks: download and extract the runner, run its configuration script with a token the settings page gives you, and start it. To keep it running after a reboot you install the runner as a service, which takes two more commands. The token lasts an hour, the runner shows up in the repository’s settings with a green dot, and one line of your workflow changes to send jobs to it.

Then the CI grows. GitHub’s Octoverse report for 2025 counted eleven and a half billion minutes of Actions in public projects alone, thirty-five per cent more than the year before. A team’s own CI grows the same way: a second machine, then a third, then the one in the other office that nobody has logged into since the person who set it up left.

Bought once

A hosted runner is sold by the minute, on a rate card that climbs with the core count, as GitHub’s pricing page sets it out in October 2026. Rent a machine of the size you actually want instead, and the rent runs all month, through the nights, the weekends and the fortnight everyone spent at the offsite. Either way you are paying for a meter, and when it stops you own nothing.

A machine in your office is bought once. It costs about three months of that rented machine, and then it is yours. A box that dies goes back to the shop, or a spare comes out of the cupboard, and six months of cloud buys two. The IRS, in its 2025 guide to depreciation, treats a computer as five-year property.

As of October 2026, GitHub’s billing page lists self-hosted runners among the things it does not charge for. GitHub announced a charge for them in December 2025 and then postponed it. So the sum is three months of cloud against a machine the IRS writes off over five years and, for now, nothing on GitHub’s meter. It leaves out everything after the purchase.

Responsible for the rest

GitHub’s page on self-hosted runners, as of October 2026, is plain: you are responsible for updating the operating system and all other software. A runner, it notes, can keep the same instance from one job to the next. On day one that is a convenience, because the cache survives and builds are quick. By day ninety it is why a test passes on one runner and fails on another, and why the disk is full of Docker images no workflow uses. The runner application does update itself, the one chore GitHub keeps, as long as the runner is up when the update arrives.

In 2026 that update got a deadline. GitHub’s minimum-version rule, paused in March, got its timeline in June: once the rule applies, a runner thirty days behind a release stops getting jobs. The machine in the other office is the one it happens to.

Actuated, which sells a way around all this, says it in one sentence of its documentation as of October 2026: self-hosted runners are continually out of date, and require fine-tuning. Anyone who has run a fleet has a list of their own. The runner someone restarted in a hurry runs as the wrong user, two jobs want the same port, and a job vanishes without a line in the log because the machine rebooted halfway through it. The bill is paid in hours, by whoever sits nearest the machine.

The runner that remembers

The upkeep is the mild problem. A machine that keeps things between jobs can be made to keep the wrong ones. GitHub’s security guidance, as of October 2026, says self-hosted runners should almost never be used for public repositories, because untrusted code in a workflow can compromise a runner for good.

In July 2023 the security researcher Adnan Khan fixed a typo in GitHub’s own runner-images repository. That made him a contributor, and his next pull request ran on the repository’s self-hosted runners with nobody approving it. The runner kept what each job left behind, his included. In January 2024 Khan and John Stawinski published the same attack against PyTorch, reading the repository’s write token off a persistent runner’s disk. Each chain started with a typo fix and a setting nobody had changed.

GitHub had shipped its answer a month before the first of them: a runner that forgets. In June 2023 it added just-in-time runners, a single-use registration honoured for one job and then deleted, which leaves no long-lived key on the box to steal. Its guidance as of October 2026 recommends ephemeral runners that start clean. Read as a list, that guidance is a specification. For every job, make a clean environment, mint a credential, start a runner and run the job, then destroy the environment, the credential and the runner. By hand, that is a great deal more than an afternoon.

A controller, or a contract

The specification has an implementation. The Actions Runner Controller, a Kubernetes operator that orchestrates and scales self-hosted runners in GitHub’s words, went into public beta in May 2023 and reached release 0.14.0 in March 2026. It runs a runner per pod, ephemeral by design, scaled to the queue. The catch is the first noun in GitHub’s description. For a team that already lives in Kubernetes this is a Tuesday. For the team with a machine under a desk it is a second job to replace the first.

The other implementation is someone else’s. As of October 2026 a small industry of managed runners will register with your repository and run its jobs on their machines or on yours: Blacksmith, Depot, Namespace, WarpBuild, RunsOn, Ubicloud and Actuated. Each is a vendor, so a bill comes back. A vendor can also close. BuildJet shut its runner service down, announcing it in February 2026 and stopping jobs on 31 March, and its customers had to change one line in every workflow.

On the box you already have

A Jaah node is the machine where your agents work, around the clock: a box in your office joined with one pasted command, or a machine Jaah launched in your AWS account. As of October 2026 each node in the console has a GitHub Runners tab. You pick the repository, a stored credential for it and how many runners you want, and press Apply. That is the whole form. Pause stops the runners, Resume brings them back, and Remove takes the pool away, with its runners, their users and their Docker stores, and leaves the node as it was.

Behind the form, the node runs the specification from two sections ago as code. Each runner is its own Unix user with its own rootless Docker. Before every job the node deletes that user’s home, Docker store included, provisions it again and extracts the runner afresh from a pinned, checksummed archive, so the version on disk is the one the pool declares and nothing from the previous job survives. It then asks GitHub for a just-in-time registration, the single-use kind introduced in 2023, so the box holds a runner key for one job at most. Security updates install unattended and never reboot a machine that has a job on it.

The console also does the running that GitHub leaves to you. The tab shows each runner as GitHub sees it, idle or busy. A machine whose disk is filling pauses its own runners and resumes them when the space comes back. Sent the stop signal, GitHub’s runner kills its job instead of finishing it, a limitation reported on the runner’s issue tracker in May 2024, so Pause drains the pool: idle runners stop first, and the rest as their jobs finish.

The pool is on your machine and registered to your repository. The node was already there and, if it is the box in your office, it was bought once. Since 2026 the same machine has run the agents that write a change, the runners that test it, and the agents that deploy it, watch it in production and roll it back. A sensitive change to authentication, credentials, migrations or personal data waits for your approval or, when you run it unattended, for a security review of its own.

The tenth runner

On a Jaah node the tenth runner is the same form as the first, with the count set to ten and Apply pressed once more.

  1. Adding self-hosted runners, GitHub Docs, 2026-10.
  2. Configuring the self-hosted runner application as a service, GitHub Docs, 2026-10.
  3. Octoverse 2025: a new developer joins GitHub every second, GitHub, 2025-10-28.
  4. GitHub Actions runner pricing, GitHub Docs, 2026-10.
  5. Publication 946 (2025), How To Depreciate Property, Internal Revenue Service, 2025.
  6. About billing for GitHub Actions, GitHub Docs, 2026-10.
  7. Update to GitHub Actions pricing (a self-hosted runner charge announced, then postponed), GitHub Changelog, 2025-12-16.
  8. Self-hosted runners, GitHub Docs, 2026-10.
  9. Self-hosted runners reference, GitHub Docs, 2026-10.
  10. Self-hosted runner minimum version enforcement paused, GitHub Changelog, 2026-03-13.
  11. GitHub Actions: minimum version enforcement timeline for self-hosted runners, GitHub Changelog, 2026-06-12.
  12. Actuated documentation, Actuated, 2026-10.
  13. Secure use reference, GitHub Docs, 2026-10.
  14. One Supply Chain Attack to Rule Them All: poisoning GitHub’s runner images, Adnan Khan, 2023-12-20.
  15. Playing with Fire: how we executed a critical supply chain attack on PyTorch, John Stawinski, 2024-01-11.
  16. GitHub Actions: just-in-time self-hosted runners, GitHub Changelog, 2023-06-02.
  17. Actions Runner Controller, GitHub Docs, 2026-10.
  18. GitHub Actions: Actions Runner Controller public beta, GitHub Changelog, 2023-05-10.
  19. Actions Runner Controller release 0.14.0, GitHub Changelog, 2026-03-19.
  20. Blacksmith, Blacksmith, 2026-10.
  21. Depot, Depot, 2026-10.
  22. Namespace, Namespace, 2026-10.
  23. WarpBuild, WarpBuild, 2026-10.
  24. RunsOn, RunsOn, 2026-10.
  25. Ubicloud, Ubicloud, 2026-10.
  26. Actuated, Actuated, 2026-10.
  27. BuildJet for GitHub Actions has been shut down, BuildJet, 2026-10.
  28. BuildJet is shutting down: migrate to WarpBuild, WarpBuild, 2026-02-10.
  29. Machines: the GitHub Runners tab of a node, Jaah Docs, 2026-10.
  30. SIGTERM kills the job instead of waiting for job completion (actions/runner issue 3308), GitHub, actions/runner, 2024-05-29.

All posts