Managed CI runners
with load-based billing
Cloud runners for GitHub Actions and GitLab CI. Each job gets a fresh, isolated virtual machine. Pay only for actual CPU and memory load.
As your business grows,
slow CI and rigid billing inflate costs
Rigid Billing
You’re charged for time, not usage: costs become unpredictable as you scale.
Slow CI
Heavy workloads clog up CI pipelines, stalling builds and slowing teams down.
Wasted Cloud Spend
You’re paying for idle resources that your pipelines don’t actually use.
No Clarity
It's hard to optimize when you can’t see where your CI resources are going.
Finally, Compute Platform
That Solves the Real Problems
High-performance by default
Get rocket-fast builds with generous CPU and memory limits — no tuning needed.
Fair, load-based billing
Every second, we track each job’s CPU and memory load. Only pay for load, idle CPU is free.
Seamless integration
Plug into your existing setup in minutes — no vendor lock-in, no headaches.
A fresh KVM instance
for each job
Spike Instances: Mighty MicroVMs
Every job spins up a clean KVM-based instance that delivers near bare-metal performance and strong tenant isolation.
Read more
Ephemeral filesystem
Every job mounts a dedicated filesystem — a high-performance, on-demand storage that vanishes on completion, ensuring zero leftover data.
Read more
Change the runner.
Keep your workflow.
Pricing plans
Free
€0/m
Per usage price for resources
400 vCPU-minutes included monthly
800 GB-minutes included monthly
Business
€50/m
Per usage price for resources
2000 vCPU-minutes included monthly
4000 GB-minutes included monthly
10 GB of Flexible Persistent File Storage included
Enterprise
General
Free
Business
Enterprise
Dynamic load-based billing: pay for CPU-seconds and memory-seconds actually utilized by your process
Each job is running in its own clean, isolated virtual machine
Maximum concurrent jobs
vCPU allocated for each job
Memory allocated for each job (GB)
Flexible Persistent File Storage included (GB). Use it to share any data among your jobs.
Job cache, ready to use with your job provider (GitLab, GitHub, etc.)
Use GPU in your jobs
Integrations (use them to isolate different teams, projects or organizations)
Job runners per integration
Manage your runners via dashboard or declarative API
Ticket-based support
Dedicated nodes for extra isolation of your workloads
Choose the region to run your jobs
GitLab CI
Maximum service containers per job
Ephemeral storage allocated for each job (GB)
Interactive Web Terminal, allowing real-time debugging of pipelines in your GitLab dashboard
GitHub Actions
Ephemeral storage allocated for each job (GB)
GitHub environment fully compatible with the official GitHub Actions runners
Coming soon
Local Docker layer cache for even faster jobs
MS Windows execution environment
ARM-based compute nodes
Have questions?
I am located in the EU. How does EU location affect pricing and VAT application?
RunJob prices on this site are listed in EUR and exclude applicable taxes. VAT depends on your billing details and is handled under the RunJob terms of use and Customer Agreement.
Is RunJob right for your CI?
RunJob is a good fit for Linux CI jobs with bursts of CPU or memory demand, running on GitHub Actions in an organization or GitLab CI.
Personal GitHub repositories are not supported. The quickstarts cover Linux on x86-64. Check Windows, ARM, and storage needs before migrating.
What execution environments do you support?
RunJob currently supports Linux x86-64 for CI jobs.
Can I run Docker with RunJob's CI runners?
Yes. RunJob runners support Docker jobs on GitHub Actions and GitLab CI. After connecting a runner, verify your Docker build and image steps in a test workflow.
Are jobs running in an isolated kernel?
Yes. Each job runs in a fresh KVM virtual machine with its own kernel.
What kind of CPU cores are allocated for jobs?
Jobs use shared CPU cores by default. Enterprise customers can request exclusive cores; those are billed by the requested allocation, regardless of momentary CPU usage.
What settings do I need to make in my jobs to run them on RunJob?
Do you support any job providers other than GitLab and GitHub?
RunJob currently supports GitLab CI and GitHub Actions jobs.
Is RunJob related to GitLab Inc. or GitHub Inc.?
No. RunJob operates independently of GitLab Inc. and GitHub Inc.