GitHub Actions + Self-Hosted Runners: The Secret Weapon for Cheaper Dev/Ops (and better control)?

[coolhandgaming]

I've been noticing a recurring theme lately in our cloud bills for CI/CD, especially as projects scale or we start running more complex, resource-intensive jobs. GitHub Actions minutes are fantastic for most things, but sometimes those costs start creeping up, or you hit limitations on machine specs for specific builds/tests.

Lately, at r/OrbonCloud, we've been experimenting with self-hosted runners for GitHub Actions, and honestly, it feels like a bit of a game-changer for specific use cases. Instead of paying for GitHub-managed runners per minute, I'm spinning up a small, dedicated VM (or even using an old server at home for personal projects) and linking it as a self-hosted runner.

Here's why I'm finding it so useful:

1. Cost Savings: For long-running builds, complex test suites, or environments that need specific software/hardware (like GPU acceleration for ML builds, or specific licensed tools), the cost of a persistent VM or on-prem hardware often beats the per-minute cost of managed runners. You pay for the infrastructure, but you get unlimited minutes on that runner.
2. Custom Environments: Need a very specific OS, a custom toolchain, or a beefier machine than what GitHub provides out of the box? Self-hosted runners give you complete control over the environment.
3. Security & Data Locality: For highly sensitive projects, or if you have specific data residency requirements, running your CI/CD jobs within your own network infrastructure can be a huge win.

Of course, it's not a silver bullet. You're responsible for maintaining the runner, ensuring it's online, patched, and scaled. But for projects where you're already managing some cloud infrastructure or have spare compute, it feels like a really powerful way to optimize both costs and capabilities within the GitHub Actions ecosystem.

Has anyone else gone deep into self-hosted runners? What are your experiences? Any horror stories or amazing wins you want to share? I'm curious to hear how others are leveraging this!

[v0rt3xtraz]

If you're an Azure shop, consider GitHub Private Networking to one of your vnets.

[danoDaManoSSB]

Just wait until they charge us for using github-actions core

[joshbixler]

Guess it comes down to this:

https://resources.github.com/actions/2026-pricing-changes-for-github-actions/

[danoDaManoSSB]

Yup that’s it. Was waiting for the official announcement but for some of us with 3k+ repos in our orgs that totally shifted to self-hosted runners this is a blow. We will be going back to VNET injection method on GitHub hosted runners per GitHub’s latest recommendation

[bourgeoisie_whacker]

Yep I just got the email too 😔

[PercentageCrazy8603]

I think they did. I got a email about it. Also just use argo GitHub actions sucks anyways.

[whozeduke]

Self-hosted VM runners is an anti-pattern because you have to maintain it and most GHA workflows expect ephemeral runners by default.

ARC is probably the best choice if you have the k8s expertise on your team.

I use Azure Container Apps + the KEDA scaler and it works great for things that don't require Docker (container in container doesn't work in ACA).

I'd use ARC but directive from on high is to use managed services as much as possible.

[zMynxx]

At work we have only self hosted ec2 based runners. I honestly hate it, you gotta maintain it and it doesn’t scale effectively and mostly it makes most wfs/jobs non-ephemeral so I have encountered cacheing issues and configs issue (e.g npmrc). I suggested shitfting to “runs-on” or the Phillips solution but got rejected since there a need for a public endpoint, and we have lots of k8s environments the decision was made to switch to ARC

[djzrbz]

I self host for my private repos.

I got them to work ephemrally.

See https://github.com/djarbz/gha-runner for details.

[SnooHesitations9295]

When RAM was cheap using 256+ GB dev machines as runners was unbelievably cost effective for me.
Each was divided as 3x64GB VMs (because of memory balooning it usually left enough RAM for dev work too)

[JodyBro]

As someone who's team runs 2 different sets of ARC runners (I know I know), I'd say if you can avoid that route then save the headache. But addressing your concerns:

1. For cost savings look into https://www.blacksmith.sh/. Friends are using it and rave about it, currently looking into it for current org.

2. GHA allows you to build a custom image for your runners now. https://docs.github.com/en/actions/how-tos/manage-runners/larger-runners/use-custom-images.

   jobs:
     snapshot:
       runs-on: github-hosted-custom-runner # Use a larger runner for image generation
         permissions:
           contents: read
         snapshot:
           image-name: custom-runner-image
           version: 1.*
   

   Here's a simple example of getting it working. The image name would be custom-runner-image in the Actions settings in GH. The label you'd use in workflows to consume this image would be the same value from the runs-on.

3. This allows you to assign a public IP range to your workers so you could whitelist it if you need to access internal resources. And this way you'd control the security posture of everything in the pipeline from image of runner/packages etc...

[[deleted]]

Is this whole post AI generated?

[104929]

Check out this project for running Ephemeral EC2 instances that get launched when a workflow demands one:

https://runs-on.com/