CI Runner Farm

CI Runner Farm turns an Unraid server into a self-hosted fleet of Docker-based runners for GitHub Actions or GitLab continuous integration/continuous delivery…

  • Development
  • Infrastructure
  • Network Services
  • Plugins
  • Productivity
  • Tools & Utilities
CI Runner Farm turns an Unraid server into a self-hosted fleet of Docker-based runners for GitHub Actions or GitLab continuous integration/continuous delivery (CI/CD), offering concurrent resource-capped jobs, warm package caches, Docker-in-Docker, autoscaling, and single-page management for trusted private workloads.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

69/100 Good

Maintained
100last commit 5 days ago
Popular
2928 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data
Security check
100no serious findings, CI, tests

Based on 4 of 5 factors.

Availability: platform listings confirmed today, links checked 4 days ago

GitHub stars
28
Open issues
25
Last commit
2026-11-16
Latest release
v3.7.1
License
Apache-2.0
Activity
rising

Checked 4 days ago - source: GitHub (unraid/ci-runner-farm)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Setup & security Configure from the Unraid webGUI page: pick a provider (GitHub Actions or GitLab CI/CD), paste your token, then use Start/Stop/Restart/Scale to manage runner slots. Only point the farm at trusted/private repositories — self-hosted and Docker-in-Docker (DinD) runners execute arbitrary workflow code and run privileged, so never let public/fork-PR code run on them. source
  • First install and security Add a GitHub or GitLab token, choose a repository or organization, then start or scale runner slots from the Unraid webGUI. Treat privileged Docker-in-Docker runners as high-trust targets and use them only for repositories you control. source

Fetched 44 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Can CI Runner Farm be used for GitLab CI/CD, not only GitHub Actions?

Yes, the farm can provide self-hosted runners for GitHub Actions or GitLab CI/CD.

Can it run multiple runners without adding a virtual machine?

Yes, it can scale several single-job runner slots without requiring a VM.

Does it keep dependency or image caches warm?

Yes, the farm keeps package and image caches warm.

Does it support jobs that need Docker-in-Docker?

Yes, Docker-in-Docker is supported.

Answers sourced from github.com

Community

Collected 48 days ago - public community threads