# GitLab compute minutes calculator

GitLab.com bills its hosted runners in compute minutes. A job uses its minutes times the runner size's cost factor, from 1 on small to 12 on 2xlarge. Each plan includes some every month; extra minutes are $10 per 1,000, so a 4 vCPU minute costs $0.020.

## Price a month

Enter the job minutes you run on GitLab's hosted runners. Plan seats are not included.

|  | This month |
| --- | --- |
| Compute minutes used | 10,000 (5,000 × 2) |
| Included in Free | 400 |
| Extra minutes to buy, in packs of 1,000 | 10,000 |
| **GitLab.com: extra minutes** | **$100.00** |
| GitLab.com: every minute at the extra price | $100.00 |
| **Groundbox, same size** | **$30.00** |

## How compute minutes are counted

GitLab counts each job's run time in seconds, divides by 60, and multiplies by the cost factor. Time spent waiting in created or pending does not count. Usage is charged to the project's top-level group or user.

| Size | Tag | vCPU, memory | Cost factor | Per job minute | Plans |
| --- | --- | --- | --- | --- | --- |
| small | `saas-linux-small-amd64` | 2 vCPU, 8 GB | 1 | $0.010 | All |
| medium | `saas-linux-medium-amd64` | 4 vCPU, 16 GB | 2 | $0.020 | All |
| large | `saas-linux-large-amd64` | 8 vCPU, 32 GB | 3 | $0.030 | Premium, Ultimate |
| xlarge | `saas-linux-xlarge-amd64` | 16 vCPU, 64 GB | 6 | $0.060 | Premium, Ultimate |
| 2xlarge | `saas-linux-2xlarge-amd64` | 32 vCPU, 128 GB | 12 | $0.120 | Premium, Ultimate |

## Minutes included with each plan

| GitLab plan | Price | Compute minutes a month | Small-runner minutes | Medium-runner minutes |
| --- | --- | --- | --- | --- |
| Free | $0 | 400 | 400 | 200 |
| Premium | $29 per user a month, billed yearly | 10,000 | 10,000 | 5,000 |
| Ultimate | custom pricing | 50,000 | 50,000 | 25,000 |

Public projects in the GitLab for Open Source program use a cost factor of 0.5.

## Worked examples

Extra minutes in packs of 1,000 past the plan's minutes, next to the same job minutes on Groundbox at list price. Groundbox bills by the second.

| Month | Job minutes | Compute minutes | GitLab.com extra minutes | Groundbox |
| --- | --- | --- | --- | --- |
| A small team on Free | 3,000 on 2 vCPU | 3,000 | $30.00 | $9.00 |
| Medium runners on Premium | 10,000 on 4 vCPU | 20,000 | $100.00 | $60.00 |
| Large runners on Premium | 20,000 on 8 vCPU | 60,000 | $500.00 | $220.00 |

Groundbox's free plan covers 3,000 CI minutes a month on any size, plus $5 of usage. The $20 plan includes $20 of usage a month. [Pricing](https://groundbox.dev/pricing) lists every size.

## When compute minutes run out

When a namespace has used its compute minutes for the month, GitLab's instance runners stop taking new jobs. Project and group runners are not affected by the quota. Usage resets to 0 each month.

Jobs on runners you add to a project or group keep running. That is how Groundbox works with GitLab: you connect GitLab, set `tags: [groundbox-4vcpu]` on a job, and it runs in a fresh VM without using compute minutes. Steps: [GitLab CI docs](https://groundbox.dev/docs/gitlab).

## Ways to use fewer compute minutes

- Run jobs on the smallest size that is not slower. A medium job uses twice the compute minutes of a small one, so it is cheaper only if it finishes in under half the time.
- Skip jobs when their files did not change, with `rules: changes:`.
- Mark jobs `interruptible: true` and turn on auto-cancel of redundant pipelines, so a new push stops the old pipeline.
- Use `needs:` so jobs start as soon as what they depend on is done, not when the whole stage is.
- Move the heavy jobs to your own runners or a third-party runner, which do not use compute minutes.

More on executors, registering runners and what self-hosting costs: [GitLab runners: hosted vs self-hosted](https://groundbox.dev/gitlab-runner).

## Questions

### How much do GitLab compute minutes cost?

Extra compute minutes are $10 per 1,000, a one-time payment. A minute on a hosted runner uses as many compute minutes as its size's cost factor: 1 on small, 2 on medium, 3 on large, 6 on xlarge, 12 on 2xlarge. So a minute on a 4 vCPU medium runner costs $0.020.

### How many compute minutes come with each GitLab plan?

On GitLab.com: 400 a month on Free, 10,000 on Premium and 50,000 on Ultimate. They are for GitLab's instance runners, and usage resets each month.

### What happens when GitLab compute minutes run out?

When a namespace has used its compute minutes for the month, GitLab's instance runners stop taking new jobs. Project and group runners are not affected by the quota. Usage resets to 0 each month. You can buy more minutes to keep using the hosted runners until then.

### Do my own runners use GitLab compute minutes?

No. Compute minutes count jobs on GitLab's instance runners. Project and group runners, whether you run them or a provider does, are not affected by the quota.

### What is the GitLab cost factor?

A multiplier for each runner size. Compute minutes used are the job's minutes times the factor: a 10-minute job on a medium runner (factor 2) uses 20 compute minutes. Public projects in the GitLab for Open Source program use a cost factor of 0.5.

### What does a Groundbox runner cost next to GitLab.com?

Per minute, 2 / 4 / 8 / 16 vCPU: $0.010 / $0.020 / $0.030 / $0.060 on GitLab.com at the extra-minutes price, and $0.003 / $0.006 / $0.011 / $0.021 on Groundbox, billed by the second.

## Sources

Checked on 2026-11-20, on each company's own pages. Prices change; their pages are the final word.

- [GitLab: Pricing](https://about.gitlab.com/pricing/)
- [GitLab: Compute minutes](https://docs.gitlab.com/ci/pipelines/compute_minutes/)
- [GitLab: Compute usage for instance runners](https://docs.gitlab.com/ci/pipelines/instance_runner_compute_minutes/)
- [GitLab: Hosted runners on Linux](https://docs.gitlab.com/ci/runners/hosted_runners/linux/)

## Related

- [GitLab runner guide](https://groundbox.dev/gitlab-runner): What a GitLab runner is, the executors, how to install and register GitLab Runner with a glrt- token, tags and concurrency, and what hosted and self-hosted runners cost.
- [GitLab runners](https://groundbox.dev/gitlab-runners): Fast GitLab CI runners: change tags in .gitlab-ci.yml and each job gets a fresh VM, billed by the second, at about a third of GitLab.com's hosted runner price. gitlab.com and self-managed.
- [GitLab CI](https://groundbox.dev/docs/gitlab): Run GitLab CI jobs on Groundbox: connect GitLab or paste a runner token, set tags: [groundbox-4vcpu], and each job gets a fresh VM, billed per second. gitlab.com and self-managed.
- [GitHub Actions cost](https://groundbox.dev/github-actions-cost): How GitHub bills Actions minutes: per-minute prices by runner, included usage per plan, rounding to the minute, and worked monthly examples.
- [Pricing](https://groundbox.dev/pricing): Free: 3,000 CI minutes a month, no card. Paid: $20 a month with $20 of usage included. CI from $0.003 a minute, sandboxes $0.04 per vCPU-hour.

**Try it:** [sign in](https://groundbox.dev/signin) with GitLab, GitHub, Google or email, then open Repos and runners › GitLab. The free plan needs no card.
