CI Runnerscirunners.org
Runner profile · Open-source project

GARM (GitHub Actions Runner Manager)

Answer in brief

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.

By the CI Runners editors · Updated

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

AttributeDetails
CI systemsGitHub Actions, Forgejo/Gitea Actions
Operating systemsLinux, Windows
Architecturesx64, arm64
DeploymentOpen-source project
Where it can runAWS, Azure, Google Cloud, Oracle Cloud, OpenStack, Kubernetes, LXD, Incus, CloudStack, Akamai/Linode
IsolationRunners 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 jobYes
HardwareNot documented
Performance (vendor claim)Not documented
Runner sizesNot documented
CachingNot documented
Docker layer cachingNot documented
GPUNot documented
ConcurrencyEach pool or scale set has a maximum number of runners and a minimum number of idle runners
Job limitsNot documented
Static IPsNot documented
SSH into running jobsYes
ObservabilityPrometheus metrics with ready-made Grafana dashboards and starter alert rules, plus a built-in web UI
SetupRun 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]
PricingFree and open source; you pay for the infrastructure it runs on.
Free tierNot documented
ComplianceNot documented
RegionsNot documented
Open sourceYes (Apache-2.0)
Company headquartersTimiș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

How GARM (GitHub Actions Runner Manager) compares

RunnerCI systemsRuns onDeploymentIsolationPriceLargest runnerDocker layer cacheGPUOpen sourceCompany HQ
GARM (GitHub Actions Runner Manager)GitHub Actions, Forgejo/Gitea ActionsLinux, Windows, x64, arm64Self-hostedDepends on providerFree software + your infrastructureSet by your infrastructureNot documentedNot documentedYesRomania
Actions Runner Controller (ARC)GitHub ActionsLinux, WindowsSelf-hostedKubernetes podFree software + your infrastructureSet by your infrastructureNot documentedNot documentedYesUnited States
terraform-aws-github-runnerGitHub ActionsLinux, Windows, macOS, x64, arm64Self-hostedEC2 instanceFree software + your infrastructureSet by your infrastructureNot documentedYesYesNot documented
myshoesGitHub ActionsLinuxSelf-hostedDepends on providerFree software + your infrastructureSet by your infrastructureNot documentedNot documentedYesNot documented
FireactionsGitHub ActionsLinux, x64, arm64Self-hostedFirecracker microVMFree software + your infrastructureSet by your infrastructureNot documentedNoYesLithuania
CirunGitHub ActionsLinux, macOS, Windows, x64, arm64Your cloud or hardwareCloud VM$29/mo (3 private repos) + cloud costSet by your infrastructureYesYesNoUnited Kingdom
RunsOnGitHub ActionsLinux, Windows, x64, arm64Your cloud or hardwareEC2 instance€300/yr licence + AWS cost896 vCPUYesYesNoFrance
TestFlows GitHub Hetzner RunnersGitHub ActionsLinux, x64, arm64Self-hostedHetzner Cloud VMFree software + your infrastructureSet by your infrastructureYesNot documentedYesNot 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

See all GARM (GitHub Actions Runner Manager) alternatives →

Frequently asked questions

What is 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.
Which CI systems does GARM (GitHub Actions Runner Manager) work with?
GARM (GitHub Actions Runner Manager) runs jobs for GitHub Actions and Forgejo/Gitea Actions, on Linux, Windows, x64 and arm64.
How does GARM (GitHub Actions Runner Manager) isolate jobs?
GARM (GitHub Actions Runner Manager) documents its isolation as: 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. Each job gets a fresh environment that is discarded afterwards.
Is GARM (GitHub Actions Runner Manager) open source?
Yes (Apache-2.0). It can be self-hosted.
How much does GARM (GitHub Actions Runner Manager) cost?
Free and open source; you pay for the infrastructure it runs on. Check the official pricing page for current rates.
How do you set up GARM (GitHub Actions Runner Manager)?
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. An example label is [ubuntu, generic].
Does GARM (GitHub Actions Runner Manager) support ARM64 runners?
Yes, GARM (GitHub Actions Runner Manager) documents arm64 runners (Linux and Windows).
How many jobs can run at once on GARM (GitHub Actions Runner Manager)?
Each pool or scale set has a maximum number of runners and a minimum number of idle runners.
Where is Cloudbase Solutions based?
Cloudbase Solutions, the organisation behind GARM (GitHub Actions Runner Manager), is headquartered in Timișoara, Romania. That is where the company is based, not where jobs run.
What are the alternatives to GARM (GitHub Actions Runner Manager)?

Sources

  1. github.com/cloudbase/garm
  2. github.com/cloudbase/garm/releases
  3. github.com/cloudbase/garm/releases/tag/v0.2.0
  4. github.com/cloudbase/garm/blob/main/doc/pools-and-scaling.md
  5. github.com/cloudbase/garm/blob/main/doc/scale-sets.md
  6. github.com/cloudbase/garm/blob/main/doc/agent-and-object-store.md
  7. github.com/cloudbase/garm/blob/main/doc/monitoring.md
  8. github.com/cloudbase/garm/blob/v0.2.1/doc/managing-entities.md
  9. github.com/cloudbase/garm/blob/main/LICENSE
  10. 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/