Hives

A hive is the set of machines that can run an organization's jobs. Installing the GitHub App creates one hive for the organization.

Who can add machines

Any member of the GitHub organization that installed the App can add a machine by installing the daemon and signing in with GitHub. There are no invite codes. Organization admins can narrow this to specific GitHub teams.

GitHub is the source of truth for membership. When a person is removed from the organization, their machines are revoked and stop receiving jobs.

When no machine is free

A job that asks for a hive label directly stays queued at GitHub until a machine of the right size is free. Hive Runner does not move a queued job to another runner.

To avoid the wait, check for a free machine before the job is queued and use the runner you have now when there is none. Routing and fallback shows the workflow, and it is the setup we recommend.

When the wallet is empty

Hive Runner stops taking new jobs for the organization. They wait in GitHub's queue and the dashboard says why. Jobs already running are not interrupted.

The public hive

Your own hive is the product today. A public hive, where jobs can overflow to machines outside your organization, comes later. It will be opt-in per repository and limited to jobs that use no secrets. See Security for the trust model.