Each job runs on its own single-use Ubuntu VM, deleted when it ends. Change one runs-on line, pay per second, and never pay for queue time.
$20 a month includes $20 of computeSign in with GitHub
Features
Every job gets its own Ubuntu VM and is billed per second. You also get the controls a team needs, without a single machine to maintain.
Single-use VMs
Each job starts on a clean Ubuntu 24.04 VM that is deleted when the job ends. Nothing carries over from one job to the next: no leftover caches, files or credentials.
Billing
Short jobs add up when every one is rounded to a full minute. Runzemi bills running time per second, with a 15-second minimum per job, and time spent waiting in the queue is never billed.
Run history
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.
The runner masks secrets before output leaves the VM. Logs stay private for 30 days, and admins can delete them anytime.
A daily spend cap and a concurrency limit. Jobs that would exceed today’s cap wait for the next UTC day.
Minutes, jobs and cost for each runner profile, so you see where this period’s compute goes.
Install the Runzemi GitHub App on an account or organization. Runzemi sees only the repositories you grant it.
Runzemi treats every job as untrusted. It runs on a VM no other job has touched, and that VM is deleted when the job ends. A started job is never rerun automatically: CI steps can have side effects.
How it works
Connect the repositories you choose, pick a runner profile, and set runs-on to a Runzemi label. Everything else in your workflows stays as it is.
Sign in with GitHub and install the Runzemi GitHub App. It sees only the repositories you grant it.
In the dashboard, add the repository and choose its runner profile: Small, Standard or Large, all on Ubuntu 24.04. Jobs are billed per second while they run, with a 15-second minimum.
runs-onRunzemi shows the exact change and commits it once you approve. On a protected branch, it pushes a branch for a pull request instead. Or edit the workflow yourself.
Pricing
One plan, Runzemi Standard, at $20 a month with $20 of compute included. Jobs are billed per second while they run, and queue time is free.
$20/ month
Includes $20 of compute each billing period. Add funds for more.
Included compute covers up to
Sign in with GitHub. Cancel any time; your subscription stays active until the end of the billing period.
Ubuntu 24.04 on x64. Add a repository in the dashboard, choose its runner profile, then set runs-on to the matching label.
| Profile | Per minute | |
|---|---|---|
Smallyuzu-ubuntu-24.04-x64-22 vCPU · 4 GB RAM | 2 vCPU · 4 GB | $0.002/min |
StandardDefaultyuzu-ubuntu-24.04-x64-44 vCPU · 8 GB RAM | 4 vCPU · 8 GB | $0.004/min |
Largeyuzu-ubuntu-24.04-x64-88 vCPU · 16 GB RAM | 8 vCPU · 16 GB | $0.008/min |
Rates drop as usage grows within a billing period. Discounts apply automatically, and each rate covers only the usage in its tier.
| vCPU-minutes this period | Per vCPU-min |
|---|---|
| First 200,000First 50,000 Standard min | $0.001 |
| 200,000 – 1,000,00010% off50,000 – 250,000 Standard min | $0.0009 |
| Above 1,000,00020% offAbove 250,000 Standard min | $0.0008 |
One minute on Standard uses 4 vCPU-minutes.
Enter the job minutes you expect each month for each runner profile, up to 100,000 minutes per profile.
Estimated monthly total
$20/ month
$12 of compute$20 included
Fits in the $20 of included compute, so you pay the plan price only.
Billed per second while a job runs, rounded up to whole seconds, with a 15-second minimum per job. Queue time is free. Each job has a 60-minute time limit, set per repository. Included compute applies to the current billing period and doesn’t roll over. Jobs start only when funds cover them, and added funds can be used only while your subscription is active. Fees and added funds aren’t refundable except as described in the Terms of Service. Prices in USD, excluding applicable taxes.
FAQ
Runners, billing and what happens to your data, in a few sentences each.
Something else? Email support
Runzemi runs your GitHub Actions jobs on managed Ubuntu runners. Every job gets a fresh, single-use VM, and the VM is deleted when the job ends.
Your workflows stay on GitHub. To send a job to Runzemi, you add its repository in the dashboard and change the job’s runs-on label.
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 yuzu-ubuntu-24.04-x64-4 for Standard.
Runzemi can make that edit for you. Pick a branch, review the exact changes, and Runzemi 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.
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.
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, Runzemi cancels the job’s whole workflow run on GitHub, so other jobs in that run stop too. The time the job ran is billed. If your jobs need longer, contact support.
Per second while the job runs, in whole seconds rounded up, with a 15-second minimum per job. Queue time is never billed. Small costs $0.002, Standard $0.004 and Large $0.008 per minute, with volume discounts applied automatically.
The Runzemi Standard plan is $20 a month and includes $20 of compute for each billing period. Included compute doesn’t roll over. When you need more, add funds to your compute balance; usage beyond the included $20 is paid from it while your subscription is active. Jobs start only when funds cover them.
No. Every job runs on a fresh VM that has never run another job, and the VM is deleted when the job finishes. There is no warm pool of used VMs.
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.
No. Once a job has started, Runzemi 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.
Yes. Set a daily spend cap, counted in UTC days. Before a job starts, Runzemi checks the most it could cost; if that would exceed what’s left of today’s cap, the job waits until the next day. You can also set a concurrency limit on how many jobs run at once. Compute beyond the included $20 is paid from added funds in your compute balance. Jobs start only when funds cover them.
Repositories on personal accounts and organizations both work. Install the Runzemi GitHub App and grant it only the repositories you choose; Runzemi sees only those. Owners and admins then add each repository in the dashboard and choose its runner profile.
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.
$20 a month includes $20 of compute. Sign in with GitHub, add a repository, then change one runs-on line.