GARM (GitHub Actions Runner Manager)
Self-hosted runner manager for GitHub and Gitea Actions that creates ephemeral runners across clouds through provider plugins. A single-binary, multi-cloud runner manager for GitHub and Gitea Actions; it suits teams that run their own infrastructure across more than one provider.
Overview
GARM (GitHub Actions Runner Manager) is a self-hosted runner manager for GitHub Actions and Gitea Actions. A single controller creates, scales and destroys ephemeral runner instances through external provider executables. It offers two scaling modes: pools, which react to workflow_job webhooks and match jobs to pools by label, and scale sets, which use GitHub’s runner scale set message queue so that no webhook endpoint is needed.
GARM ships as one binary with an embedded SQLite database and a built-in web UI. The README lists providers for Amazon EC2, Azure, GCP, Oracle OCI, OpenStack, LXD, Incus, Kubernetes, CloudStack and (experimental) Akamai/Linode, and providers can be written in any language. It works with github.com, GitHub Enterprise Server and Gitea, at repository, organization and enterprise level. A Kubernetes operator is maintained separately by Mercedes-Benz.
Notable
- v0.2.0 (26 April 2026) was the first stable release of the v0.2 branch, adding runner scale sets, Gitea support, agent mode with remote shell access and a new web UI
- v0.2.1 was released on 8 May 2026 to follow the renaming of Gitea’s runner assets
- The README credits Mercedes-Benz for the GARM Kubernetes operator and links its Kubernetes provider
GARM (GitHub Actions Runner Manager) specifications
| Attribute | Details |
|---|---|
| CI systems | GitHub Actions, Forgejo/Gitea Actions |
| Operating systems | Linux, Windows |
| Architectures | x64, arm64 |
| Deployment | Open-source project |
| Where it can run | AWS, Azure, Google Cloud, Oracle Cloud, OpenStack, Kubernetes, LXD, Incus, CloudStack, Akamai/Linode |
| Isolation | Runners are instances created by an external provider (cloud VMs, LXD or Incus instances, or Kubernetes pods), so the boundary depends on the provider you choose |
| Fresh environment per job | Yes |
| Hardware | Not documented |
| Performance (vendor claim) | Not documented |
| Runner sizes | Not documented |
| Caching | Not documented |
| Docker layer caching | Not documented |
| GPU | Not documented |
| Concurrency | Each pool or scale set has a maximum number of runners and a minimum number of idle runners |
| Job limits | Not documented |
| Static IPs | Not documented |
| SSH into running jobs | Yes |
| Observability | Prometheus metrics with ready-made Grafana dashboards and starter alert rules, plus a built-in web UI |
| Setup | Run the GARM binary with Docker or systemd, add credentials for your forge and install a provider. Then create a pool or scale set for a repository, organization or enterprise. |
| Example label | [ubuntu, generic] |
| Pricing | Free and open source; you pay for the infrastructure it runs on. |
| Free tier | Not documented |
| Compliance | Not documented |
| Regions | Not documented |
| Open source | Yes (Apache-2.0) |
| Company headquarters | Timișoara, Romania · More from Romania |
Facts from GARM (GitHub Actions Runner Manager)’s public documentation, verified November 22, 2026. Performance figures are vendor claims.
Strengths and trade-offs
Reasons to choose it
- You want one controller that manages runners in several clouds and on private infrastructure at once
- You want a single binary with an embedded SQLite database instead of an external database or message broker
- You run Gitea or GitHub Enterprise Server as well as github.com
- You want to choose between webhook-driven pools and GitHub runner scale sets
- You want to write your own provider for infrastructure that is not covered
Trade-offs
- Pools rely on workflow_job webhooks, so the forge must be able to reach GARM; the release notes cite lost webhook deliveries as a risk that scale sets avoid
- Scale set labels can only be set at creation time and cannot be updated afterwards
- The README warns that the main branch and its documentation describe unreleased code and are not guaranteed to be stable
- The Kubernetes, CloudStack and Linode providers are maintained outside the cloudbase organisation, and the Linode provider is marked experimental
Good fit for: Teams that want one self-hosted controller for GitHub or Gitea runners spread over several clouds or private infrastructure.
Use cases GARM (GitHub Actions Runner Manager) fits
- ARM64 builds: Pools accept arm64 as a runner architecture.
- Windows builds: Pools accept windows as an OS type alongside linux.
- Your own cloud: Providers create runners in your own cloud accounts, OpenStack, LXD, Incus or Kubernetes.
- Open source and self-hosted: GARM is Apache-2.0 licensed and runs as a single self-hosted binary.
How GARM (GitHub Actions Runner Manager) compares
| Runner | CI systems | Runs on | Deployment | Isolation | Price | Largest runner | Docker layer cache | GPU | Open source | Company HQ |
|---|---|---|---|---|---|---|---|---|---|---|
| GARM (GitHub Actions Runner Manager) | GitHub Actions, Forgejo/Gitea Actions | Linux, Windows, x64, arm64 | Self-hosted | Depends on provider | Free software + your infrastructure | Set by your infrastructure | Not documented | Not documented | Yes | Romania |
| Actions Runner Controller (ARC) | GitHub Actions | Linux, Windows | Self-hosted | Kubernetes pod | Free software + your infrastructure | Set by your infrastructure | Not documented | Not documented | Yes | United States |
| terraform-aws-github-runner | GitHub Actions | Linux, Windows, macOS, x64, arm64 | Self-hosted | EC2 instance | Free software + your infrastructure | Set by your infrastructure | Not documented | Yes | Yes | Not documented |
| myshoes | GitHub Actions | Linux | Self-hosted | Depends on provider | Free software + your infrastructure | Set by your infrastructure | Not documented | Not documented | Yes | Not documented |
| Fireactions | GitHub Actions | Linux, x64, arm64 | Self-hosted | Firecracker microVM | Free software + your infrastructure | Set by your infrastructure | Not documented | No | Yes | Lithuania |
| Cirun | GitHub Actions | Linux, macOS, Windows, x64, arm64 | Your cloud or hardware | Cloud VM | $29/mo (3 private repos) + cloud cost | Set by your infrastructure | Yes | Yes | No | United Kingdom |
| RunsOn | GitHub Actions | Linux, Windows, x64, arm64 | Your cloud or hardware | EC2 instance | €300/yr licence + AWS cost | 896 vCPU | Yes | Yes | No | France |
| TestFlows GitHub Hetzner Runners | GitHub Actions | Linux, x64, arm64 | Self-hosted | Hetzner Cloud VM | Free software + your infrastructure | Set by your infrastructure | Yes | Not documented | Yes | Not documented |
Head-to-head: Actions Runner Controller (ARC) vs GARM (GitHub Actions Runner Manager) · Cirun vs GARM (GitHub Actions Runner Manager) · Fireactions vs GARM (GitHub Actions Runner Manager) · GARM (GitHub Actions Runner Manager) vs myshoes · GARM (GitHub Actions Runner Manager) vs terraform-aws-github-runner · GARM (GitHub Actions Runner Manager) vs TestFlows GitHub Hetzner Runners
Frequently asked questions
What is GARM (GitHub Actions Runner Manager)?
Which CI systems does GARM (GitHub Actions Runner Manager) work with?
How does GARM (GitHub Actions Runner Manager) isolate jobs?
Is GARM (GitHub Actions Runner Manager) open source?
How much does GARM (GitHub Actions Runner Manager) cost?
How do you set up GARM (GitHub Actions Runner Manager)?
[ubuntu, generic].Does GARM (GitHub Actions Runner Manager) support ARM64 runners?
How many jobs can run at once on GARM (GitHub Actions Runner Manager)?
Where is Cloudbase Solutions based?
What are the alternatives to GARM (GitHub Actions Runner Manager)?
Sources
- github.com/cloudbase/garm
- github.com/cloudbase/garm/releases
- github.com/cloudbase/garm/releases/tag/v0.2.0
- github.com/cloudbase/garm/blob/main/doc/pools-and-scaling.md
- github.com/cloudbase/garm/blob/main/doc/scale-sets.md
- github.com/cloudbase/garm/blob/main/doc/agent-and-object-store.md
- github.com/cloudbase/garm/blob/main/doc/monitoring.md
- github.com/cloudbase/garm/blob/v0.2.1/doc/managing-entities.md
- github.com/cloudbase/garm/blob/main/LICENSE
- cloudbase.it/about/
Check before you rely on it. Products change quickly, and this page reflects public documentation as of November 22, 2026. Confirm anything that matters in the provider’s own documentation.
Cite this page
CI Runners. (2026). GARM (GitHub Actions Runner Manager). cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/runners/garm/