CI Runnerscirunners.org
Head-to-head

GitLab-hosted runners vs RunJob

Answer in brief

GitLab-hosted runners suits teams on GitLab.com that want CI jobs to run with no runner setup and can work within the included compute minutes. RunJob suits teams on GitLab CI or GitHub Actions that want EU-hosted runners billed by actual CPU and memory use instead of by runner size. GitLab-hosted runners is the CI platform’s own hosted runners for GitLab CI, priced at $10 per 1,000 compute minutes; RunJob is a managed service hosted by the vendor for GitHub Actions and GitLab CI, priced at €0.00002 per vCPU-second used.

By the CI Runners editors · Updated

Key differences between GitLab-hosted runners and RunJob

  • Type: GitLab-hosted runners is the CI platform’s own hosted runners; RunJob is a managed service hosted by the vendor.
  • CI systems: Only RunJob documents GitHub Actions.
  • Operating systems: Only GitLab-hosted runners documents macOS and Windows.
  • Architectures: Only GitLab-hosted runners documents arm64.
  • Isolation: GitLab-hosted runners: Ephemeral VM. RunJob: KVM virtual machine.
  • Published price: $10 per 1,000 compute minutes (GitLab-hosted runners) versus €0.00002 per vCPU-second used (RunJob).
  • Largest runner: 32 vCPU / 128 GB (GitLab-hosted runners) versus 48 vCPU / 96 GB (RunJob).

What they have in common

  • Both run GitLab CI jobs.
  • Both document Linux runners.
  • Both use a virtual machine per runner.
  • Both give every job a fresh environment.
  • Neither is open source.
  • Both document GPU runners.

GitLab-hosted runners vs RunJob at a glance

AttributeGitLab-hosted runnersRunJob
What it isGitLab.com’s built-in runners: each job gets a single-use VM, metered in compute minutes with a cost factor per machine size.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.
TypeFirst-party hosted runnersManaged runner service
CI systemsGitLab CIGitHub Actions, GitLab CI
Operating systemsLinux, macOS, WindowsLinux
Architecturesx64, arm64x64
IsolationEach job runs in a newly provisioned VM that serves a single job and is deleted right after it; firewall rules block inbound traffic and traffic between VMsEach 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 jobYesYes
HardwareLinux runners are Google Compute Engine VMs running Container-Optimized OS; macOS runners are Apple silicon M1 and M2 Pro machines. GitLab notes that machine and processor types might changeNot documented
Performance (vendor claim)Not documentedPuzl says jobs run up to 2x faster and up to 5x cheaper than on other platforms (vendor claim)
Runner sizesLinux x86-64: 2 vCPU / 8 GB to 32 vCPU / 128 GB; Linux Arm64: 2 vCPU / 8 GB to 8 vCPU / 32 GB; macOS: 4 vCPU / 8 GB (M1) and 6 vCPU / 16 GB (M2 Pro); Windows: 2 vCPU / 7.5 GBNo 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
CachingHosted runners share a distributed cache in Google Cloud Storage. Cache contents not updated in the last 14 days are removed, and an uploaded cache archive can be at most 5 GB.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 cachingNot documentedNo
GPUOne GPU machine type on Linux x86-64 for Premium and Ultimate: 4 vCPU, 15 GB RAM and 1 NVIDIA Tesla T4 (or similar) with 16 GB, at cost factor 7.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.
ConcurrencyMaximum jobs in active pipelines on GitLab.com: 500 on Free, 20,000 on Premium and 60,000 on Ultimate10 concurrent jobs on Free; unlimited on Business and Enterprise
Static IPsNot documentedNot documented
SSH into running jobsNot documentedYes
PricingNo per-minute price is published. Jobs consume compute minutes at job duration times a cost factor: Linux small 1, medium 2, large 3, xlarge 6, 2xlarge 12; GPU 7; macOS M1 6 and M2 Pro 12 (beta); Windows 1 (beta). Additional compute minutes cost $10 per 1,000 minutes as a one-time purchase.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 tier400 compute minutes per month on the Free tier; Premium includes 10,000 and Ultimate 50,000 per monthFree 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
Open sourceNoNo
Self-host / your cloudNo / NoNo / Not documented
ComplianceNot documentedSOC 2 Type II; Puzl also states GDPR compliance
RegionsLinux x86-64 VMs run in Google Cloud us-east1 and us-east5; Linux Arm64 VMs run in us-central1Described as EU based; specific locations are not published, and choosing a run region is listed as an Enterprise feature
Company headquartersNot documentedTallinn, Harju County, Estonia
Good fit forTeams on GitLab.com that want CI jobs to run with no runner setup and can work within the included compute minutesTeams on GitLab CI or GitHub Actions that want EU-hosted runners billed by actual CPU and memory use instead of by runner size

Verified November 22, 2026 from each provider’s documentation. Performance figures are vendor claims, not our measurements.

Which should you choose?

Reasons to choose GitLab-hosted runners

  • You host code on GitLab.com and want pipelines to run without registering any runner
  • You want each job in its own VM that is deleted after the job
  • You need Docker-in-Docker, which the Linux runners support by running in privileged mode
  • You need Linux Arm64 or a GPU machine alongside x86-64 from the same platform

Reasons to choose RunJob

  • 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 to check first

  • GitLab-hosted runners: Hosted runners on macOS and on Windows are in beta
  • GitLab-hosted runners: Jobs time out after 3 hours regardless of the project timeout
  • RunJob: Linux x86-64 is the only currently supported execution environment (FAQ)
  • RunJob: GitHub runners work with organization accounts only; personal repositories are not supported

Run your slowest workflow on both before deciding. See the full GitLab-hosted runners profile and RunJob profile, or the complete comparison.

More comparisons

Frequently asked questions

Is GitLab-hosted runners or RunJob better?
Neither is better for every pipeline. GitLab-hosted runners suits teams on GitLab.com that want CI jobs to run with no runner setup and can work within the included compute minutes. RunJob suits teams on GitLab CI or GitHub Actions that want EU-hosted runners billed by actual CPU and memory use instead of by runner size.
What is the difference between GitLab-hosted runners and RunJob?
GitLab-hosted runners is the CI platform’s own hosted runners; RunJob is a managed service hosted by the vendor. Only RunJob documents GitHub Actions. Only GitLab-hosted runners documents macOS and Windows. Only GitLab-hosted runners documents arm64. Isolation is Ephemeral VM on GitLab-hosted runners and KVM virtual machine on RunJob.
Which is open source, GitLab-hosted runners or RunJob?
Neither is open source.
How do GitLab-hosted runners and RunJob isolate jobs?
GitLab-hosted runners: Each job runs in a newly provisioned VM that serves a single job and is deleted right after it; firewall rules block inbound traffic and traffic between VMs. RunJob: 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.
How does GitLab-hosted runners pricing compare with RunJob?
GitLab-hosted runners: No per-minute price is published. Jobs consume compute minutes at job duration times a cost factor: Linux small 1, medium 2, large 3, xlarge 6, 2xlarge 12; GPU 7; macOS M1 6 and M2 Pro 12 (beta); Windows 1 (beta). Additional compute minutes cost $10 per 1,000 minutes as a one-time purchase. RunJob: 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. Rates change, so check the GitLab-hosted runners and RunJob pricing pages before deciding.
Is GitLab-hosted runners or RunJob faster?
We have not benchmarked them, and speed depends on the workload. What each provider says: GitLab-hosted runners: Not documented. RunJob: Puzl says jobs run up to 2x faster and up to 5x cheaper than on other platforms (vendor claim).
Do GitLab-hosted runners and RunJob cache Docker layers?
GitLab-hosted runners: Docker layer caching is not documented. RunJob: No Docker layer caching.
Do GitLab-hosted runners and RunJob offer GPU runners?
GitLab-hosted runners: One GPU machine type on Linux x86-64 for Premium and Ultimate: 4 vCPU, 15 GB RAM and 1 NVIDIA Tesla T4 (or similar) with 16 GB, at cost factor 7. RunJob: 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.
Where do GitLab-hosted runners and RunJob runners run?
GitLab-hosted runners is the CI platform’s own hosted runners. RunJob is a managed service hosted by the vendor.

Sources

  1. docs.gitlab.com/ci/runners/hosted_runners/
  2. docs.gitlab.com/ci/runners/hosted_runners/linux/
  3. docs.gitlab.com/ci/runners/hosted_runners/macos/
  4. docs.gitlab.com/ci/runners/hosted_runners/windows/
  5. runjob.eu/
  6. runjob.eu/docs/introduction
  7. runjob.eu/docs/getting-started
  8. runjob.eu/docs/security

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). GitLab-hosted runners vs RunJob. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/gitlab-hosted-runners-vs-runjob/