Skip to content

Runners for GitHub Actions

Fast CI.
Smaller bill.

Change one runs-on line and pay up to 40% less per minute than GitHub’s Linux x64 runners.

$20/month includes $40 of compute.
Sign in with GitHub.

RunzumiRuns / #1048
Passed4 vCPU · 8 GB RAM

Build and test

website main7b32c8e

Job duration
2m 22s
Billed VM cost
$0.0194
Illustrative job. Billed for 2m 42s of metered VM time, including 20s of simulated overhead; actual overhead varies.
Lower rate
40%
4-vCPU compute vs. GitHub Linux x64
Starting at
$0.0036/min
2 vCPUs · 4 GB RAM
Minimum billed
20s
Then per second of VM lifetime
Largest runner
16vCPUs
32 GB RAM on Ubuntu 24.04

How it works

Three steps,
one changed line.

Connect your repository, choose a runner, and change its label. Everything else in your workflow stays as it is.

Get started

.github/workflows/ci.yml

  jobs:    test:-     runs-on: ubuntu-latest+     runs-on: runzumi-ubuntu-24.04-x64-4      steps:        # Your existing build and test steps
runs-on: runzumi-ubuntu-24.04-x64-4

  1. Install the GitHub App

    Sign in with GitHub and install the Runzumi GitHub App. It sees only the repositories you grant it.

  2. Add a repository, choose a profile

    Pick 2, 4, 8 or 16 vCPUs to match your workload. All profiles run Ubuntu 24.04.

  3. Approve the workflow change

    Review the exact change before Runzumi commits it. On a protected branch, it pushes a branch for a pull request instead. Or edit the workflow yourself.

Features

Put more compute behind every push

Choose 2, 4, 8 or 16 vCPUs for your builds and tests, with lower Linux x64 compute rates than GitHub at every size. Your workflows stay familiar. Your runners are managed.

Build performance

Give demanding builds more power

Step up to 16 vCPUs and 32 GB RAM when your builds need more room for parallel work. Every profile runs Ubuntu 24.04 on its own VM, managed from start to finish.

Lower compute costs

Small rates. Down to the second.

Start at $0.0036 per minute for 2 vCPUs. VM time is billed by the second with a 20-second minimum, and queueing before VM creation is free.

Run history

Know where every CI dollar goes

Status, duration and cost for every job, with the repository, branch and commit it ran on. Charts track duration and queue time next to your success rate.

  • Secrets masked

    The runner masks secrets before output leaves the VM. Logs stay private for 30 days, and admins can delete them anytime.

  • Spend controls

    A daily spend cap and a concurrency limit. Jobs wait when their reservation would exceed the remaining cap for the UTC day.

  • Usage by profile

    Billed VM minutes and cost for each runner profile. Track GitHub execution time separately from the compute you pay for.

  • Only repos you choose

    Install the Runzumi GitHub App on an account or organization. Runzumi sees only the repositories you grant it.

Billed by the second. A 25-second job costs 75% less than on GitHub.

GitHub
Billed 1:00
$12.00 per 1,000 jobs
Runzumi
Billed 0:25
$3.00 per 1,000 jobs
You save
$9.00 per 1,000 jobs, 75% less

Standard profile, 4 vCPUs, at list prices per 1,000 jobs. Runzumi bills every second, with a 20-second minimum; GitHub rounds each job up to the minute. How we compare

Pricing

Up to 40% lower rates than GitHub. $20 a month includes $40 of compute.

Start at $0.0036 per minute, and contact us for Enterprise pricing at higher volumes.

Runzumi Standard

$20/ month

Includes $40 of compute.
Add funds for more.

  • 2, 4, 8 or 16 vCPU runner profiles
  • Per-second VM billing, 20-second minimum
  • Queueing before VM creation is free
  • Add funds as your usage grows
  • Personal and organization repositories
  • Daily spend cap and concurrency limit
Get started

Sign in with GitHub. Cancel any time; your subscription stays active until the end of the billing period.

Estimate your monthly bill

Enter total billed VM minutes for each profile, including preparation, idle time, execution, metered cleanup and the 20-second minimum per VM. Up to 100,000 minutes per profile. Estimates use published Standard rates. For higher volumes, contact us for Enterprise pricing.

Billed VM minutes per month

2 vCPU · 4 GB RAM · $0.0036/min

4 vCPU · 8 GB RAM · $0.0072/min

8 vCPU · 16 GB RAM · $0.0144/min

16 vCPU · 32 GB RAM · $0.0324/min

Estimated monthly total

$20/ month

$21.60 of compute$40 included

Runzumi Standard plan (includes $40 of compute)
$20
Extra compute from added funds
$0
Billed vCPU-minutes
12,000

Fits in the $40 of included compute, so you pay the plan price only.

Runner profiles and rates

Ubuntu 24.04 on x64. Choose a repository’s profile in the dashboard, then set runs-on to the matching label. Rates apply to the VM’s metered lifetime.

Runzumi runner profiles and per-minute rates, compared with GitHub paid Linux x64 rates
ProfileRunzumivs GitHub
Smallrunzumi-ubuntu-24.04-x64-22 vCPU · 4 GB RAM$0.0036/minGitHub $0.006−40%
StandardDefaultrunzumi-ubuntu-24.04-x64-44 vCPU · 8 GB RAM$0.0072/minGitHub $0.012−40%
Largerunzumi-ubuntu-24.04-x64-88 vCPU · 16 GB RAM$0.0144/minGitHub $0.022−34%
X-Largerunzumi-ubuntu-24.04-x64-1616 vCPU · 32 GB RAM$0.0324/minGitHub $0.042−22%
Compare runner pricing

Runzumi Enterprise

Running at higher volumes? Contact us to discuss an Enterprise plan and pricing for your team’s compute needs.

Contact us

FAQ

Questions, answered

Runners, billing and what happens to your data, in a few sentences each.

Something else? Email support

What is Runzumi?

Runzumi runs your GitHub Actions jobs on managed Ubuntu runners. Choose 2, 4, 8 or 16 vCPUs, pay by the second, and track each job’s cost in the dashboard.

Your workflows stay on GitHub. To send a job to Runzumi, you add its repository in the dashboard and change the job’s runs-on label.

How much can I save compared with GitHub?

At list rates, 2- and 4-vCPU compute costs 40% less per minute than GitHub’s paid Linux x64 runners at the same CPU count. The 8-vCPU rate is about 34% lower, and the 16-vCPU rate is about 22% lower.

Actual savings depend on job duration, VM overhead, memory needs and any GitHub minutes included in your plan. Runzumi starts at $20 a month with $40 of compute included. See the pricing comparison for rates and assumptions.

How do I move a workflow to Runzumi?

Start in the dashboard: an owner or admin adds the repository and chooses its runner profile. Then set each job’s runs-on to that profile’s label, such as runzumi-ubuntu-24.04-x64-4 for Standard.

Runzumi can make that edit for you. Pick a branch, review the exact changes, and Runzumi commits them in one commit – or, on a protected branch, pushes a separate branch for you to open a pull request. Only the runs-on value changes; the rest of each file stays as it is. This needs an owner or admin with write access to the repository on GitHub.

You can also edit .github/workflows yourself.

What’s on the runner image?

Ubuntu 24.04 on x64, with Docker for container and service jobs, plus git and common build tools. Tool versions can differ from GitHub-hosted images, so pin the versions you rely on with setup actions such as actions/setup-node. Jobs that run on ubuntu-latest or ubuntu-24.04 today are the best fit; macOS, Windows and ARM jobs stay on GitHub.

Is there a job time limit?

Yes. Each job can run for up to 60 minutes. The job time limit is set per repository and appears as “Default job timeout” in the dashboard. When a job reaches it, Runzumi cancels the job’s whole workflow run on GitHub, so other jobs in that run stop too. The VM’s metered lifetime is billed, including cleanup. If your jobs need longer, contact support.

How is usage billed?

Per second for the VM’s metered lifetime, including preparation, idle time, job execution and metered cleanup, with a 20-second minimum per created VM—even if its job never starts. Queueing before VM creation and unmetered deletion waits are free. Per minute at published Standard rates: Small $0.0036, Standard $0.0072, Large $0.0144 and X-Large $0.0324. For higher volumes, contact us about Enterprise pricing.

Why can billed time be longer than job duration?

GitHub job duration measures execution. Billed VM time also includes preparation, idle time and metered cleanup. The dashboard shows them separately. If final usage is unavailable, a settled charge may use the last valid usage reading, capped at the original reservation; it is labeled as an estimate. If no usable reading exists, the charge is written off and you pay nothing for that VM.

What does the Runzumi Standard plan include?

The Runzumi Standard plan is $20 a month and includes $40 of compute for each billing period. Unused included compute expires at the end of the period and doesn’t roll over. When you need more, add funds to your compute balance; usage beyond the included $40 is paid from it while your subscription is active. Added funds don’t expire while your account stays open. Jobs start only when funds cover them.

Is a VM ever reused?

No. Every job runs on a dedicated VM that has never run another job, and the VM is deleted when the job finishes. There is no warm pool of used VMs.

What happens to my logs and secrets?

The runner masks secrets on the VM, before any output leaves it. Logs are stored privately for 30 days, and owners and admins can delete a job’s logs at any time. GitHub keeps its own copy, which you manage on GitHub.

Will Runzumi rerun a failed or interrupted job?

No. Once a job has started, Runzumi never reruns it automatically, because CI steps can have side effects outside the VM, such as a deploy or a published package. When you want another attempt, rerun the job from GitHub.

Can I limit spending?

Yes. Set a daily spend cap, counted in UTC days. Before a job starts, Runzumi checks the most it could cost, including a five-minute allowance beyond its time limit. If that reservation exceeds the remaining cap, the job waits for budget to become available. You can also set a concurrency limit on how many jobs run at once. Compute beyond the included $40 is paid from added funds in your compute balance. Jobs start only when funds cover their reservation. Reserved funds cover running VMs and VMs awaiting final billing; the unused portion is released when billing settles.

Which repositories can I use?

Repositories on personal accounts and organizations both work. Install the Runzumi GitHub App and grant it only the repositories you choose; Runzumi sees only those. Owners and admins then add each repository in the dashboard and choose its runner profile.

How do I cancel?

Owners, admins and billing members can cancel the subscription from the billing portal, which opens from the Billing page in the dashboard. Payments are handled by Stripe. Your subscription stays active until the end of the current billing period.

Added funds can be used only while the workspace has an active subscription. Unused added funds stay in the workspace and can be used again if you resubscribe. Fees and added funds aren’t refundable, except as described in the Terms of Service.

Make your next build cost less

$20 a month includes $40 of compute. Sign in with GitHub, add a repository, then change one runs-on line.