FlyCI macOS Runners (discontinued)
FlyCI announced on August 14, 2024 that it would discontinue FlyCI macOS runners effective September 30, 2024, after which they would no longer be available or supported, and that it would focus on FlyCI Wingman. Closest alternatives: GitHub-hosted runners, GetMac, Bitrise Build Hub.
Status: FlyCI announced on August 14, 2024 that it would discontinue FlyCI macOS runners effective September 30, 2024, after which they would no longer be available or supported, and that it would focus on FlyCI Wingman.
Overview
FlyCI macOS Runners was a managed runner service for GitHub Actions. Teams installed the FlyCI GitHub App and pointed runs-on at a FlyCI label such as flyci-macos-14-m2 to run jobs on FlyCI’s Apple silicon machines instead of GitHub-hosted macOS runners. In its own words, FlyCI started with Linux runners and later pivoted to macOS runners before adding an AI assistant named FlyCI Wingman.
On August 14, 2024 FlyCI announced that it would discontinue the macOS runners effective September 30, 2024 and put its development effort into FlyCI Wingman, a tool that proposes fixes for failing GitHub Actions workflows. The announcement told customers to migrate, giving GitHub-hosted macos-14 runners as an example. The FlyCI GitHub App listing now describes only Wingman. This record is kept so that older references to FlyCI runners can be resolved.
Notable
- August 14, 2024: FlyCI announced it would discontinue FlyCI macOS runners and focus on FlyCI Wingman
- September 30, 2024: effective date of the discontinuation given in the announcement
How FlyCI macOS Runners compares
| Runner | CI systems | Runs on | Deployment | Isolation | Price | Largest runner | Docker layer cache | GPU | Open source | Company HQ |
|---|---|---|---|---|---|---|---|---|---|---|
| FlyCI macOS Runners | GitHub Actions | macOS, arm64 | Vendor-hosted | Not documented | Not documented | Not documented | Not documented | Not documented | Not documented | Not documented |
| GitHub-hosted runners | GitHub Actions | Linux, macOS, Windows, x64, arm64 | Platform-hosted | Fresh VM | $0.006/min | 96 vCPU / 384 GB | Not documented | Yes | No | United States |
| GetMac | GitHub Actions, GitLab CI, Buildkite | macOS, arm64 | Vendor-hosted | macOS VM | $0.012/min (macOS M4, Developer plan) | Not documented | Not documented | Not documented | No | Lithuania |
| Bitrise Build Hub | GitHub Actions | macOS, Linux, arm64, x64 | Vendor-hosted | Virtual machine | $0.00625/min | 16 vCPU / 64 GB | Not documented | Not documented | No | Not documented |
| Namespace | GitHub Actions, Buildkite | Linux, macOS, Windows, x64, arm64 | Vendor-hosted | Virtual machine | $0.002/min prepaid, $0.003/min overage (2 vCPU / 4 GB) | 64 vCPU / 512 GB | Yes | Not documented | No | Not documented |
| WarpBuild | GitHub Actions | Linux, macOS, Windows, x64, arm64 | Vendor-hosted | Ephemeral VM | $0.004/min | 32 vCPU / 128 GB | Yes | Not documented | No | Not documented |
Frequently asked questions
What is FlyCI macOS Runners?
Which CI systems does FlyCI macOS Runners work with?
How does FlyCI macOS Runners isolate jobs?
Is FlyCI macOS Runners open source?
How much does FlyCI macOS Runners cost?
What are the alternatives to FlyCI macOS Runners?
Sources
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). FlyCI macOS Runners (discontinued). cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/runners/flyci/