GitHub Actions runners

GitHub self-hosted runners, fresh for every job.

When a queued workflow job carries the labels you chose, FlatRun starts a self-hosted runner in a fresh Firecracker microVM or Docker container on your server. It exits after that job.

Open source, MIT licensed · Runs on any Linux server with Docker

Sound familiar?

A persistent runner runs every job where the last one ran.

GitHub lists its standard Linux hosted runner at $0.006 a minute in private repositories, and self-hosted runner usage is free: you pay for the server. But a runner that stays installed reuses its machine between jobs, so files and processes one job leaves are there for the next.

How it works

Three steps, on a server you control.

  1. 01

    Connect a GitHub App

    Install your GitHub App on the repository with Administration write permission and point its workflow job webhook at FlatRun.

  2. 02

    Choose the labels

    Set the labels that start a runner, such as self-hosted and flatrun, and use the same labels in the workflow's runs-on.

  3. 03

    Run the workflow

    A matching queued job starts a runner. Firecracker is the default runtime, and a job can run for up to an hour.

Runner job

Before you get started.

Can jobs run Docker containers?

Not with the default image. Container jobs need a runner image with Docker Engine whose start script launches the daemon, and that only works under Firecracker, where the daemon stays inside the VM.

Are runner credentials stored with the run?

No. The installation token and the runner's registration are kept out of run records and the delivery log. The runner receives its registration as a secret.

Which image does a job run in?

ghcr.io/actions/actions-runner unless you name another. Jobs that need tools it lacks must install them or use an image that includes them.

More of FlatRun

Star us on GitHub