Runloft vs WarpBuild
WarpBuild sells fast runners on Linux, Windows and macOS to GitHub organizations, billed by the minute. Runloft is a quarter cheaper on 2 vCPU Linux, bills by the second, and installs on personal accounts too.
| Feature | WarpBuild | Runloft |
|---|---|---|
| Linux x64, 2 vCPU 8 GB, per minute | $0.004 | $0.003 |
| Linux arm64, 2 vCPU 8 GB, per minute | $0.003 | $0.003 (by request) |
| Windows, per minute | $0.016 for 4 vCPU (smallest size) | $0.007 for 2 vCPU (by request) |
| macOS, per minute | $0.08 | $0.06 (by request) |
| Personal GitHub accounts | No, organizations only | Yes |
| Billing granularity | Per minute | Per second, no minimum |
| Free usage | $10 of credit at signup | 3,000 Linux minutes every month |
| Setup | Install a GitHub App, change runs-on | Install a GitHub App, change runs-on |
WarpBuild prices from warpbuild.com/pricing, October 2026. Runloft prices are on the pricing page.
When WarpBuild is the better fit
- You need macOS, Windows or arm64 runners today, at sizes up to 32 vCPU.
- You want their cache and snapshot features, or to run their runners inside your own cloud account.
When Runloft is
- Most of your jobs are short Linux jobs, where per-second billing and the lower 2 vCPU rate add up.
- You work from a personal GitHub account, or want one setup for personal and organization repositories.
- Agents run on every pull request and comment, and you want a monthly free allowance instead of a one-off credit.
Trying it takes one line
Install the GitHub App on one repository and change one job. If it is not for you, change the line back; there is nothing else to undo.
All comparisons. Others: GitHub-hosted runners, Blacksmith, Depot, Ubicloud, Namespace, RunsOn
.github/workflows/ci.yml
jobs:
build:
- runs-on: ubuntu-latest
+ runs-on: runloft-ubuntu-24.04