← All integrations

Boat integration

Route jobs between Boat, your machines and GitHub.

Boat runs each GitHub Actions job in a fresh Linux VM, under your Boat account. Jobs go to your machines first and to Boat when they're busy. You change the order from the dashboard, not your workflows.

Get started with GitHub

With routing

Boat on its own, or in your runner order

Boat on its own

  1. Each workflow names a Boat label, so every job runs on Boat.
  2. Your own machines sit idle while Boat bills you.
  3. Trying another host means editing every workflow again.
  4. Each host shows its own job times in its own dashboard.

In your runner order

  1. Jobs run on your machines first, and on Boat when your machines are busy.
  2. GitHub-hosted runners stay as the fallback after Boat.
  3. Move Boat up, down or out from the dashboard. No workflow edits.
  4. The Performance page compares Boat's job times with your machines and GitHub-hosted runners.

Setup

How to set up Boat

  1. Set up your Boat account

    Get Boat's $20 plan or higher, then run boat ci connect to install the boat CI GitHub App on your organization.

  2. Add Boat to your runner order

    On the Router page, put Boat where you want it. A common order is your machines, then Boat, then GitHub-hosted.

  3. Add relays to your jobs

    Run npx relayrunner init in your repo. It adds a relay to each job you pick and keeps the label the job uses today as its fallback.

.github/workflows/ci.yml
jobs:
  relay-test:
    uses: relayrunner/actions/.github/workflows/relay.yml@v1
    with:
      machine: self-hosted
      boat: boat
      github: ubuntu-latest
  test:
    needs: relay-test
    runs-on: ${{ needs.relay-test.outputs.runner }}

The relay

Name a Boat label in the relay.

The relay answers in about a second and uses no minutes. It returns the label of the first runner in your order that can take the job, and the job runs there.

Read how routing works →

Details

Boat at a glance

What it is
Hosted Linux runners for GitHub Actions, billed per second.
Labels
boat, boat-*
Example
runs-on: boat
Relay input
boat
Links

Plans

CI needs the $20 plan or higher. Each plan's fee comes back as VM time at machine prices, and unused time ends with the month. boat-xlarge needs $100 or more.

Plan Monthly Included Job starts
$20 plan $20 $20 of VM time 12/min · 60/hr · 200/day
$100 plan $100 $100 of VM time 30/min · 210/hr · 840/day
$500 plan $500 $500 of VM time 65/min · 420/hr · 1,680/day
$2,000 plan $2,000 $2,000 of VM time 90/min · 600/hr · 2,400/day

From Boat's pricing page, checked Nov 17, 2026.

List prices

boat-small $0.0003/min
boat $0.0006/min
boat-large $0.0012/min
boat-xlarge $0.00333/min

As of November 2026, from Boat's price page. Boat bills you directly, so your plan and credits apply.

CI needs Boat's $20 plan or higher, which comes back as VM time. Starts past the plan's limits cost $0.03 to $0.07 each.

Common questions

How is this different from using Boat directly?

Used directly, every job that names a Boat label runs on Boat. In a runner order, jobs go to your own machines first and to Boat only when they're busy, and you can move Boat up, down or out from the dashboard without editing workflows.

Do I have to change my workflows to use Boat?

Once. Run npx relayrunner init in your repo and it adds a relay to each job you pick. After that, you move Boat up or down in the dashboard.

Which jobs go to Boat?

Jobs whose relay names a Boat label, when nothing above Boat in your runner order is free.

Who bills me for Boat?

Boat does. Jobs run under your own Boat account, so your plan, credits and discounts still apply.

Do public repos run on Boat?

Not by default. Boat refuses jobs from public repos until you allow them with boat ci public, and then runs only the people you list.

What happens when I reach Boat's start limits?

Each job is one start, and Boat caps starts per minute, hour and day: 12, 60 and 200 on the $20 plan. Past the hour or day limit a job shows Paused by plan limit on GitHub and waits until someone re-runs it. Putting your own machines first in the runner order keeps those starts for when you need them.

Which runners does Boat have?

Linux x64 only, on Ubuntu 24.04: boat-small (2 vCPU), boat (4 vCPU), boat-large (8 vCPU) and boat-xlarge (16 vCPU, on the $100 plan and up). For macOS, Windows or Arm, put another runner after Boat in your order.

Add Boat to your runner order.

Add relays once. After that, change the order in the dashboard.

  1. 1. In your repo, add relays to the jobs you want to route
    npx relayrunner init
  2. 2. Optionally, turn this computer into a runner
    npx relayrunner connect