Self-Hosted GitHub Actions Runners
Scalable Docker-based GitHub Actions runners with autoscaling on Kubernetes and Docker Swarm, eliminating per-minute costs while enabling IP-restricted deployments.
Simple self-hosted GitHub Actions runners with autoscaling on Kubernetes/Docker Swarm. Eliminates runner minute costs, enables IP-restricted deployments.
The GitHub Runner Minute Problem
GitHub’s hosted runners charge per-minute usage fees that add up quickly for high-volume teams. IP-restricted production deployments were difficult with shared runners, requiring VPN installation & configuration.
And Github’s Kubernetes operator, ARC, is great for teams running K8s who have the experiment to maintain such deployments. But a lot of mid sized teams, desire something a bit more simple.
High-volume teams spending thousands monthly on runner minutes, with no control over deployment IPs.
Solution: Self-Hosted Autoscaling Runners
Here is where Scalable Github Runners come in, a Docker container with a simple interface, accepting an access token and organisation name via environment variables.
It will then register with GH as an active runner ready to accept jobs. And then on termination, will be culled from GHs registry of active runners.
Allowing you to scale up and down your runners, using your existing container orchestration tooling.
Business Impact
Eliminated £12,000+ annual costs while enabling IP-restricted deployments and dramatically faster builds.
- Saves thousands monthly for high-volume teams
- 100%+ availability in production deployments
- Enables secure deployments with IP restrictions
- Faster builds skipping VPN setup for production deployments
Technical Highlights
- Scale-up/down as/when needed with single commands: e.g
docker service scale ghr=15 - Integrate with your existing container orchestration
- Infinitely scalable, based on hardware availability
- Simple familiar interface for non Kubernetes operators
- Deploy with K8s / Docker Swarm / Docker Compose