Runloft vs Namespace
Namespace bundles runners with remote Docker builds and devboxes, metered in unit minutes on monthly plans. Runloft prices a 2 vCPU, 8 GB Linux machine at half Namespace's pay-as-you-go rate for the same size, per second, with no plan.
| Feature | Namespace | Runloft |
|---|---|---|
| Linux, 2 vCPU 8 GB, per minute | $0.006 pay as you go, $0.004 inside a plan | $0.003 |
| Linux, 2 vCPU 4 GB, per minute | $0.003 pay as you go | Smallest size is 2 vCPU 8 GB |
| Monthly plans | Optional, from $100 per month | None, prepaid credits |
| Billing granularity | Per minute, 1 minute minimum | Per second, no minimum |
| Free usage | 30-day trial | 3,000 Linux minutes every month |
| Windows and macOS | Yes | By request |
Namespace prices from namespace.so/pricing, October 2026. Namespace counts one unit per vCPU or per 2 GB of memory, whichever is larger. Runloft prices are on the pricing page.
When Namespace is the better fit
- You also want remote Docker builds, cross-run caching and devboxes from the same vendor.
- You need macOS or Windows runners today.
When Runloft is
- Your workload is GitHub Actions jobs and agents, and you want to pay only for the seconds they run.
- You want a free allowance that renews every month rather than a trial.
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, WarpBuild, RunsOn
.github/workflows/ci.yml
jobs:
build:
- runs-on: ubuntu-latest
+ runs-on: runloft-ubuntu-24.04