Loading…

.github/workflows/ci.yml

-runs-on: ubuntu-latest+runs-on: hive

Run GitHub Actions on the Macs your team already has.

HiveWorker is runner software for GitHub Actions. That one line sends a job to a throwaway VM on one of your own developers' machines. The rest of the workflow stays as it is.

Install the GitHub App Read the docs

Early access. HiveWorker is not generally available yet. These pages describe how it is designed to work.

Cheaper

A 2 vCPU minute costs $0.001 in a private pool. The same Linux arm64 minute is $0.005 on a GitHub-hosted runner and $0.0025 on Blacksmith. When your own machines run the job, most of that payment comes back to your organization and the net cost is $0.00025. Work out your month

Faster

Jobs land on Apple Silicon your team already owns. Each machine keeps one VM booted and waiting, so a job starts on a runner that is already up instead of waiting for one to be provisioned.

Simple

One GitHub App install for the organization. One sign-in for each developer. One changed line in a workflow. No invite codes, no subscription and no platform fee.

Three steps, and the third is the diff above.

1
Install the GitHub App
An organization owner installs HiveWorker on the organization. That creates the runner labels, a private pool, and a wallet holding a trial grant.
- hive
- hive-4cpu
- hive-8cpu
2
Developers add their Macs
Each developer installs the daemon and signs in with GitHub. Belonging to your GitHub organization is what lets a machine join the pool.
Terminal
```
curl -fsSL https://get.hiveworkr.thecomputerplumbers.com/install.sh | sh
```
The daemon is not released yet. Requirements and status
3
Change one line
Jobs with a hive label run on your pool. Jobs without one keep running where they run today.
```
-runs-on: ubuntu-latest+runs-on: hive
```

A job never touches the machine it runs on.

Every job gets its own hardware-virtualized VM, which is destroyed when the job ends. The VM talks to GitHub directly. HiveWorker assigns the job and is not in its data path.

The GitHub App has no access to code, contents or secrets.
Only members of your GitHub organization can add machines.
The daemon gives way when the developer needs their Mac back.

How isolation and trust work

A developer's Mac

Throwaway Linux VM

GitHub's runner, one job, then destroyed

HiveWorker daemon

Runs as your user, not root. No inbound ports.

The Mac's files and keychain stay outside the VM.

GitHub

The job, its logs and its artifacts

HiveWorker coordinator

Presence and job assignment. No job data

Try it on one workflow.

Every new organization starts with a trial grant, and switching back is the same one line. HiveWorker is in early access, so installs are not open to everyone yet.

Install the GitHub App See pricing

Loading…

.github/workflows/ci.yml

-runs-on: ubuntu-latest+runs-on: hive

Run GitHub Actions on the Macs your team already has.

HiveWorker is runner software for GitHub Actions. That one line sends a job to a throwaway VM on one of your own developers' machines. The rest of the workflow stays as it is.

Install the GitHub App Read the docs

Early access. HiveWorker is not generally available yet. These pages describe how it is designed to work.

Cheaper

Faster

Jobs land on Apple Silicon your team already owns. Each machine keeps one VM booted and waiting, so a job starts on a runner that is already up instead of waiting for one to be provisioned.

Simple

One GitHub App install for the organization. One sign-in for each developer. One changed line in a workflow. No invite codes, no subscription and no platform fee.

Three steps, and the third is the diff above.

1
Install the GitHub App
An organization owner installs HiveWorker on the organization. That creates the runner labels, a private pool, and a wallet holding a trial grant.
- hive
- hive-4cpu
- hive-8cpu
2
Developers add their Macs
Each developer installs the daemon and signs in with GitHub. Belonging to your GitHub organization is what lets a machine join the pool.
Terminal
```
curl -fsSL https://get.hiveworkr.thecomputerplumbers.com/install.sh | sh
```
The daemon is not released yet. Requirements and status
3
Change one line
Jobs with a hive label run on your pool. Jobs without one keep running where they run today.
```
-runs-on: ubuntu-latest+runs-on: hive
```

A job never touches the machine it runs on.

Every job gets its own hardware-virtualized VM, which is destroyed when the job ends. The VM talks to GitHub directly. HiveWorker assigns the job and is not in its data path.

The GitHub App has no access to code, contents or secrets.
Only members of your GitHub organization can add machines.
The daemon gives way when the developer needs their Mac back.

How isolation and trust work

A developer's Mac

Throwaway Linux VM

GitHub's runner, one job, then destroyed

HiveWorker daemon

Runs as your user, not root. No inbound ports.

The Mac's files and keychain stay outside the VM.

GitHub

The job, its logs and its artifacts

HiveWorker coordinator

Presence and job assignment. No job data

Try it on one workflow.

Every new organization starts with a trial grant, and switching back is the same one line. HiveWorker is in early access, so installs are not open to everyone yet.

Install the GitHub App See pricing

Run GitHub Actions on the Macs your team already has.

Cheaper

Faster

Simple

Three steps, and the third is the diff above.

Install the GitHub App

Developers add their Macs

Change one line

A job never touches the machine it runs on.

Try it on one workflow.

Run GitHub Actions on the Macs your team already has.

Cheaper

Faster

Simple

Three steps, and the third is the diff above.

Install the GitHub App

Developers add their Macs

Change one line

A job never touches the machine it runs on.

Try it on one workflow.