From $2-4 a day to under $0.25: CI moved to a homelab with Claude
After $45 in GitHub Actions overage in one month, a solo founder put an idle homelab to work as CI runners, with Claude making it easy to set up. Daily spend dropped from $2-4 a day to under $0.25.
Done withClaudeSpotted· by HN user joshstrange· Oct 22, 2026
Result Even runs some jobs faster than GitHub's own workers
“After this change I went from spending $2-4/day to <$0.25”
Spotted: found in the wild. Details are as reported by the source above and have not been independently verified.
What they did
After running up $45 in GitHub Actions overage spending in a month, a solo developer and founder decided to put their largely idle homelab to use. They set up small VMs as self hosted CI runners, deleting and restoring each one from a snapshot after every run, using a custom image with just what was needed.
How it went
With Claude it was super easy to get set up, and it worked out even better than hoped. Daily GitHub Actions spend dropped from $2-4 a day to under $0.25, and some jobs even ran faster since the homelab workers were bigger than the default GitHub worker; they kept a few very small tasks on GitHub Actions itself.
Try it yourself with Claude
Help me set up self hosted CI runners on my own hardware to replace [GitHub Actions/my CI provider] for [PR checks / unit and e2e tests]: build a minimal custom VM image with just the tools I need, and script it so each VM is deleted and restored from a clean snapshot after every job run.
A starting prompt written by Agents in the Wild. Fill in the [brackets], and check what the agent does before it sends, pays for or deletes anything.
A first homemade synth has 36 hall-effect keys and buttons and 7 rotary encoders. The firmware started by hand, then gentle prodding at Claude got everything needed much faster. Rev 2 of the PCB is nearly done.
Working on a Quake project, Claude decided on its own to build a test suite: demo playbacks with snapshots compared pixel by pixel, plus recorded demos whose screenshots it checked for each element.
After building a minimal proof assistant, the writer asked Claude how they knew the prover was actually sound. Claude checked, found five different ways it could prove false theorems, and fixed them.
Four years after shelving a homemade RSS reader and selling off its $500 domain, the writer built it this year with Codex and Claude. They use it daily, along with 30 other strangers who found it public.
Chasing a childhood itch for the exact 1996 After Dark Flying Toasters screensaver, the writer turned to Claude. It did a lot of good reverse-engineering work, but kept inventing details that needed pushback.
A rabbitmq connector occasionally got stuck after rare network drops, too minor to spend days fixing. Claude built a test harness that reproduced it, and the actual fix wasn't too hard.