Run your builds.
Not up your bill.
Fixed-price GitHub Actions runners. We handle the servers, updates, and cleanup. Your unused capacity earns extra compute for later.
Your quiet hours power your busy hours.
Leave capacity unused
No jobs runningEarn compute credits
Saved for laterRun more jobs at once
Your reserved runnerExtra runner using creditsExtra runner using credits
Predictable bills. No servers to maintain.
| Runners | Your monthly bill | Who maintains the servers? | Need more jobs running? |
|---|---|---|---|
| GitHub-hosted / Blacksmith | Pay per build minute | The provider | More runners, billed by usage |
| Your VPS | Fixed, even when idle | You | Wait or rent more servers |
| BaseRunner | Fixed. Idle time earns credits. | We do | Use earned credits for extra runners |
Start fresh between customers.
Start with a clean VM
An isolated environment assigned to you.
Reuse for your jobs
Jobs with the same trust level can share the VM.
New customer, new VM
We destroy the old VM before switching customers.
Common questions.
What does the subscription cover?
You reserve computing power and a guaranteed number of jobs that can run at once. Run them all month for the same price. You also pay when they’re idle. Plans and pricing haven’t been set yet.
How do compute credits work?
When you leave reserved capacity unused, part of that time becomes compute credits. Spend them on extra runners so more jobs can run at once. The earning rate, expiry window, and limits on extra runners are still being worked out.
What would I change in GitHub Actions?
Keep your repositories and workflows in GitHub, and point jobs at BaseRunner’s runners. Setup details and supported operating systems and architectures are still being worked out.
Do I need credits for my regular jobs?
No. Your subscription guarantees your reserved capacity, even if you use it all month. Credits only pay for extra runners. Without credits, jobs beyond your reserved capacity wait in the queue.
Would you have access to my code and secrets?
Yes. BaseRunner would execute your code and any secrets passed to a job. Untrusted pull requests must run separately from jobs with deployment secrets. The security design and an independent review still need to be completed.