Self-Hosted macOS Apple Silicon GitHub Actions Runners
Short answer: Strict turns any Apple Silicon Mac (macOS 15+) into a bare-metal GitHub Actions runner via a user-level launchd service—giving workflows 10+ native cores, warm NVMe storage, 7-tier cleanup, and zero per-minute fees.
Turn spare M1, M2, M3, or M4 Macs into self-healing, zero-sudo GitHub Actions runners at $0/min.
Drop-in workflow YAML & zero-sudo enrollment
Enroll your host with strict add-runner and route jobs directly via GitHub's native runs-on labels:
jobs:
build:
runs-on: [self-hosted, macOS, ARM64]
steps:
- uses: actions/checkout@v4
curl -fsSL https://strict.ai/install.sh | sh
strict add-runner owner/repo --labels self-hosted,macOS,ARM64
How Strict keeps macOS Apple Silicon runners healthy
| Subsystem | How it applies to macOS Apple Silicon |
|---|---|
| Disk Cleanup | Automatic Tiers 1–4 prune runner _diag/_temp files, npm/bun/cargo/brew caches, git-ignored scratch dirs, and stale Xcode DerivedData whenever free space falls under lowGiB. Opt-in Tier 6 handles APFS snapshots and DeviceSupport. |
| Preflight Doctor | strict doctor verifies dns-github, disk-headroom, apfs-unallocated, macos-sleep (pmset), macos-autologin, runner-hooks, xcode-license, and tailscale-health without root access. |
| Tracked Toolchains | xcode, swift, node, bun, python, rust, go, gh, ruby, java, runner |
| Cache & Balancing | Local NVMe keeps DerivedData and SPM packages warm across runs, while Tailnet Build Cache shares artifacts over Tailscale. computeFleetDirective drains noisy slots before RAM or CPU saturates. |
When Strict fits vs. when hosted runners win
Use Strict for macOS Apple Silicon when
- Full 10–16 bare-metal Apple Silicon cores instead of 3–6 shared cloud vCPUs
- Zero $0.062–$0.102/min metered macOS runner bills on private repositories
- Zero-sudo launchd setup with sleep/autologin drift monitoring built in
Use cloud-hosted runners when
- Public open-source repos accepting untrusted external fork pull requests
- Rare quarterly bursts where you only use a few hundred macOS minutes total
Frequently asked questions
Which Macs and macOS versions does Strict support?
Strict targets Apple Silicon Macs running macOS 15 or newer for its signed desktop app, and runs its Python host agent as a standard launchd user agent without requiring sudo.
How does Strict keep a spare Mac from going to sleep mid-build?
strict doctor runs the macos-sleep and macos-autologin checks on every preflight cycle, flagging pmset sleep timeouts or disabled autologin before builds silently hang.
Do I lose existing workflow steps when switching runs-on?
No. Strict registers GitHub's official actions/runner directly with your repository or organization, so checkout, matrices, artifacts, and secrets keep working untouched.
Try Strict on one spare Mac in under two minutes
Signed Apple Silicon app or single-line CLI · Zero accounts required