CI Runnerscirunners.org
Runner profile · Open-source project

myshoes

Answer in brief

Daemon that provisions self-hosted GitHub Actions runners on demand through pluggable providers such as LXD, OpenStack and AWS. A community-maintained runner provisioner with a plugin model for private clouds; it suits platform teams offering GitHub Actions runners on LXD, OpenStack or AWS.

By the CI Runners editors · Updated

Overview

myshoes is a Go daemon that provides auto-scaling self-hosted runners for GitHub Actions. It receives workflow_job webhooks through a GitHub App and asks a provider plugin, which the project calls a shoes provider, to add or delete a runner instance. Providers are separate binaries that speak gRPC; the project links providers for LXD, OpenStack and AWS EC2, and documents how to write your own.

An administrator runs the daemon with a MySQL database and a machine image for the runners. Users then register a repository or an organization as a target through a REST API and pick a resource type from nano to 4xlarge; a repository can override the size set for its organization. GitHub Enterprise Server is supported through a GITHUB_URL setting. The README links talks about its use for an internal hosted-runner service at CyberAgent.

Notable

  • v1.20.4 was released on 5 November 2026
  • The README links a talk titled “Development myshoes and Provide Cycloud-hosted runner” and one on an OSS CI/CD platform at CyberAgent

myshoes specifications

AttributeDetails
CI systemsGitHub Actions
Operating systemsLinux
ArchitecturesNot documented
DeploymentOpen-source project
Where it can runLXD, OpenStack, AWS
IsolationRunners 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 jobNot documented
HardwareNot documented
Performance (vendor claim)Not documented
Runner sizesNine named resource types from nano to 4xlarge, which each provider maps to its own machine specs
CachingNot documented
Docker layer cachingNot documented
GPUThe README lists special hardware such as GPUs and FPGAs as a reason to use your own provider, without setup details.
ConcurrencyMAX_CONNECTIONS_TO_BACKEND caps connections to the provider (default 50)
Job limitsNot documented
Static IPsNot documented
SSH into running jobsNot documented
ObservabilityOptional Docker Hub rate-limit metrics
SetupAn admin runs the myshoes daemon with a MySQL database, a GitHub App and a provider plugin. Users install the GitHub App and register a repository or organization as a target through the REST API.
Example labelNot documented
PricingFree and open source; you pay for the infrastructure it runs on.
Free tierNot documented
ComplianceNot documented
RegionsNot documented
Open sourceYes (MIT)
Company headquartersNot documented

Facts from myshoes’s public documentation, verified November 22, 2026. Performance figures are vendor claims.

Strengths and trade-offs

Reasons to choose it

  • 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

  • A MySQL database is required
  • GitHub (or your GitHub Enterprise Server) must be able to reach the myshoes webhook endpoint
  • The README lists the GCP provider as not yet available
  • Admins must prepare the runner machine image themselves; the setup guide strongly recommends preinstalling Docker and the runner package

Good fit for: Platform teams that run a private cloud such as OpenStack or LXD and want to offer on-demand GitHub Actions runners to their organisation.

Use cases myshoes fits

  • Your own cloud: Providers create runners on your own LXD hosts, OpenStack cloud or AWS account.
  • Open source and self-hosted: myshoes is MIT licensed and self-hosted, with providers as separate open-source plugins.

How myshoes compares

RunnerCI systemsRuns onDeploymentIsolationPriceLargest runnerDocker layer cacheGPUOpen sourceCompany HQ
myshoesGitHub ActionsLinuxSelf-hostedDepends on providerFree software + your infrastructureSet by your infrastructureNot documentedNot documentedYesNot documented
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
FireactionsGitHub ActionsLinux, x64, arm64Self-hostedFirecracker microVMFree software + your infrastructureSet by your infrastructureNot documentedNoYesLithuania
TestFlows GitHub Hetzner RunnersGitHub ActionsLinux, x64, arm64Self-hostedHetzner Cloud VMFree software + your infrastructureSet by your infrastructureYesNot documentedYesNot documented
CirunGitHub ActionsLinux, macOS, Windows, x64, arm64Your cloud or hardwareCloud VM$29/mo (3 private repos) + cloud costSet by your infrastructureYesYesNoUnited Kingdom

Head-to-head: Fireactions vs myshoes · GARM (GitHub Actions Runner Manager) vs myshoes

See all myshoes alternatives →

Frequently asked questions

What is myshoes?
Daemon that provisions self-hosted GitHub Actions runners on demand through pluggable providers such as LXD, OpenStack and AWS. A community-maintained runner provisioner with a plugin model for private clouds; it suits platform teams offering GitHub Actions runners on LXD, OpenStack or AWS.
Which CI systems does myshoes work with?
myshoes runs jobs for GitHub Actions, on Linux.
How does myshoes isolate jobs?
myshoes documents its isolation as: 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.
Is myshoes open source?
Yes (MIT). It can be self-hosted.
How much does myshoes 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 myshoes?
An admin runs the myshoes daemon with a MySQL database, a GitHub App and a provider plugin. Users install the GitHub App and register a repository or organization as a target through the REST API.
How many jobs can run at once on myshoes?
MAX_CONNECTIONS_TO_BACKEND caps connections to the provider (default 50).
What are the alternatives to myshoes?

Sources

  1. github.com/whywaita/myshoes
  2. github.com/whywaita/myshoes/releases
  3. github.com/whywaita/myshoes/blob/master/LICENSE
  4. github.com/whywaita/myshoes/blob/master/docs/01_01_for_admin_setup.md
  5. github.com/whywaita/myshoes/blob/master/docs/02_01_for_user_setup.md
  6. github.com/whywaita/myshoes/blob/master/docs/03_how-to-develop-shoes.md
  7. github.com/whywaita/myshoes-providers

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