Title: Blacksmith vs GitHub Actions runners vs your own machines URL: https://codemany.com/articles/blacksmith-vs-github-actions Description: Blacksmith vs GitHub Actions runners vs your own Mac or Linux box: compare where jobs run, macOS support, pricing model and setup in one honest table. All pages as Markdown: https://codemany.com/llms.txt --- [Home](https://codemany.com/) › [Articles](https://codemany.com/articles) # Blacksmith vs GitHub-hosted vs your own machines Blacksmith vs GitHub Actions is not a choice between two CI systems: Blacksmith runs your GitHub Actions jobs on its own cloud machines instead of GitHub's. A third option is to run those same jobs on Mac or Linux machines you own. ## The three ways to run a GitHub Actions job Your workflow files stay the same in all three. GitHub still schedules the jobs and shows the logs. What changes is the `runs-on` line, and whose computer does the work. - **GitHub-hosted runners.** GitHub's machines. The default. - **A hosted runner service,** like Blacksmith. Another company's machines. - **Your own machines.** Self-hosted runners, by hand or with a tool like Codemany. ## What Blacksmith is Blacksmith runs GitHub Actions jobs on Blacksmith's cloud. You install its GitHub app, then point jobs at its runners with labels like `blacksmith-2vcpu-ubuntu-2404`. Its docs show Linux, macOS and Windows labels. Per its quickstart, it works for GitHub organizations, not personal repos. Blacksmith has real strengths. Its docs describe: - a cache next to its runners, which `actions/cache` and similar actions use instead of GitHub's; - Docker layer caching, so image builds reuse layers; - tools to see what went wrong: run history, logs, SSH access and test analytics. You don't own or care for any machines. Blacksmith runners are billed per minute, with free minutes each month. Rates change, so check [Blacksmith's docs](https://docs.blacksmith.sh/) and pricing page for today's numbers. ## What GitHub-hosted runners give you GitHub-hosted runners need no setup. Write `runs-on: ubuntu-latest` and go. Each job gets a clean machine that is thrown away after. - Linux, Windows and macOS, on x86 and arm64. - Free and unlimited standard runners on public repos. - On private repos, some free minutes each month, then a price per minute. macOS minutes cost the most. As of November 2026, GitHub lists $0.006 a minute for 2-core Linux and $0.062 a minute for macOS. See [GitHub Actions cost per minute](https://codemany.com/docs/guides/actions-cost) for a worked bill. ## Running jobs on machines you own The third way uses hardware you already have. The Mac on your desk, a Mac mini in a closet or a Linux server can take jobs. Codemany sets this up. Install the app, sign in with GitHub, and change one line: ``` jobs: build: runs-on: [self-hosted, codemany] steps: - uses: actions/checkout@v4 - run: make test ``` Each job gets a fresh, single-use runner. Codemany updates itself and cleans up disk. Your code stays on your machines. Know the tradeoffs, too: - Macs need Apple silicon and macOS 14 or later. Intel Macs and Windows are not supported. - On a Mac, jobs run as your user. It is not a sandbox, so run only code you trust. - On Linux, jobs run on the host by default. You can turn on a fresh VM per job with `codemany isolation vm` if the machine has KVM. - You keep the machine on, powered and online. On speed, our nightly [benchmarks](https://codemany.com/benchmarks) show jobs on Codemany running 1.5×–4.3× faster on private code than on GitHub's 2-core runners. Codemany can also create a machine in your own Google Cloud, Hetzner or DigitalOcean account. Your cloud bills you for that machine, and Codemany never sees the bill. ## Side-by-side table | | GitHub-hosted | Blacksmith | Your machines (Codemany) | | --- | --- | --- | --- | | Where jobs run | GitHub's cloud | Blacksmith's cloud | Your Macs and Linux machines | | macOS | Yes | Yes | Yes, Apple silicon | | Linux | x86 and arm64 | Yes | x86-64 and arm64 | | Windows | Yes | Yes | No | | Pricing model | Per minute, after free minutes | Per minute, with free minutes | $20/month for 2 machines, $10 each extra | | Setup | None | Install a GitHub app, change `runs-on` | Install the app, change `runs-on` | | Who runs the hardware | GitHub | Blacksmith | You | | Code leaves your network | Yes | Yes | No | Last checked 2026-11-11 from each one's public docs. More services are in [Codemany compared](https://codemany.com/docs/compare). Each option has costs that the table can't show. Hosted runners bill by the minute. Your own machines cost a bit of your time to keep on and online. ## Which fits your team - **Pick GitHub-hosted** if your jobs fit in your free minutes, or you need Windows. - **Pick Blacksmith** if you want hosted runners with no hardware to own, and value its caching and debugging tools. - **Pick your own machines** if you have Macs or Linux boxes to spare, build iOS apps, or want a flat bill that long builds don't raise. Many teams mix them. Jobs left on `ubuntu-latest` keep running on GitHub, so you can move one workflow at a time. For more options, read [GitHub Actions alternatives](https://codemany.com/docs/guides/github-actions-alternatives). The best test is your own workflow. Run one real job on each option for a week. Compare how long it takes, how often it fails and what it costs. ## Questions ### Is Blacksmith a GitHub Actions replacement? No. It runs GitHub Actions jobs on its own cloud machines, and you keep your workflows. ### Does Codemany run macOS jobs? Yes, on your own Apple silicon Macs. ### How is Codemany priced? $20 a month for 2 machines, after a 14-day trial with no card. ## Related Read next: [Codemany compared](https://codemany.com/docs/compare), [GitHub Actions alternatives](https://codemany.com/docs/guides/github-actions-alternatives), the [benchmarks](https://codemany.com/benchmarks), [pricing](https://codemany.com/pricing) and [GitHub Actions costs](https://codemany.com/docs/guides/actions-cost). [Start a 14-day trial](https://codemany.com/pricing) No card needed. $20 a month for 2 machines after that.