# Self-hosted alternative to GitHub-hosted macOS runners

kinhin runs GitHub Actions macOS jobs on an Apple Silicon Mac that you own. Like GitHub-hosted runners, each job gets a fresh
VM that is deleted when the job ends. The difference is where the Mac lives and who pays for it: kinhin is free and open
source under Apache-2.0, and the hardware, power and upkeep are yours.

## When kinhin fits

- You already have Apple Silicon Macs, or you are willing to buy one, and you run many macOS jobs. A busy Mac can cost less
  than per-minute macOS runner charges.
- You want jobs to run on your own network, with your own toolchains and caches. See [Toolchains](https://kinhin.dev/v0.0.1-beta-7/guide/toolchains.md).
- You need several jobs at once. kinhin runs a fleet on one Mac; see [How scaling works](https://kinhin.dev/v0.0.1-beta-7/guide/scaling.md).

## When GitHub-hosted runners fit better

- **You need Intel macOS.** kinhin needs an Apple Silicon Mac.
- **You do not want hardware.** Nothing to buy, power, update or repair.
- **Your jobs are rare.** A Mac that waits for work all day is wasted money.

## Other options

Several hosted macOS services exist, along with other self-hosted tools. The [comparison](https://kinhin.dev/v0.0.1-beta-7/guide/compare.md) covers them with
what each does well.

To start, follow [How to run GitHub Actions on a self-hosted Mac](https://kinhin.dev/v0.0.1-beta-7/how-to-run-github-actions-on-a-self-hosted-mac.md).

## Next steps

- [Quick start](https://kinhin.dev/v0.0.1-beta-7/guide/quick-start.md): From zero to a working fleet
- [Install](https://kinhin.dev/v0.0.1-beta-7/guide/install.md): Pinned versions, updates and uninstall
- [Forge support](https://kinhin.dev/v0.0.1-beta-7/guide/forges.md): What has been run against a real server
- [Why kinhin](https://kinhin.dev/v0.0.1-beta-7/guide/why-kinhin.md): Why most runners do one job at a time
