CI Runnerscirunners.org
Head-to-head

GARM (GitHub Actions Runner Manager) vs myshoes

Answer in brief

GARM (GitHub Actions Runner Manager) suits teams that want one self-hosted controller for GitHub or Gitea runners spread over several clouds or private infrastructure. myshoes suits platform teams that run a private cloud such as OpenStack or LXD and want to offer on-demand GitHub Actions runners to their organisation. GARM (GitHub Actions Runner Manager) is an open-source project you run yourself for GitHub Actions and Forgejo/Gitea Actions; myshoes is an open-source project you run yourself for GitHub Actions.

By the CI Runners editors · Updated

Key differences between GARM (GitHub Actions Runner Manager) and myshoes

  • CI systems: Only GARM (GitHub Actions Runner Manager) documents Forgejo/Gitea Actions.
  • Operating systems: Only GARM (GitHub Actions Runner Manager) documents Windows.
  • Licence: GARM (GitHub Actions Runner Manager) is Apache-2.0; myshoes is MIT.

What they have in common

  • Both are open-source projects you run yourself.
  • Both run GitHub Actions jobs.
  • Both document Linux runners.
  • Both are open source.
  • Both can be self-hosted.

GARM (GitHub Actions Runner Manager) vs myshoes at a glance

AttributeGARM (GitHub Actions Runner Manager)myshoes
What it isSelf-hosted runner manager for GitHub and Gitea Actions that creates ephemeral runners across clouds through provider plugins.Daemon that provisions self-hosted GitHub Actions runners on demand through pluggable providers such as LXD, OpenStack and AWS.
TypeOpen-source projectOpen-source project
CI systemsGitHub Actions, Forgejo/Gitea ActionsGitHub Actions
Operating systemsLinux, WindowsLinux
Architecturesx64, arm64Not documented
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 chooseRunners are instances created by a provider plugin (LXD, OpenStack, AWS EC2 or your own), so the boundary depends on the provider; whether each instance is single-use is not stated in the README or setup docs
Fresh environment per jobYesNot documented
HardwareNot documentedNot documented
Performance (vendor claim)Not documentedNot documented
Runner sizesNot documentedNine named resource types from nano to 4xlarge, which each provider maps to its own machine specs
CachingNot documentedNot documented
Docker layer cachingNot documentedNot documented
GPUNot documentedThe README lists special hardware such as GPUs and FPGAs as a reason to use your own provider, without setup details.
ConcurrencyEach pool or scale set has a maximum number of runners and a minimum number of idle runnersMAX_CONNECTIONS_TO_BACKEND caps connections to the provider (default 50)
Static IPsNot documentedNot documented
SSH into running jobsYesNot documented
PricingFree and open source; you pay for the infrastructure it runs on.Free and open source; you pay for the infrastructure it runs on.
Free tierNot documentedNot documented
Open sourceYes (Apache-2.0)Yes (MIT)
Self-host / your cloudYes / YesYes / Yes
ComplianceNot documentedNot documented
RegionsNot documentedNot documented
Company headquartersTimișoara, RomaniaNot documented
Good fit forTeams that want one self-hosted controller for GitHub or Gitea runners spread over several clouds or private infrastructurePlatform teams that run a private cloud such as OpenStack or LXD and want to offer on-demand GitHub Actions runners to their organisation

Verified November 22, 2026 from each provider’s documentation. Performance figures are vendor claims, not our measurements.

Which should you choose?

Reasons to choose GARM (GitHub Actions Runner Manager)

  • 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

Reasons to choose myshoes

  • You run private infrastructure such as LXD or OpenStack and want runners created on it
  • You want to set a default runner size per organization and override it for individual repositories
  • You use GitHub Enterprise Server
  • You want to write a provider for your own platform as a gRPC plugin

Trade-offs to check first

  • GARM (GitHub Actions Runner Manager): 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
  • GARM (GitHub Actions Runner Manager): Scale set labels can only be set at creation time and cannot be updated afterwards
  • myshoes: A MySQL database is required
  • myshoes: GitHub (or your GitHub Enterprise Server) must be able to reach the myshoes webhook endpoint

Run your slowest workflow on both before deciding. See the full GARM (GitHub Actions Runner Manager) profile and myshoes profile, or the complete comparison.

More comparisons

Frequently asked questions

Is GARM (GitHub Actions Runner Manager) or myshoes better?
Neither is better for every pipeline. GARM (GitHub Actions Runner Manager) suits teams that want one self-hosted controller for GitHub or Gitea runners spread over several clouds or private infrastructure. myshoes suits platform teams that run a private cloud such as OpenStack or LXD and want to offer on-demand GitHub Actions runners to their organisation.
What is the difference between GARM (GitHub Actions Runner Manager) and myshoes?
Only GARM (GitHub Actions Runner Manager) documents Forgejo/Gitea Actions. Only GARM (GitHub Actions Runner Manager) documents Windows. GARM (GitHub Actions Runner Manager) is licensed Apache-2.0; myshoes is licensed MIT.
Which is open source, GARM (GitHub Actions Runner Manager) or myshoes?
Both are open source (GARM (GitHub Actions Runner Manager): Apache-2.0; myshoes: MIT).
How do GARM (GitHub Actions Runner Manager) and myshoes isolate jobs?
GARM (GitHub Actions Runner Manager): 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. myshoes: Runners are instances created by a provider plugin (LXD, OpenStack, AWS EC2 or your own), so the boundary depends on the provider; whether each instance is single-use is not stated in the README or setup docs.
How does GARM (GitHub Actions Runner Manager) pricing compare with myshoes?
GARM (GitHub Actions Runner Manager): Free and open source; you pay for the infrastructure it runs on. myshoes: Free and open source; you pay for the infrastructure it runs on. Rates change, so check the GARM (GitHub Actions Runner Manager) and myshoes pricing pages before deciding.
Where do GARM (GitHub Actions Runner Manager) and myshoes runners run?
GARM (GitHub Actions Runner Manager) is an open-source project you run yourself (AWS, Azure, Google Cloud, Oracle Cloud, OpenStack, Kubernetes, LXD, Incus, CloudStack and Akamai/Linode). myshoes is an open-source project you run yourself (LXD, OpenStack and AWS).

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/whywaita/myshoes
  6. github.com/whywaita/myshoes/releases
  7. github.com/whywaita/myshoes/blob/master/LICENSE
  8. github.com/whywaita/myshoes/blob/master/docs/01_01_for_admin_setup.md

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) vs myshoes. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/garm-vs-myshoes/