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.
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
| Attribute | Details |
|---|---|
| CI systems | GitHub Actions |
| Operating systems | Linux |
| Architectures | Not documented |
| Deployment | Open-source project |
| Where it can run | LXD, OpenStack, AWS |
| Isolation | 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 |
| Fresh environment per job | Not documented |
| Hardware | Not documented |
| Performance (vendor claim) | Not documented |
| Runner sizes | Nine named resource types from nano to 4xlarge, which each provider maps to its own machine specs |
| Caching | Not documented |
| Docker layer caching | Not documented |
| GPU | The README lists special hardware such as GPUs and FPGAs as a reason to use your own provider, without setup details. |
| Concurrency | MAX_CONNECTIONS_TO_BACKEND caps connections to the provider (default 50) |
| Job limits | Not documented |
| Static IPs | Not documented |
| SSH into running jobs | Not documented |
| Observability | Optional Docker Hub rate-limit metrics |
| Setup | 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. |
| Example label | Not documented |
| 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 (MIT) |
| Company headquarters | Not 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
| Runner | CI systems | Runs on | Deployment | Isolation | Price | Largest runner | Docker layer cache | GPU | Open source | Company HQ |
|---|---|---|---|---|---|---|---|---|---|---|
| myshoes | GitHub Actions | Linux | Self-hosted | Depends on provider | Free software + your infrastructure | Set by your infrastructure | Not documented | Not documented | Yes | Not documented |
| 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 |
| Fireactions | GitHub Actions | Linux, x64, arm64 | Self-hosted | Firecracker microVM | Free software + your infrastructure | Set by your infrastructure | Not documented | No | Yes | Lithuania |
| 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 |
| 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 |
Head-to-head: Fireactions vs myshoes · GARM (GitHub Actions Runner Manager) vs myshoes
Frequently asked questions
What is myshoes?
Which CI systems does myshoes work with?
How does myshoes isolate jobs?
Is myshoes open source?
How much does myshoes cost?
How do you set up myshoes?
How many jobs can run at once on myshoes?
What are the alternatives to myshoes?
Sources
- github.com/whywaita/myshoes
- github.com/whywaita/myshoes/releases
- github.com/whywaita/myshoes/blob/master/LICENSE
- github.com/whywaita/myshoes/blob/master/docs/01_01_for_admin_setup.md
- github.com/whywaita/myshoes/blob/master/docs/02_01_for_user_setup.md
- github.com/whywaita/myshoes/blob/master/docs/03_how-to-develop-shoes.md
- 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/