RelayRunner docs: Hosted providers Page: https://relayrunner.dev/docs/runners/hosted Markdown: https://relayrunner.dev/docs/runners/hosted.md All pages: https://relayrunner.dev/docs/llms.txt Other pages (Markdown): - Route GitHub Actions jobs to any runner: https://relayrunner.dev/docs/get-started/overview.md - How it works with GitHub Actions: https://relayrunner.dev/docs/get-started/github-actions.md - Quickstart: https://relayrunner.dev/docs/get-started/quickstart.md - Install the CLI: https://relayrunner.dev/docs/get-started/install.md - RelayRunner for Mac: https://relayrunner.dev/docs/get-started/mac-app.md - Set up with an agent: https://relayrunner.dev/docs/get-started/agents.md - Move your workflows over: https://relayrunner.dev/docs/get-started/move-over.md - Principles: https://relayrunner.dev/docs/concepts/principles.md - Routing: https://relayrunner.dev/docs/concepts/routing.md - Runner order: https://relayrunner.dev/docs/concepts/runner-order.md - Optimized checks: https://relayrunner.dev/docs/concepts/optimized-checks.md - Spend controls: https://relayrunner.dev/docs/guides/spend-controls.md - Providers: https://relayrunner.dev/docs/runners/providers.md - Your machines: https://relayrunner.dev/docs/runners/self-hosted.md - GitHub-hosted: https://relayrunner.dev/docs/runners/github.md - Hosted providers: https://relayrunner.dev/docs/runners/hosted.md (this page) - Runner labels: https://relayrunner.dev/docs/reference/labels.md - Add a provider: https://relayrunner.dev/docs/contribute/add-provider.md - Run CI on your laptop while you work: https://relayrunner.dev/docs/guides/laptop-ci.md - macOS and iOS builds on your Mac: https://relayrunner.dev/docs/guides/mac-builds.md - Share your team's machines: https://relayrunner.dev/docs/guides/team-machines.md - Keep up with coding agents: https://relayrunner.dev/docs/guides/agent-surge.md - Activity and history: https://relayrunner.dev/docs/dashboard/activity.md - Signals: https://relayrunner.dev/docs/dashboard/signals.md - Performance: https://relayrunner.dev/docs/dashboard/performance.md - Usage and savings: https://relayrunner.dev/docs/dashboard/usage.md - Telemetry: https://relayrunner.dev/docs/dashboard/telemetry.md - AI: https://relayrunner.dev/docs/dashboard/ai.md - CLI: https://relayrunner.dev/docs/reference/cli.md - relay.yml inputs: https://relayrunner.dev/docs/reference/relay-inputs.md - Repo config: https://relayrunner.dev/docs/reference/repo-config.md - MCP server: https://relayrunner.dev/docs/reference/mcp.md - RelayRunner API: https://relayrunner.dev/docs/reference/api.md - Workspaces and members: https://relayrunner.dev/docs/dashboard/workspaces.md - GitHub App: https://relayrunner.dev/docs/reference/github-app.md - Security: https://relayrunner.dev/docs/reference/security.md - Data and privacy: https://relayrunner.dev/docs/reference/privacy.md - Remove RelayRunner: https://relayrunner.dev/docs/dashboard/remove.md - Troubleshooting: https://relayrunner.dev/docs/reference/troubleshooting.md - Errors: https://relayrunner.dev/docs/reference/errors.md - FAQ: https://relayrunner.dev/docs/reference/faq.md - Feedback: https://relayrunner.dev/docs/contribute/feedback.md - Changelog: https://relayrunner.dev/docs/changelog.md - Agents can change your routing: https://relayrunner.dev/docs/changelog/agent-changes.md - Pick runner sizes on the dashboard: https://relayrunner.dev/docs/changelog/auto-runner-sizes.md - CLI changelog: https://relayrunner.dev/docs/changelog/cli.md - Send job logs to your tools or your own bucket: https://relayrunner.dev/docs/changelog/job-log-export.md - Mac app changelog: https://relayrunner.dev/docs/changelog/mac.md - RelayRunner for Mac: https://relayrunner.dev/docs/changelog/mac-app.md - CI traces in your observability tool: https://relayrunner.dev/docs/changelog/opentelemetry-traces.md - Platform changelog: https://relayrunner.dev/docs/changelog/platform.md - Retries, queueing and provider usage: https://relayrunner.dev/docs/changelog/retries-queueing-and-provider-usage.md - Route a repo from the dashboard: https://relayrunner.dev/docs/changelog/route-a-repo.md - Clearer run times and job sizes for members: https://relayrunner.dev/docs/changelog/run-times.md - Usual times, job history and the Mac queue: https://relayrunner.dev/docs/changelog/usual-times-and-mac-queue.md --- # 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. ## Set it up 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](/docs/concepts/runner-order) on the Router page. 3. Name one of its labels in the relay input of the same name: ```yaml 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](/docs/reference/relay-inputs#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. ## Where it sits in the order 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. ## The providers | 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 (as of November 2026) - Links: [Docs](https://docs.blacksmith.sh), [Dashboard](https://app.blacksmith.sh) **Depot**: Hosted runners for GitHub Actions. - Labels: `depot-*` - Example: `runs-on: depot-ubuntu-24.04` - List price: $0.006/min (as of November 2026) - Links: [Docs](https://depot.dev/docs/github-actions/overview), [Dashboard](https://depot.dev/orgs) **Namespace**: Hosted runners for GitHub Actions, sized by runner profile. - Labels: `namespace-profile-*, nscloud-*` - Example: `runs-on: namespace-profile-default` - Links: [Docs](https://namespace.so/docs), [Dashboard](https://cloud.namespace.so) **WarpBuild**: Hosted runners for GitHub Actions. - Labels: `warp-*` - Example: `runs-on: warp-ubuntu-latest-x64-2x` - List price: $0.004/min (as of November 2026) - Links: [Docs](https://docs.warpbuild.com), [Dashboard](https://app.warpbuild.com) **Ubicloud**: Hosted runners for GitHub Actions. - Labels: `ubicloud, ubicloud-*` - Example: `runs-on: ubicloud-standard-2` - List price: $0.00125/min (as of November 2026) - Links: [Dashboard](https://console.ubicloud.com) **Boat**: Hosted Linux runners for GitHub Actions, billed per second. - Labels: `boat, boat-*` - Example: `runs-on: boat` - List price: $0.0006/min (as of November 2026) - Links: [Docs](https://docs.boat.dev/ci), [Dashboard](https://boat.dev) 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=/runner=` - Example: `runs-on: runs-on=${{ github.run_id }}/runner=2cpu-linux-x64` - Links: [Docs](https://runs-on.com/docs/) 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--` - Example: `runs-on: starsling-ubuntu-24.04-2` - List price: $0.004/min (as of November 2026) - Links: [Docs](https://docs.starsling.dev), [Dashboard](https://runners.starsling.dev) 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-` - Example: `runs-on: monkci-ubuntu-24.04-2` - List price: $0.004/min (as of November 2026) - Links: [Docs](https://monkci.com/docs), [Dashboard](https://app.monkci.com) `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 (as of November 2026) - Links: [Docs](https://runloft.dev/docs/), [Dashboard](https://runloft.dev/app/) 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 (as of November 2026) - Links: [Docs](https://latchkey.dev/documentation), [Dashboard](https://latchkey.dev/sign-in) 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-vcpu-ubuntu-2404` - Example: `runs-on: berrybox-2vcpu-ubuntu-2404` - List price: $0.002/min (as of November 2026) - Links: [Docs](https://docs.berrybox.io), [Dashboard](https://berrybox.io/login) 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 (as of November 2026) - Links: [Docs](https://celesto.ai/docs/ci), [Dashboard](https://celesto.ai/dashboard) 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 (as of November 2026) - Links: [Docs](https://instabox.sh/docs/use-cases/ci), [Dashboard](https://instabox.sh) 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 (as of November 2026) - Links: [Docs](https://lizard.build/ci), [Dashboard](https://lizard.build) 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. ## Good to know - 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.