GitLab Runners
- Free allowance
- Quoted: 'The base monthly compute quota is determined by your subscription tier.
- Verdict
- fails: identitythe identity required is not reachable without it
- Cost
- free tier
- Identity
- cardcard required, phone required
- Binding limit
- write-gatedQuoted: 'Inbound communication from the public internet to the ephemeral VM is not allowed.' Firewall rules 'only allow outbound communication from the ephemeral VM to the public internet'.; A card gates the free minutes. Quoted...
- Evidence
- documented12 sources; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-11-25checked 2026-10-25 (live); stale on 2026-11-25
| Free tier | Quoted: 'The base monthly compute quota is determined by your subscription tier. Free tier namespaces receive 400 compute minutes per month.' The pricing page repeats it as '400 compute minutes per month'. A compute minute is not a wall-clock minute: the usage formula is 'Job duration / 60 * Cost factor', and the default small Linux x86-64 runner has cost factor 1, so 400 compute minutes is 400 wall-clock minutes on the default shape and less on any larger one. The card requirement is the finding: 'credit/debit card details are required if you choose to use GitLab.com shared runners', verified with 'a one-dollar authorization transaction'.unit minutes; metered on wall-clock; 400 compute minutes at cost factor 1 is 6 hours 40 minutes a month, which is 0.22 hours a day. The card gate is on the shared runners specifically, not on the account. |
|---|---|
| Price | none stated |
| Limits |
Three separate ceilings and the smallest is the card gate: 400 compute minutes a month, a 3-hour job timeout, and a card required to use the shared runners that the minutes are spent on. Bringing your own runner removes the card requirement and the minute quota at the same time, which needs a machine to run the runner on. |
| Binding | write-gated the card is what fails, not the quota: 400 compute minutes is small but the free minutes cannot be reached at all without a payment instrument on file, so the machine is behind an identity gate a user does not want to pass. Even past the card, 400 minutes a month is 6 hours 40 minutes. |
| Identity | card A card, for the thing this record is about. The account itself is free and the pricing page says 'No credit card required' for the Free plan, but the free compute minutes sit behind a card: 'credit/debit card details are required if you choose to use GitLab.com shared runners'. The card is verified by 'a one-dollar authorization transaction' and 'No charge will be made and no money will transfer', so the hold is USD 1.00 authorised and released, not captured. GitLab's identity-verification page adds a second, independent gate that is risk-scored: 'All users - Email verification. Medium-risk users - Phone number verification. High-risk users - Credit card verification.' Whether a new account lands in the medium or high band is not published. Debit acceptance is not stated on any page read; the pages say 'credit/debit card' without distinguishing. |
| Egress | not published on any page read: no egress quota, shaping tier or per-byte price is stated for GitLab.com hosted runners |
| Retention | Quoted: 'Ephemeral runner VMs serve a single job and are deleted right after the job execution.' Nothing on the VM survives the job. |
| Interface | unknown a .gitlab-ci.yml pipeline; a runner with a shell |
| Tooling | a shell on an ephemeral runner; package managers; a checkout |
| Composes with | a real machine for the length of a job and nothing after it |
| Reliability | no reliability event recorded |
| Notes | This corrects the corpus's own record, which said paid-only and identity_cost.kind: email on the strength of the pricing page's 'No credit card required' line. That line is true of the account and false of the thing the record is about. GitLab's own FAQ says the card is required 'if you choose to use GitLab.com shared runners', and shared runners are the only way to spend the 400 minutes without a self-managed runner. So the kind is card, with a USD 1.00 authorisation hold and release. Identity verification on the GitLab free tier is a risk-scored three-stage scheme, and it is documented; separately and unconditionally, the shared runners need a card. Not established: whether a new account from a given country lands in the medium-risk (phone) or high-risk (card) band, because the risk score is not published; and whether a debit or prepaid card passes the one-dollar authorisation, because no page says. |
| Evidence note | documented the 400 minutes, the cost factors, the 2 vCPU / 8 GB / 30 GB shape, the 3-hour job timeout, the inbound block and the card requirement are each quoted from a first-party GitLab page read on 2026-10-24. The card requirement is quoted from about.gitlab.com's own FAQ twice, on the pricing page and on the free-trial page, with the same wording. |
| Parsed numbers |
|
Evidence 12
| date | source | what it proved |
|---|---|---|
| 2026-10-02 | about.gitlab.com/pricing/ | a free tier with a monthly CI minute allowance; the runner is ephemeral per job |
| 2026-10-22 | about.gitlab.com/pricing/ | read live: free tier carries 400 compute minutes a month |
| 2026-10-24 | docs.gitlab.com/ci/pipelines/compute_minutes/ | quoted: 'The base monthly compute quota is determined by your subscription tier. Free tier namespaces receive 400 compute minutes per month. Paid tiers receive a higher monthly quota.' |
| 2026-10-24 | docs.gitlab.com/ci/pipelines/compute_minutes/ | cost-factor table quoted row by row: '| Linux x86-64 (default) | small | 1 |', '| Linux x86-64 | medium | 2 |', 'large | 3', 'xlarge | 6', '2xlarge | 12'; formula quoted: 'Job duration / 60 * Cost factor'. This row is what makes 400 compute minutes 400 wall-clock minutes on the default shape. |
| 2026-10-24 | docs.gitlab.com/ci/runners/hosted_runners/linux/ | quoted shape table: 'saas-linux-small-amd64 (default) | 2 | 8 GB | 30 GB' and 'saas-linux-medium-amd64 | 4 | 16 GB | 50 GB' |
| 2026-10-24 | docs.gitlab.com/ci/runners/hosted_runners/ | quoted: 'Each of your jobs runs in a newly provisioned VM, which is dedicated to the specific job.' and 'Jobs handled by hosted runners on GitLab.com time out after 3 hours, regardless of the timeout configured in a project.' |
| 2026-10-24 | docs.gitlab.com/ci/runners/hosted_runners/ | quoted: 'Firewall rules only allow outbound communication from the ephemeral VM to the public internet.' and 'Inbound communication from the public internet to the ephemeral VM is not allowed.' and 'Ephemeral runner VMs serve a single job and are deleted right after the job execution.' |
| 2026-10-24 | about.gitlab.com/pricing/ | quoted, the card gate: 'credit/debit card details are required if you choose to use GitLab.com shared runners. Credit/debit card details are not required if you bring your own runner or disable shared runners. When you provide the card, it will be verified with a one-dollar authorization transaction. No charge will be made and no money will transfer.' |
| 2026-10-24 | about.gitlab.com/pricing/ | quoted, the Free plan row: 'per user/month, No credit card required' with '5 users per top-level group', '400 compute minutes per month', '10 GiB adjustable storage' |
| 2026-10-24 | about.gitlab.com/free-trial/ | quoted, the same card gate from a second first-party page: 'A credit/debit card is not required for customers who do not use GitLab.com CI/CD, bring their own runners, or disable shared runners. However, credit/debit card details are required if you choose to use GitLab.com shared runners. This change was made to discourage abuse of the free compute minutes provided on GitLab.com to mine cryptocurrencies' |
| 2026-10-24 | docs.gitlab.com/security/identity_verification/ | quoted from the page's opening: 'Depending on your risk score, you might be required to perform up to' then 'three stages of verification to create a user account:' then the list items 'All users - Email verification.', 'Medium-risk users - Phone number verification.', 'High-risk users - Credit card verification.' Also quoted: 'GitLab does not store your card details directly or make any charges.' |
| 2026-10-24 | docs.gitlab.com/ci/pipelines/instance_runner_compute_minutes | quoted: 'When the compute quota is used for the current month, instance runners stop processing new jobs.' and 'Jobs running on instance runners can continue to run until the overall namespace usage goes over-quota by 1,000 compute minutes.' |
More fields 17
{
"shape": {
"vcpu": 2,
"ram_gib": 8,
"disk_gib": 30,
"gpu_class": null,
"gpu_count": null,
"note": "`saas-linux-small-amd64`, the default for untagged jobs. RAM and disk are the vendor's decimal GB, kept unconverted: 8 GB is about 7.5 GiB and 30 GB about 27.9 GiB. Quoted caveat: 'The storage is shared by the operating system, the container image with pre-installed software, and a copy of your cloned repository. This means that the available free disk space for your jobs to use is reduced.'"
},
"billing_model": "free",
"session_cap": {
"wall_clock_min": 180,
"idle_reap_s": null,
"restart_required": true,
"note": "3 hours per job on GitLab.com hosted runners regardless of project setting, then the VM is deleted; 400 compute minutes a month is the other clock and it binds first"
},
"keep_rate": {
"value": 0.0,
"basis": "the VM is deleted after the job and nothing is billed for it",
"source": "https://docs.gitlab.com/ci/runners/hosted_runners/"
},
"persistent_storage": {
"included_gib": 0,
"price_gib_month": "not applicable: nothing on the runner survives",
"durability": "none: the ephemeral VM is deleted right after the job",
"survives_stop": false,
"survives_destroy": false,
"max_retention": "the job"
},
"network_out": {
"allow_outbound": true,
"allow_inbound_listen": false,
"ports": "none inbound: 'Inbound communication from the public internet to the ephemeral VM is not allowed'",
"static_ip": false,
"ipv6": null,
"per_session_bytes": null
},
"free_tier_kind": "allowance",
"topic_note": "belongs to ci-cd-runners",
"granularity": {
"min_billed_s": 60,
"rounding_s": null
},
"burst_x": 1.0,
"term": "none",
"m10h_usd": null,
"m24h_usd": null,
"price_arithmetic": "400 compute minutes / cost factor 1 = 400 wall-clock minutes a month on the 2 vCPU default, which is 6 h 40 min, or 0.22 h a day. 10 h a day x 30 = 300 h needs 18,000 compute minutes, 45 times the quota. 24/7 x 30 = 730 h needs 43,800 compute minutes, 110 times the quota. No USD figure is given because no per-minute price was read on a page.",
"concurrency": {
"jobs_at_once": null,
"note": "not published on any page read: no concurrent-job number for a Free namespace was found. The 400-minute monthly quota is the ceiling that matters at this size."
},
"units": "RAM and disk are the vendor's decimal GB, kept unconverted. 8 GB reads as 8, 30 GB as 30.",
"checked": {
"verified": [
"400 compute minutes a month on the Free tier",
"2 vCPU / 8 GB / 30 GB on the default saas-linux-small-amd64",
"3-hour job timeout on GitLab.com hosted runners",
"inbound is explicitly blocked",
"the ephemeral VM is deleted after the job"
],
"new": "the risk-scored three-stage identity verification (email / phone / card) is documented and is a second, independent gate"
}
}Unknown values 4
$.egress.meteredegress metering was not published$.interfacethe access interface was not established$.per_object_cap.statedthe field does not apply to this kind of offer$.reliability_notenothing of this kind was observed