Introduction

What RaftRun runs for you: GitHub Actions jobs, and Docker hosts for your laptop and coding agents.

RaftRun gives your team machines for two jobs. GitHub Actions runners run your workflow jobs on a fresh Ubuntu machine each, billed by the second. Docker hosts give each person a remote Docker engine for their laptop, their CI and their coding agents, which starts when they connect and stops when they leave.

Both live in one workspace, with one plan, one invoice and one set of people.

GitHub Actions runners

Install the RaftRun GitHub App on your organisation, then change a job's runs-on line. Nothing else in the workflow changes.

.github/workflows/ci.yml
jobs:
  build:
    runs-on: ubuntu-latest
    runs-on: raft-ubuntu-24.04
  • Each job gets its own Ubuntu 24.04 x64 machine with root and Docker, from half a vCPU to 16. It is deleted when the job ends.
  • Billing starts when the machine picks up the job and stops when the job ends. Queueing and start-up are free.
  • A cache for actions/cache, outbound traffic rules, limits, log search and analytics come with every plan.

Docker hosts

Point docker at your host and builds, containers and compose stacks run there instead of on your laptop. It reaches the host over SSH, so there is nothing to install beyond Docker itself.

your terminal
export DOCKER_HOST=ssh://my-laptop@ssh.raftrun.com:2222
docker compose up -d
  • A host starts on the first command and stops after 10 minutes without a connection. Stopped, it costs nothing and keeps its images and volumes.
  • Published ports are private. You open them on your own machine through an SSH tunnel, and the dashboard shows which services are running and healthy.
  • Give each project folder its own host, so projects, and the coding agents working in them, never share containers or ports.

Where to start