RunJob
EU-based managed runners for GitHub Actions and GitLab CI that run each job in a fresh KVM virtual machine and bill only CPU and memory used. An EU-based managed runner service for GitLab CI and GitHub Actions with usage-metered billing and one KVM virtual machine per job, suited to teams whose jobs spend much of their time below peak load.
Overview
RunJob (formerly RunMyJob by puzl.cloud) is a managed runner service from Puzl Cloud OÜ for GitHub Actions and GitLab CI. GitHub organizations install an app and change runs-on to runjob-ubuntu-latest; GitLab users register a RunJob runner against GitLab.com or a self-hosted instance and keep their pipeline files as they are. Each job runs in a fresh KVM virtual machine that the company calls a Spike Instance.
Instead of fixed runner sizes, a job’s VM draws CPU and memory as the workload needs them, up to a per-plan limit, and billing counts only the vCPU-seconds and GB-seconds actually used. The service describes itself as EU based and SOC 2 Type II compliant. Runners can be managed from a console, a Kubernetes-style declarative API or Terraform modules, and Business and Enterprise plans add an interactive web terminal for GitLab jobs.
Notable
- The docs introduction states that RunJob was formerly named RunMyJob by puzl.cloud; on November 22, 2026 the puzl.cloud product and documentation URLs redirected to runjob.eu.
- As of November 22, 2026 the plan table lists a Windows execution environment and a local Docker layer cache as coming soon.
- As of November 22, 2026 the FAQ states that Linux x86-64 is the currently supported environment for CI jobs.
RunJob specifications
| Attribute | Details |
|---|---|
| CI systems | GitHub Actions, GitLab CI |
| Operating systems | Linux |
| Architectures | x64 |
| Deployment | Managed runner service |
| Isolation | Each job runs in its own dynamically spawned KVM virtual machine (a “Spike Instance”) with its own kernel; the job filesystem is erased when the job completes |
| Fresh environment per job | Yes |
| Hardware | Not documented |
| Performance (vendor claim) | Puzl says jobs run up to 2x faster and up to 5x cheaper than on other platforms (vendor claim) |
| Runner sizes | No fixed sizes: a job’s VM scales with load up to a per-job limit of 12 vCPU / 32 GB on Free and 48 vCPU / 96 GB on Business; custom on Enterprise |
| Caching | GitHub Actions jobs use RunJob’s own cache action (puzl-cloud/github-actions-cache) with 30-day default retention, or shared persistent mount points. Job cache and persistent file storage are listed for the Business and Enterprise plans. A local Docker layer cache is listed as coming soon. |
| Docker layer caching | No |
| GPU | GPU use is listed as an Enterprise-plan feature, billed per allocated GPU-second on top of any plan; models and prices are not published. |
| Concurrency | 10 concurrent jobs on Free; unlimited on Business and Enterprise |
| Job limits | Ephemeral storage per job is 100 GB for GitLab and 150 GB for GitHub; GitLab jobs get up to 2 service containers on Free and 10 on Business |
| Static IPs | Not documented |
| SSH into running jobs | Yes |
| Observability | A cloud console lists jobs, integrations and runners; the same resources can be managed through a Kubernetes-style API and Terraform modules |
| Setup | GitHub Actions: install the RunJob app in a GitHub organization and change runs-on to runjob-ubuntu-latest. GitLab CI: create an integration and a runner claim with a GitLab token; existing pipeline files stay unchanged. |
| Example label | runjob-ubuntu-latest |
| Pricing | Load-based: €0.00002 per utilized vCPU-second and €0.000001 per utilized GB-second of memory, with idle CPU not billed; persistent storage is €0.00000006 per GB-second. Free plan: €0/month with 400 vCPU-minutes and 800 GB-minutes included. Business: €50/month with 2,000 vCPU-minutes and 4,000 GB-minutes included. Prices exclude VAT. |
| Free tier | Free plan at €0/month with 400 vCPU-minutes and 800 GB-minutes per month, 1 integration and 10 concurrent jobs; the Business plan has a 14-day trial |
| Compliance | SOC 2 Type II; Puzl also states GDPR compliance |
| Regions | Described as EU based; specific locations are not published, and choosing a run region is listed as an Enterprise feature |
| Open source | No |
| Company headquarters | Tallinn, Harju County, Estonia · More from Estonia |
Facts from RunJob’s public documentation, verified November 22, 2026. Performance figures are vendor claims.
Strengths and trade-offs
Reasons to choose it
- You run GitLab CI, on GitLab.com or self-hosted, and want a third-party managed runner that needs no pipeline changes
- You want billing by CPU-seconds and memory-seconds actually used, with idle CPU not charged
- You need each job isolated in its own KVM virtual machine at an EU-based, SOC 2 Type II provider
- You want to manage runners declaratively through an API or Terraform modules
Trade-offs
- Linux x86-64 is the only currently supported execution environment (FAQ)
- GitHub runners work with organization accounts only; personal repositories are not supported
- Job cache and persistent file storage are not included in the Free plan
- A local Docker layer cache is listed as coming soon
Good fit for: Teams on GitLab CI or GitHub Actions that want EU-hosted runners billed by actual CPU and memory use instead of by runner size.
Use cases RunJob fits
- Lower CI cost: Billing covers only utilized vCPU-seconds and GB-seconds, and a free plan includes 400 vCPU-minutes per month.
- GitLab CI runners: RunJob registers managed runners for GitLab.com and self-hosted GitLab without changes to existing pipelines.
- Security and compliance: Each job runs in its own KVM virtual machine with an ephemeral filesystem, and Puzl states SOC 2 Type II and GDPR compliance.
How RunJob compares
| Runner | CI systems | Runs on | Deployment | Isolation | Price | Largest runner | Docker layer cache | GPU | Open source | Company HQ |
|---|---|---|---|---|---|---|---|---|---|---|
| RunJob | GitHub Actions, GitLab CI | Linux, x64 | Vendor-hosted | KVM virtual machine | €0.00002 per vCPU-second used | 48 vCPU / 96 GB | No | Yes | No | Estonia |
| GitLab-hosted runners | GitLab CI | Linux, macOS, Windows, x64, arm64 | Platform-hosted | Ephemeral VM | $10 per 1,000 compute minutes | 32 vCPU / 128 GB | Not documented | Yes | No | Not documented |
| GitLab Runner | GitLab CI | Linux, macOS, Windows, x64, arm64 | Self-hosted | Depends on executor | Free software + your infrastructure | Set by your infrastructure | Not documented | Yes | Yes | Not documented |
| GitHub-hosted runners | GitHub Actions | Linux, macOS, Windows, x64, arm64 | Platform-hosted | Fresh VM | $0.006/min | 96 vCPU / 384 GB | Not documented | Yes | No | United States |
| Ubicloud Runners | GitHub Actions | Linux, x64, arm64 | Vendor-hosted | KVM VM | $0.00125/min | 30 vCPU / 120 GB | Yes | Not documented | Yes | United States |
| Namespace | GitHub Actions, Buildkite | Linux, macOS, Windows, x64, arm64 | Vendor-hosted | Virtual machine | $0.002/min prepaid, $0.003/min overage (2 vCPU / 4 GB) | 64 vCPU / 512 GB | Yes | Not documented | No | Not documented |
| Blacksmith | GitHub Actions | Linux, macOS, Windows, x64, arm64 | Vendor-hosted | Firecracker microVM | $0.004/min | 32 vCPU / 128 GB | Yes | Not documented | No | United States |
| Cirun | GitHub Actions | Linux, macOS, Windows, x64, arm64 | Your cloud or hardware | Cloud VM | $29/mo (3 private repos) + cloud cost | Set by your infrastructure | Yes | Yes | No | United Kingdom |
Head-to-head: GitLab-hosted runners vs RunJob
Frequently asked questions
What is RunJob?
Which CI systems does RunJob work with?
How does RunJob isolate jobs?
Is RunJob open source?
How much does RunJob cost?
How do I switch from GitHub-hosted runners to RunJob?
runjob-ubuntu-latest.How fast is RunJob?
Does RunJob have a free tier?
Does RunJob offer GPU runners?
How many jobs can run at once on RunJob?
Where do RunJob runners run?
What compliance certifications does RunJob have?
Where is Puzl Cloud OÜ based?
What are the alternatives to RunJob?
Sources
- runjob.eu/
- runjob.eu/docs/introduction
- runjob.eu/docs/getting-started
- runjob.eu/docs/security
- runjob.eu/docs/spike-instances
- runjob.eu/docs/github-actions/github-runner-labels
- runjob.eu/docs/github-actions/github-actions-cache-and-persistent-storage
- runjob.eu/docs/gitlab-pipelines/quick-setup-of-gitlab-runner
- runjob.eu/docs/resources-and-billing/nvidia-gpu
- puzl.cloud
- puzl.cloud/pricing/
- puzl.cloud/trust/
Check before you rely on it. Products change quickly, and this page reflects public documentation as of November 22, 2026. Confirm anything that matters in the provider’s own documentation.
Cite this page
CI Runners. (2026). RunJob. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/runners/runjob/