GitHub Actions runners on your own Mac mini.
minitart runs every job in a fresh virtual machine and deletes it when the job ends. A job reaches the internet and nothing of yours: not your files, not your keychain, not your home network.
Early. Built for one Mac mini and a handful of private repos; read it before you trust it.
How it works
-
A workflow asks for it
runs-on: minitart-linuxorminitart-macos. Every other job stays where it was. -
The job gets a new VM
minitart clones an image in under a second, boots it and registers a runner that exists for that one job.
-
The VM is deleted
When the job ends, so does everything it wrote, installed or left running. The next job starts from the image again.
What keeps it safe
- The same isolation hosted runners have
- One VM per job, on Apple's hypervisor, driven by Tart. No folder is shared with a VM.
- The network is an allowlist
- A VM can send to public internet addresses and nowhere else. Your router, your NAS and your tailnet are out of reach without being listed, and so is the next thing you add.
- GitHub holds the list of repos
- minitart is a GitHub App you create in one click and install on the repos you choose. It cannot register a runner anywhere else. Public repos are skipped.
- A job never sees a key
- The App's key stays on the Mac. A VM holds the single-use config of its own runner, already spent.
- You can check
-
minitart selftestboots a VM and tries to reach your router and your Mac from inside it. - Small enough to read
- A manager and a page. TypeScript that Node runs as it is, with no runtime dependencies.
What it does not cover is written down too: the security model.
What it is not
It is not for a team with a fleet of Macs. It does not fall back to hosted runners when the Mac is off, it runs arm64 only, and it keeps no caches between jobs. Switching a job back to GitHub's runners is a one-word change.