Skip to content

Hosted providers

Routing jobs to Blacksmith, Depot, Namespace, WarpBuild, Ubicloud, Boat, RunsOn and seven more runner clouds.

Hosted providers run GitHub Actions jobs on their own machines, under your account with them. Route jobs to any of these when your own machines are busy, or ahead of GitHub-hosted runners.

  1. Install the provider’s GitHub App on the organization and set up your account with them. A routed job only gets one of the provider’s labels. The provider’s App runs it and bills you.
  2. Add the provider to your workspace’s runner order on the Router page.
  3. Name one of its labels in the relay input of the same name:
relay-test:
uses: relayrunner/actions/.github/workflows/relay.yml@v1
with:
machine: self-hosted
depot: depot-ubuntu-24.04
github: ubuntu-latest

Each job has its own relay, so each job picks its own size, such as blacksmith-2vcpu-ubuntu-2404 for a lint job and blacksmith-4vcpu-ubuntu-2404 for tests. Or write auto, such as depot: auto, and pick each job’s size on the Router page instead (see Auto sizes). relayrunner init keeps a job’s existing provider label as its fallback, so a job already on a hosted provider stays there whenever no machine is free.

A provider’s step always takes a job that names one of its labels. There’s no way to see a provider’s capacity, so steps below it only run for jobs that don’t name one. A common order is your machines, then a hosted provider, then GitHub-hosted.

Unlike machines, hosted providers also run public repos’ jobs, except Boat, which refuses them unless you allow them in Boat, and BerryBox, which runs private repos only. RelayRunner skips both for public repos. StarSling, Monk CI, Latchkey, BerryBox and Lizard only run organizations’ repos, so RelayRunner skips them for a personal account’s jobs.

Provider Relay input
Blacksmith blacksmith
Depot depot
Namespace namespace
WarpBuild warpbuild
Ubicloud ubicloud
Boat boat
RunsOn runs-on
StarSling starsling
Monk CI monkci
Runloft runloft
Latchkey latchkey
BerryBox berrybox
Celesto celesto
InstaBox instabox
Lizard lizard
Blacksmith

Hosted runners for GitHub Actions.

Labels
blacksmith-*
Example
runs-on: blacksmith-4vcpu-ubuntu-2404
List price
$0.008/min
Links
Depot

Hosted runners for GitHub Actions.

Labels
depot-*
Example
runs-on: depot-ubuntu-24.04
List price
$0.006/min
Links
Namespace

Hosted runners for GitHub Actions, sized by runner profile.

Labels
namespace-profile-*, nscloud-*
Example
runs-on: namespace-profile-default
Links
WarpBuild

Hosted runners for GitHub Actions.

Labels
warp-*
Example
runs-on: warp-ubuntu-latest-x64-2x
List price
$0.004/min
Links
Ubicloud

Hosted runners for GitHub Actions.

Labels
ubicloud, ubicloud-*
Example
runs-on: ubicloud-standard-2
List price
$0.00125/min
Links
Boat

Hosted Linux runners for GitHub Actions, billed per second.

Labels
boat, boat-*
Example
runs-on: boat
List price
$0.0006/min
Links

Boat runs Linux x64 only. Its CI needs Boat’s $20 plan or higher, and boat-xlarge its $100 plan, so auto picks Boat sizes up to boat-large. Boat caps job starts per minute, hour and day; past the hour or day cap it pauses a job until someone re-runs it. Starts past the plan’s included ones cost extra, which spend limits don’t count.

RunsOn

Runners started in your own AWS account.

Labels
runs-on=<run id>/runner=<type>
Example
runs-on: runs-on=${{ github.run_id }}/runner=2cpu-linux-x64
Links

RunsOn’s label carries the run’s id, so write it as an expression: runs-on: runs-on=${{ github.run_id }}/runner=2cpu-linux-x64.

StarSling

Hosted Linux runners for GitHub Actions, with GPU runners on request.

Labels
starsling-ubuntu-<version>-<vcpus>
Example
runs-on: starsling-ubuntu-24.04-2
List price
$0.004/min
Links

StarSling’s label with no size, starsling-ubuntu-24.04, is 4 vCPU. Add -2 for 2 vCPU.

Monk CI

Hosted Linux runners for GitHub Actions.

Labels
monkci-ubuntu-24.04-<vcpus>
Example
runs-on: monkci-ubuntu-24.04-2
List price
$0.004/min
Links

monkci-ubuntu-latest is Monk CI’s largest runner, 32 vCPU. Name a size, such as monkci-ubuntu-24.04-4, for anything smaller.

Runloft

Hosted runners for GitHub Actions, billed per second.

Labels
runloft-*
Example
runs-on: runloft-ubuntu-24.04
List price
$0.003/min
Links

Runloft runs 2 vCPU Linux x64 until it turns on bigger sizes, Arm, Windows or macOS for your account, so auto always picks runloft-ubuntu-24.04.

Latchkey

Hosted Linux runners for GitHub Actions.

Labels
latchkey-small, -medium, -large, -xlarge
Example
runs-on: latchkey-small
List price
$0.0025/min
Links

Latchkey’s $5 plan covers one repo. At its spend limit, Latchkey holds queued jobs.

BerryBox

Hosted Linux runners for GitHub Actions, billed per second.

Labels
berrybox-<vcpus>vcpu-ubuntu-2404
Example
runs-on: berrybox-2vcpu-ubuntu-2404
List price
$0.002/min
Links

Turn on each BerryBox size you name in its team settings, and keep enough credit for a job’s maximum runtime: BerryBox holds that much before it starts a job.

Celesto

Linux runners for GitHub Actions on Celesto's sandboxes.

Labels
celesto, celesto-*
Example
runs-on: celesto-standard
List price
$0.0005/min
Links

Celesto’s trial runs celesto-micro (1 vCPU) only, so add credit before routing auto jobs there: auto starts at celesto-standard (2 vCPU).

InstaBox

Linux runners for GitHub Actions on InstaBox's sandboxes.

Labels
instabox-*
Example
runs-on: instabox-medium
List price
$0.00057/min
Links

InstaBox’s plan decides which sizes run, and the Free plan runs instabox-medium (4 vCPU) only. auto answers a 2 vCPU job with instabox-medium too.

A label the account can’t run sits queued on GitHub. After a few jobs on it go unanswered, the Router skips that label until a trial job starts.

Lizard

Linux runners for GitHub Actions on Lizard's Firecracker VMs, billed per second.

Labels
lizard-small, -medium, -large-ubuntu-2404
Example
runs-on: lizard-medium-ubuntu-2404
List price
$0.00054/min
Links

Lizard runs Linux x64 in three sizes: lizard-small-ubuntu-2404 (2 vCPU), lizard-medium-ubuntu-2404 (4) and lizard-large-ubuntu-2404 (8). Its trial runs a set number of jobs of each size and then skips that size until you start Pro. On Pro, usage past the included amount is billed as you go, and jobs past 5 at once (20 on Pro 5x and Pro 20x) wait in Lizard’s queue.

  • Provider-only actions in a job, such as Blacksmith’s cache actions, won’t work on your machines or GitHub. init warns about Blacksmith’s.