Fireactions vs myshoes
Fireactions suits teams with their own Linux servers that want microVM isolation for GitHub Actions jobs without running Kubernetes. 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. Fireactions is an open-source project you run yourself for GitHub Actions; myshoes is an open-source project you run yourself for GitHub Actions.
Key differences between Fireactions and myshoes
- Isolation: Fireactions: Firecracker microVM. myshoes: Depends on provider.
- Licence: Fireactions 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.
Fireactions vs myshoes at a glance
| Attribute | Fireactions | myshoes |
|---|---|---|
| What it is | Orchestrator that runs self-hosted GitHub Actions runners in ephemeral Firecracker microVMs on your own Linux hosts. | Daemon that provisions self-hosted GitHub Actions runners on demand through pluggable providers such as LXD, OpenStack and AWS. |
| Type | Open-source project | Open-source project |
| CI systems | GitHub Actions | GitHub Actions |
| Operating systems | Linux | Linux |
| Architectures | x64, arm64 | Not documented |
| Isolation | Each runner is a Firecracker microVM that is created from scratch and destroyed after the job, with no state kept between jobs | 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 | Yes | Not documented |
| Hardware | Any Linux host with KVM on x86_64 or aarch64: a bare-metal server or a VM with nested virtualization, plus a dedicated block device for containerd image storage | Not documented |
| Performance (vendor claim) | The Fireactions docs cite a GitHub runner startup time of about 20 seconds (vendor claim) | Not documented |
| Runner sizes | vCPU count and memory are set per pool in the Firecracker machine configuration | Nine named resource types from nano to 4xlarge, which each provider maps to its own machine specs |
| Caching | A tutorial describes running a Docker registry mirror (pull-through cache) on the host for Docker Hub images. | Not documented |
| Docker layer caching | Not documented | Not documented |
| GPU | The FAQ states that Fireactions does not support GPU workloads, because Firecracker has no GPU support. | The README lists special hardware such as GPUs and FPGAs as a reason to use your own provider, without setup details. |
| Concurrency | Each pool keeps a configured number of runner replicas | MAX_CONNECTIONS_TO_BACKEND caps connections to the provider (default 50) |
| Static IPs | Not documented | Not documented |
| SSH into running jobs | Yes | Not documented |
| Pricing | Free and open source; you pay for the infrastructure it runs on. | Free and open source; you pay for the infrastructure it runs on. |
| Free tier | Not documented | Not documented |
| Open source | Yes (Apache-2.0) | Yes (MIT) |
| Self-host / your cloud | Yes / Yes | Yes / Yes |
| Compliance | Not documented | Not documented |
| Regions | Not documented | Not documented |
| Company headquarters | Vilnius, Lithuania | Not documented |
| Good fit for | Teams with their own Linux servers that want microVM isolation for GitHub Actions jobs without running Kubernetes | Platform 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 Fireactions
- You want each job in its own Firecracker microVM that is destroyed afterwards
- You have bare-metal Linux servers, or VMs with nested virtualization, on x86_64 or arm64
- You prefer a standalone binary configured with one YAML file to a Kubernetes operator
- You want to build runner images with ordinary Docker tooling
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
- Fireactions: Only GitHub organisation accounts are supported
- Fireactions: GPU workloads are not supported
- 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 Fireactions profile and myshoes profile, or the complete comparison.
More comparisons
Frequently asked questions
Is Fireactions or myshoes better?
What is the difference between Fireactions and myshoes?
Which is open source, Fireactions or myshoes?
How do Fireactions and myshoes isolate jobs?
How does Fireactions pricing compare with myshoes?
Is Fireactions or myshoes faster?
Do Fireactions and myshoes offer GPU runners?
Where do Fireactions and myshoes runners run?
Sources
- github.com/hostinger/fireactions
- github.com/hostinger/fireactions/releases
- github.com/hostinger/fireactions/blob/main/LICENSE
- github.com/hostinger/fireactions/blob/main/ADOPTERS.md
- 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
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). Fireactions vs myshoes. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/fireactions-vs-myshoes/