> ## Documentation Index
> Fetch the complete documentation index at: https://docs.darkbloom.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# CI on Darkbloom runners

> Run a public repository's GitHub Actions jobs on Darkbloom's Linux and macOS runners, with fallback to your own runners and billing from your Darkbloom balance.

Darkbloom Sandboxes runs your public repository's GitHub Actions jobs in
Linux and macOS virtual machines on Apple silicon Macs, paid from your
Darkbloom balance. A routing workflow sends each group of jobs (a *lane*) to
Darkbloom when it has room for them and to your usual runners otherwise, so a
run never waits on Darkbloom.

> [!NOTE]
>
> Access is by invitation. Ask your Darkbloom contact about onboarding,
> approved repositories and the hosts your jobs need to reach.

## Who it is for

Use Darkbloom runners for CI checks that fit the routing rules: builds and
tests on Linux and macOS, including Xcode and Metal work. Release, publishing
and deployment jobs stay on your own runners.

The route workflow asks Darkbloom whether it can take each lane of a run. If
Darkbloom is off, unreachable, slow or says no, every lane keeps its fallback
label and the run continues on your usual runners. A lane that Darkbloom
accepts runs on a Darkbloom runner; if Darkbloom then cannot start its jobs,
they wait on GitHub until you cancel and re-run it (see
[troubleshooting](https://docs.darkbloom.dev/ci/troubleshooting.md)).

## Public repositories only

Darkbloom runs public repositories only. Private repositories show *Private*
in the console and cannot be requested.

Your jobs run on Macs that other people own. Darkbloom checks at every job
that the repository is public and refuses private ones, so nothing a Mac sees
is secret: the code is public, the job's token is read-only, and routed jobs
cannot hold secrets. See [security](https://docs.darkbloom.dev/ci/security.md) for what the Mac's owner can
see and what Darkbloom keeps.

## Linux and macOS

| Profile | `runs-on` on Darkbloom | Runner classes |
| - | - | - |
| `linux_arm64` | `[self-hosted, linux, ARM64, darkbloom-linux-arm64]` | `linux-arm64-4cpu-16gb` (default), `linux-arm64-8cpu-32gb` |
| `macos_arm64` | `[self-hosted, macOS, ARM64, darkbloom-macos-arm64]` | `macos-arm64-8cpu-16gb`, `macos-arm64-12cpu-32gb` |

Your approval sets each profile's size, and so its runner class. See
[runner images](https://docs.darkbloom.dev/ci/runner-images.md) for the operating systems and tools each
class provides.

## How a run is routed

1. A `route` job at the start of the run asks Darkbloom which lanes it can
   take and reserves capacity for their jobs.
2. Each routed job takes its `runs-on` from the route job's answer: Darkbloom's
   runner labels, or the lane's fallback label.
3. A lane that was routed can only run on a Darkbloom runner. The optional
   watchdog workflow rescues a run whose routed jobs never get one.

Lanes, labels and the caller workflow are in
[route workflows](https://docs.darkbloom.dev/ci/route-workflows.md).

## Billing

Jobs are paid from your Darkbloom balance, the same balance Darkbloom
inference uses. A job holds funds when it starts and settles to its billable
time at the rate in effect when it started; the rest of the hold is released.
Rates are per minute of each runner class and billed per second, as of November
2026; the [CI pricing page](https://docs.darkbloom.dev/ci/pricing.md) lists them, and the
live rates are in the sandbox console under **Billing → Rates**.

A monthly cap and a concurrency limit apply per installation. Lanes that
would not fit the monthly cap fall back to your runners. See
[limits and billing](https://docs.darkbloom.dev/ci/limits-and-billing.md).

## Next steps

> [card] [Quickstart](https://docs.darkbloom.dev/ci/quickstart.md)
>
> Sign in, install the GitHub App, route a workflow, and watch the job run.

> [card] [Route workflows](https://docs.darkbloom.dev/ci/route-workflows.md)
>
> Copy the route workflow, declare lanes, and keep jobs on their fallback.

> [card] [Runner images](https://docs.darkbloom.dev/ci/runner-images.md)
>
> What is installed on Linux and macOS runners, and how to add tools.

> [card] [Limits and billing](https://docs.darkbloom.dev/ci/limits-and-billing.md)
>
> Concurrency, spend caps, holds, and what a finished job costs.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.