GitLab

gitlab.com · CI runners, Compute, Storage · 14 records · JSON

GitLab.com container registry Storage★ qualifiesanonymousno cardR
GitLab.com generic package registry Storage★ qualifiesinstitutionno cardRper-object-cap
GitLab Container Registry (gitlab.com) Storage★ qualifiesanonymousno cardR
GitLab Package Registry (generic / npm / Maven / PyPI / NuGet / Conan) Storage★ qualifiesinstitutionno cardRper-object-cap
GitLab CI on GitLab.com Free CI runnerscaveatemailno cardDrequest-rate
GitLab Container Registry CI runnerscaveatemailno cardDrequest-rate
GitLab Computecaveatemailno cardDwrite-gated
GitLab CI Job Artifacts (GitLab.com Free) Storagecaveatemail?card?R
GitLab.com Git LFS Storagecaveatemail?card?R
GitLab.com snippets Storagecaveatemail?card?R
GitLab Snippets / GitLab.com projects Storagecaveatemail?card?R
GitLab Runners Computefails: identitycardcardphoneDwrite-gated
GitLab Pages (gitlab.io) Storagefails: quotaemail?card?R
gitlab pages Storagefails: quotaemail?card?R

GitLab.com container registry Storage

★ qualifiesanonymousno cardR

registry.gitlab.com · registry · storage/gitlab-com-container-registry · JSON · compare

Free tier	No published storage cap. Explicitly excluded from the per-project 10 GiB limit; unlimited container repositories per project is the practical reading. unit GiB; metered on stored-bytes
Price	none stated
Per-object cap	not stated
Retention	not stated
Egress	Free, Cloudflare + Google Cloud CDN. Blob requests 307-redirect to cdn.registry.gitlab-static.net with a signed URL — directly cacheable by an external Cloudflare zone.
Identity	anonymous derived from the record's prose, not from an identity field, and no signup was executed: er repos is blocked. Public pulls are rate-limited loosely; anonymous token issuance works but each pull needs a token round-trip. registry
Binding	none no constraint in the record binds at this scale; the record carries no limit of a kind the vocabulary names
Interface	oci oci
Tooling	Standard OCI Distribution v2. ORAS, skopeo, crane, docker. Auth flow is anonymous for public projects (`/jwt/auth` returns a token with auth_type=none).
Composes with	One OCI artifact per blob of any size -> unlimited projects x unlimited repositories x unlimited tags. This is the canonical 'OCI registry as object store' pattern (ORAS). Blob dedupe means the same chunk stored in N projects costs one copy but is addressable N times.
Reliability	GitLab has run garbage-collection and cleanup-policy tooling against registries since 2023; no automatic purge is documented, but stale-tag cleanup policies are a first-class feature other users may set on shared projects. Own projects are not touched.
Notes	No published storage cap. Explicitly excluded from the per-project 10 GiB limit; unlimited container repositories per project is the practical reading.
Evidence rung	reported One page read moves it to documented.
Checked	2026-10-21 (inherited); stale on 2026-11-04

Evidence (5)

date	source	what it proved
2026-10-21	docs.gitlab.com/user/storage_usage_quotas/	package/container registries excluded from the limit
2026-10-21	registry.gitlab.com/v2/	probe: GET -> 401 with WWW-Authenticate: Bearer realm="https://gitlab.com/jwt/auth",service="container_registry"; Server: cloudflare; gitlab-sv: registry-us-east1-c
2026-10-21	gitlab.com/jwt/auth?service=container_registry&scope=reposit	probe: GET -> 200, JWT with "auth_type":"none" (anonymous pull token, no credentials)
2026-10-21	withheld	probe: GET /v2/gitlab-org/gitlab-runner/manifests/latest with that token -> 200, application/vnd.oci.image.index.v1+json, digest sha256:f1c76f915d7f70d8b3e25cac58da3d87d3d10106dda82ee780409440e1dc1ccc, Server: cloudflare
2026-10-21	cdn.registry.gitlab-static.net/	probe: GET /v2/gitlab-org/gitlab-runner/blobs/sha256:a60ef8ec184edb5ed91f5983f00261359fb2fe20f603e8d488b9477d32fcad70 -> 307 to ... (signed CDN URL, cacheable)

Unknown or withheld values (6)

$.evidence[3].url private-url
$.free_tier.notes process
$.per_object_cap.notes not-extracted
$.per_object_cap.stated not-extracted
$.retention.notes not-extracted
$.retention.stated not-extracted

GitLab.com generic package registry Storage

★ qualifiesinstitutionno cardRper-object-cap

gitlab.com · registry · storage/gitlab-com-generic-package-registry · JSON · compare

Free tier	5 GB maximum per uploaded file (Generic). No per-project or per-namespace package storage cap is documented; the package registry is explicitly excluded from the 10 GiB project storage limit. unit GiB; metered on stored-bytes
Price	none stated
Per-object cap	5 GB maximum per upload (5000000000 bytes)
Retention	Artifacts expire in 30 days, packages do not. (30 days)
Egress	Free and Cloudflare-fronted. GitLab.com is behind Cloudflare and blobs are served from Google Cloud Storage / the GitLab CDN (cdn.registry.gitlab-static.net). No egress billing for public projects.
Identity	institution derived from the record's prose, not from an identity field, and no signup was executed: accounts. 5 GB per file (Generic / Maven / npm / NuGet / PyPI / Conan); 10 GB for ML models (upload capped at 5 GB); 1 GB for Terraform state; Helm only 5 MB. Anonymous read of publ
Limits	per-object-cap 5 GB per file source retention-clamped expire in 30 days source 5 GB per file (Generic / Maven / npm / NuGet / PyPI / Conan); 10 GB for ML models (upload capped at 5 GB); 1 GB for Terraform state; Helm only 5 MB. Anonymous read of public project packages; writes need a token. Repository/LFS Git push limited to 5 GiB per request, irrelevant to packages.
Binding	per-object-cap the per-object cap sets the shard size and therefore the object count; it bounds the total more tightly than any headline quota
Interface	rest, cli rest
Tooling	GitLab REST API v4 (`PUT /projects/:id/packages/generic/:package_name/:version/:file_name`, `GET .../package_files/:id/download`), glab CLI, python-gitlab (has generic package support, merged), goreleaser pushes generic packages natively (PR #2745 merged). Works with plain curl — no special client needed.
Composes with	Unlimited projects per namespace (no project-count cap is documented on GitLab.com; the only new limits are 3 top-level groups for accounts created after 2026-01-27, and the personal namespace does not count). Each project is its own unbounded package bucket at 5 GB/file. N projects x unlimited package versions x 5 GB. Multiply again by additional free namespaces (3 groups + personal) and by unlimited free accounts.
Reliability	Snippets, packages and job artifacts count toward namespace storage as a display/billing figure but are not enforced as a cap — enforcement is per-project on repo+LFS only. GitLab could start enforcing namespace storage at any time; it has never done so for packages. Artifacts expire in 30 days, packages do not.
Notes	5 GB maximum per uploaded file (Generic). No per-project or per-namespace package storage cap is documented; the package registry is explicitly excluded from the 10 GiB project storage limit.
Evidence rung	reported One page read moves it to documented.
Checked	2026-10-21 (inherited); stale on 2026-11-04
Parsed numbers	`$.limits[0].value` limit:per-object-cap 5.0 GB

Evidence (5)

date	source	what it proved
2026-10-21	docs.gitlab.com/user/storage_usage_quotas/	'Only the project's repository and LFS are included in the storage limit. The container registry, package registry, and build artifacts are not included in the limit.' and 'Each project in a Free tier namespace on GitLab.com has 10 GiB of free storage.'
2026-10-21	docs.gitlab.com/user/gitlab_com/	package registry max file size table: 'Generic \| 5 GB'; also 'GitLab.com is fronted by Cloudflare'
2026-10-21	docs.gitlab.com/user/free_user_limit/	top-level group limit of 3 applies only to accounts created after January 27, 2026, and 'Your personal namespace does not count toward this limit'
2026-10-21	gitlab.com/api/v4/projects/gitlab-org%2Fcli/packages/2752497	probe: GET with Range: bytes=0-1023 -> 206 Partial Content, Content-Range: bytes 0-1023/9035444, Server: cloudflare, x-goog-stored-content-length 9035444 (anonymous public-package download, Cloudflare-served, range-capable) — no token sent
2026-10-21	gitlab.com/api/v4/projects/gitlab-org%2Fcli/packages?per_pag	probe: GET -> 200, glab 1.44.1 last_downloaded_at 2026-10-21 (packages API anonymously listable)

Unknown or withheld values (3)

$.free_tier.notes process
$.per_object_cap.notes not-extracted
$.retention.notes not-extracted

GitLab Container Registry (gitlab.com) Storage

★ qualifiesanonymousno cardR

registry.gitlab.com · registry · storage/gitlab-container-registry · JSON · compare

Free tier	Not counted against any storage quota. GitLab docs: 'Only the project's repository and LFS are included in the storage limit. The container registry, package registry, and build artifacts are not included in the limit.' The 10 GiB Free limit therefore does not apply to OCI blobs. unit GiB; metered on stored-bytes
Price	none stated
Per-object cap	not stated
Retention	not stated
Egress	No egress charge is published for gitlab.com registry pulls; anonymous pulls are served without auth beyond a JWT. Effectively unmetered for anonymous public projects.
Identity	anonymous derived from the record's prose, not from an identity field, and no signup was executed: a documented per-file cap. Requires CI or a token for push; anonymous pull works on public projects. registry
Binding	none no constraint in the record binds at this scale; the record carries no limit of a kind the vocabulary names
Interface	oci, rclone oci
Tooling	ORAS / docker / skopeo / crane all work against registry.gitlab.com; rclone has no OCI backend but 'oras cp' + rclone covers push/pull. Public projects allow anonymous pull tokens.
Composes with	Unlimited projects per namespace x unlimited namespaces/accounts x 5 GB per layer (generic package max file is 5 GB; container layers see the same class of limit). Since blobs are outside the 10 GiB project quota, a single free account can host arbitrarily many OCI layers. Compare GHCR (already known) — the differentiator here is the explicit quota exemption, not the registry itself.
Reliability	Storage is reported under 'reduce container registry storage' but no hard cap or eviction is documented on Free; the risk is administrative cleanup of dormant projects rather than quota enforcement.
Notes	Not counted against any storage quota. GitLab docs: 'Only the project's repository and LFS are included in the storage limit. The container registry, package registry, and build artifacts are not included in the limit.' The 10 GiB Free limit therefore does not apply to OCI blobs.
Evidence rung	reported One page read moves it to documented.
Checked	2026-10-21 (inherited); stale on 2026-11-04

Evidence (4)

date	source	what it proved
2026-10-21	docs.gitlab.com/user/storage_usage_quotas/	'Only the project's repository and LFS are included in the storage limit. The container registry, package registry, and build artifacts are not included in the limit.'
2026-10-21	about.gitlab.com/pricing/	'Purchased storage applies to Git repository size and LFS usage. It does not apply to other storage types, such as the container registry.'
2026-10-21	gitlab.com/jwt/auth?service=container_registry&scope=reposit	probe: GET -> {"token":"eyJ..."} anonymous pull token issued with no credentials
2026-10-21	registry.gitlab.com/v2/gitlab-org/gitlab-runner/manifests/la	probe: GET (Bearer token) -> 200, Content-Type: application/vnd.oci.image.index.v1+json, docker-content-digest: sha256:f1c76f91... (real OCI manifest served anonymously)

Unknown or withheld values (5)

$.free_tier.notes process
$.per_object_cap.notes not-extracted
$.per_object_cap.stated not-extracted
$.retention.notes not-extracted
$.retention.stated not-extracted

GitLab Package Registry (generic / npm / Maven / PyPI / NuGet / Conan) Storage

★ qualifiesinstitutionno cardRper-object-cap

gitlab.com · registry · storage/gitlab-package-registry · JSON · compare

Free tier	Explicitly EXCLUDED from the project storage quota. GitLab docs, verbatim: 'GitLab projects have a storage limit for their Git repository and Large File Storage (LFS). Only the project's repository and LFS are included in the storage limit. The container registry, package registry, and build artifacts are not included in the limit.' The 10 GiB figure (pricing page: 'Storage 10 GiB') therefore applies only to git+LFS; package bytes are unquota'd. Per-file ceilings: Generic 5 GB, npm 5 GB, Maven 5 GB, NuGet 5 GB, PyPI 5 GB, Conan 5 GB, Terraform 1 GB, ML model 10 GB (uploads capped at 5 GB), Helm 5 MB. unit GiB; metered on stored-bytes
Price	none stated
Per-object cap	5 GB per file (5000000000 bytes)
Retention	not stated
Egress	Free and unmetered for downloads; no egress line item anywhere in GitLab pricing. Served through Cloudflare (probe returned Server: cloudflare).
Identity	institution derived from the record's prose, not from an identity field, and no signup was executed: ceilings: Generic 5 GB, npm 5 GB, Maven 5 GB, NuGet 5 GB, PyPI 5 GB, Conan 5 GB, Terraform 1 GB, ML model 10 GB (uploads capped at 5 GB), Helm 5 MB. Package registry is a real fea
Limits	per-object-cap 5 GB per file source 5 GB per file (generic). Package registry rate limits apply to the Packages API. Authenticated API traffic 2,000 req/min per user; unauthenticated 60 req/hr per IP. Project creation 200/day/user. No per-project package storage cap documented.
Binding	per-object-cap the per-object cap sets the shard size and therefore the object count; it bounds the total more tightly than any headline quota
Interface	rest, rclone rest
Tooling	Full REST API: PUT /api/v4/projects/:id/packages/generic/:package_name/:version/:file_name and GET the same path for download. Also native npm/maven/pypi/nuget/conan clients by pointing the client at the GitLab URL. No rclone backend, but the generic-package PUT/GET is a two-verb blob API — trivial to drive from curl or a 30-line Python loop. Deploy tokens with write_package_registry scope give scoped push credentials.
Composes with	UNBOUNDED on two axes: (a) unlimited free projects per account (GitLab Free has no project cap; only project creation rate is limited to 200/day/user) x 5 GB per file x unlimited files per project; (b) package bytes sit outside the 10 GiB quota entirely, so a single project is already a de-facto unlimited bucket and additional projects multiply it further. 10 TiB hot = 2,048 x 5 GB generic files, achievable in one project.
Reliability	Package registry is a real feature not a cache — no TTL, but a project cleanup policy can auto-delete package assets if configured, so leave it off. Anonymous pull must be enabled per project ('Allow anyone to pull from package registry'). NuGet group endpoints refuse anonymous pulls entirely.
Notes	Explicitly EXCLUDED from the project storage quota. GitLab docs, verbatim: 'GitLab projects have a storage limit for their Git repository and Large File Storage (LFS). Only the project's repository and LFS are included in the storage limit. The container registry, package registry, and build artifacts are not included in the limit.' The 10 GiB figure (pricing page: 'Storage 10 GiB') therefore applies only to git+LFS; package bytes are unquota'd. Per-file ceilings: Generic 5 GB, npm 5 GB, Maven 5 GB, NuGet 5 GB, PyPI 5 GB, Conan 5 GB, Terraform 1 GB, ML model 10 GB (uploads capped at 5 GB), Helm 5 MB.
Evidence rung	reported One page read moves it to documented.
Checked	2026-10-21 (inherited); stale on 2026-11-04
Parsed numbers	`$.limits[0].value` limit:per-object-cap 5.0 GB

Evidence (5)

date	source	what it proved
2026-10-21	docs.gitlab.com/user/storage_usage_quotas/	'the container registry, package registry, and build artifacts are not included in the limit'; 'Each project in a Free tier namespace on GitLab.com has 10 GiB of free storage'
2026-10-21	docs.gitlab.com/user/gitlab_com/	per-format max file size table (Generic 5 GB, npm 5 GB, ML model 10 GB)
2026-10-21	gitlab.com/api/v4/projects/34675721/packages/generic/glab/1.	probe: GET (no auth) -> 200 OK, Content-Length: 9035444, Content-Type: application/gzip, Server: cloudflare
2026-10-21	gitlab.com/api/v4/projects/gitlab-org%2Fcli/packages	probe: GET (no auth) -> 200 OK, JSON listing packages
2026-10-21	docs.gitlab.com/user/packages/generic_packages/	'To interact with the package registry, you must authenticate' for upload; download paths documented as GET

Unknown or withheld values (4)

$.free_tier.notes process
$.per_object_cap.notes not-extracted
$.retention.notes not-extracted
$.retention.stated not-extracted

GitLab CI on GitLab.com Free CI runners

caveatemailno cardDrequest-rate

docs.gitlab.com/ci/pipelines/compute_minutes/ · CI runner · ci-cd-runners/gitlab-ci · JSON · compare

Free tier	400 compute minutes a month per namespace; 5 users per top-level group; 10 GiB of repository storage unit minutes; metered on wall-clock
Price	none stated
Per-object cap	no published per-job cap on the small Linux runner; the binding limit is the monthly pool and the cost factor
Retention	artifacts expire per job configuration, default 30 days; compute minutes reset on the first of the month (30 days)
Egress	the container registry is excluded from the namespace storage quota; storage beyond the purchased amount is billed free_allowance: 10 GiB per namespace
Identity	email email signup; identity verification is required for some namespaces
Limits	request-rate 400 compute minutes a month on Free; a job consumes duration divided by 60 times the cost factor source request-rate cost factor 1 for small Linux, 2 for medium, 3 for large, 6 for xlarge, 12 for 2xlarge, 6 for macOS M1 source per-object-cap 10 GiB of repository storage per namespace source a 1,000-minute grace period exists before jobs are dropped when the quota is exceeded; the 300,000-minute cap applies only to the community-contribution programme
Binding	request-rate
Interface	git, cli a .gitlab-ci.yml pipeline; instance runners on GitLab.com; self-managed runners are free of the vendor cap
Tooling	the runner images; any shell; docker-in-docker on the Linux runners
Composes with	the only free pool here with a cost-factor discount that makes open-source work cheaper: 0.5 for a GitLab-for-Open-Source project and 0.008 for a public fork of one
Reliability	no reliability event recorded
Notes	400 minutes is 6.7 hours, and a medium runner halves that. The open-source discount is the interesting part and it needs the project to be accepted into the programme, which is a review.
Evidence rung	documented the compute-minutes doc and the storage-quota doc were read today.
Checked	2026-10-23 (live); stale on 2026-11-22
Parsed numbers	`$.limits[2].value` limit:per-object-cap 10.0 GiB

Evidence (2)

date	source	what it proved
2026-10-22	docs.gitlab.com/ci/pipelines/compute_minutes/	'Free tier namespaces receive 400 compute minutes per month'; cost factors small 1, medium 2, large 3, xlarge 6, 2xlarge 12; public projects in GitLab for Open Source 0.5 and public forks 0.008; usage resets on the first day of the month
2026-10-22	docs.gitlab.com/user/storage_usage_quotas/	the container registry is excluded from the namespace repository quota

Unknown or withheld values (1)

$.reliability_note none-observed

GitLab Container Registry CI runners

caveatemailno cardDrequest-rate

docs.gitlab.com/user/storage_usage_quotas/ · container registry · ci-cd-runners/gitlab-container-registry · JSON · compare

Free tier	the registry is excluded from the 10 GiB namespace repository quota; no separate free cap is published unit unlimited; metered on stored-bytes
Price	none stated
Per-object cap	no separate published cap; storage above the namespace's purchased amount is billed
Retention	tags expire per the project's cleanup policy if one is configured; nothing expires by default
Egress	no egress charge is published; storage is what is metered
Identity	email a GitLab account
Limits	per-object-cap storage above the namespace purchased amount is billed; the registry is excluded from the 10 GiB repository quota source the 10 GiB figure that circulates is the repository quota and not the registry quota; the two are different limits and the comparison literature conflates them
Binding	request-rate
Interface	oci, rest the OCI distribution API at registry.gitlab.com; docker login with a deploy token or CI job token
Tooling	docker, podman, skopeo
Composes with	the only free registry here that does not count image layers against the same quota as the code
Reliability	no reliability event recorded
Notes	An exclusion is not an allowance. The doc says the registry does not count against 10 GiB; it does not say the registry is free, and no separate free figure is published.
Evidence rung	documented the storage-quota doc was read today and states the exclusion.
Checked	2026-10-23 (live); stale on 2026-11-22
Parsed numbers	`$.limits[0].value` limit:per-object-cap 10.0 GiB

Evidence (1)

date	source	what it proved
2026-10-22	docs.gitlab.com/user/storage_usage_quotas/	the container registry is excluded from the namespace repository storage quota

Unknown or withheld values (1)

$.reliability_note none-observed

GitLab Compute

caveatemailno cardDwrite-gated

about.gitlab.com/solutions/open-source/join/ · CI runner · compute/gitlab · JSON · compare

Free tier	Quoted: 'Enroll in the GitLab for Open Source Program and receive features of GitLab Ultimate ..., including 50,000 compute minutes calculated at a program-specific cost factor.' Quoted from the compute-minutes page: 'Public projects in the GitLab for Open Source program' cost factor '0.5', '1 minute per 2 minutes of job time'. Quoted from the GPU runner page: 'Tier: Premium, Ultimate' with a single machine type of 4 vCPU, 15 GB, 50 GB disk and '1 NVIDIA Tesla T4 (or similar)' at 16 GB GPU memory. The default Linux runner is 2 vCPU / 8 GB / 30 GB; medium is 4 vCPU / 16 GB / 50 GB. unit minutes; metered on wall-clock; reviewed-programme-grant
Price	none stated
Per-object cap	not applicable
Retention	not applicable
Egress	not stated
Identity	email not published
Limits	write-gated not published source
Binding	write-gated
Interface	unknown inferred from the tooling the provider documents; not probed
Tooling	not stated
Composes with	This is the only free lane in the survey that reaches a GPU through a CI system at a published price of zero: the OSS grant is Ultimate, and Ultimate unlocks the saas-linux-medium-amd64-gpu-standard T4 runner, so a reviewed open-source namespace composes into about 1,667 GPU-hours a month on the literal reading of the docs, or 238 GPU-hours if the programme factor and the runner factor multiply instead of substituting.
Reliability	no reliability event recorded
Notes	The largest free-GPU number found, and it depends on one ambiguity I could not close. The docs formula is job duration divided by 60 times the cost factor, with project type and runner type in separate tables, and the project table says OSS public projects cost 0.5 with no runner qualifier. Read literally the GPU job also costs 0.5, so 50,000 divided by 0.5 is 100,000 job-minutes, or 1,667 GPU-hours a month. If instead the two factors multiply, 50,000 divided by 3.5 is 14,285 GPU-minutes, or 238 GPU-hours. The two readings differ by a factor of seven and only a run would settle it, which needs programme acceptance first. Recorded conservatively here and generously in the offer field, with the ambiguity stated rather than resolved. Also note this is not a same-shape substitute for GitHub: the default runner is 2 vCPU against GitHub's 4, a job is capped at 60 minutes against GitHub's 360, and the grant is a monthly pool rather than unlimited time.
Evidence rung	documented
Checked	2026-10-22 (live); stale on 2026-11-21

Evidence (6)

date	source	what it proved
2026-10-22	about.gitlab.com/solutions/open-source/join/	receive features of GitLab Ultimate including 50,000 compute minutes at a program-specific cost factor; requirements are an OSI-approved licence on every project in the namespace, no profit-seeking, and public visibility; membership must be renewed annually
2026-10-22	docs.gitlab.com/ci/pipelines/compute_minutes/	Free tier namespaces receive 400 compute minutes per month; project-type discount table: public projects in the GitLab for Open Source program cost factor 0.5, public forks of them 0.008, standard projects 1; runner cost factors small 1, medium 2, large 3, xlarge 6, 2xlarge 12, GPU standard 7, macOS M1 6
2026-10-22	docs.gitlab.com/ci/runners/hosted_runners/gpu_enabled/	Tier: Premium, Ultimate; one GPU machine type saas-linux-medium-amd64-gpu-standard at 4 vCPU, 15 GB, 50 GB and one NVIDIA Tesla T4 with 16 GB
2026-10-22	docs.gitlab.com/ci/runners/hosted_runners/linux/	saas-linux-small-amd64 is the untagged default at 2 vCPU, 8 GB, 30 GB; medium is 4 vCPU, 16 GB, 50 GB; large and above are Premium and Ultimate only
2026-10-22	docs.gitlab.com/administration/cicd/limits/	The default maximum time that jobs can run for is 60 minutes, settable per project between 10 minutes and 1 month
2026-10-22	gitlab.com/gitlab-org/gitlab/-/work_items/351933	the 0.5 factor was introduced because projects migrating to the OSS plan were using more than 50,000 minutes per month, where 50,000 is the OSS and Ultimate monthly limit

More fields (1)

{
 "wave2": {
  "class": "ci-runner-capacity",
  "free_tier_kind": "reviewed-programme-grant",
  "shape": {
   "vcpu": 2,
   "ram_gib": 8,
   "gpu_class": "T4",
   "gpu_count": 1
  }
 }
}

Unknown or withheld values (13)

$.binding_note withheld
$.egress.metered egress-unknown
$.egress.terms not-stated
$.identity_cost.detail process
$.interface interface-unknown
$.limits[0].value withheld
$.limits_note withheld
$.per_object_cap.notes process
$.per_object_cap.stated not-applicable
$.reliability_note none-observed
$.retention.notes process
$.retention.stated not-applicable
$.tooling not-stated

GitLab CI Job Artifacts (GitLab.com Free) Storage

caveatemail?card?R

gitlab.com · paas · storage/gitlab-ci-job-artifacts · JSON · compare

Free tier	Not counted against the 10 GiB project storage limit ('build artifacts are not included in the limit'). 1 GB compressed maximum per artifact archive on GitLab.com. unit GiB; metered on stored-bytes
Price	none stated
Per-object cap	not stated
Retention	Default expiry 30 days, but `expire_in: never` is a valid documented value and the latest-successful-job artifact on every ref is exempt from expiry entirely (30 days)
Egress	Free, anonymous for public projects. Verified a 321 MB anonymous download.
Identity	email (placeholder) not published
Binding	none no constraint in the record binds at this scale; the record carries no limit of a kind the vocabulary names
Interface	rest rest
Tooling	GET /projects/:id/jobs/artifacts/:ref/download?job=NAME, and GET /projects/:id/jobs/:job_id/artifacts (zip). No auth needed against a public project. Upload is automatic from .gitlab-ci.yml `artifacts:`.
Composes with	Unlimited jobs per project x 1 GB per artifact archive, uncounted against quota. Force permanence with `expire_in: never` or the 'Keep' button. Because 'artifacts from the latest pipeline for the ref' never expire regardless of expire_in, every branch/tag becomes a permanent shelf: unlimited branches x 1 GB.
Reliability	Expiry is enforced hourly and irreversible — anything not pinned with `never`/Keep silently vanishes. Treat as durable only when pinned.
Notes	Not counted against the 10 GiB project storage limit ('build artifacts are not included in the limit'). 1 GB compressed maximum per artifact archive on GitLab.com.
Evidence rung	reported One page read moves it to documented.
Checked	2026-10-21 (inherited); stale on 2026-11-04

Evidence (3)

date	source	what it proved
2026-10-21	docs.gitlab.com/ci/yaml/	'artifacts:expire_in ... Valid values include ... never' and 'expire_in does not affect artifacts from the latest job'
2026-10-21	docs.gitlab.com/user/gitlab_com/	'Artifacts maximum size (compressed) \| 1 GB' and 'Artifacts expiry time \| 30 days unless otherwise specified'
2026-10-21	gitlab.com/api/v4/projects/gitlab-org%2Fgitlab-foss/jobs/art	probe: curl -L -> 302 then 200, 321472291 bytes, no auth

Unknown or withheld values (6)

$.free_tier.notes process
$.identity_cost.detail defaulted
$.identity_cost.kind identity-defaulted
$.per_object_cap.notes not-extracted
$.per_object_cap.stated not-extracted
$.retention.notes not-extracted

GitLab.com Git LFS Storage

caveatemail?card?R

gitlab.com · registry · storage/gitlab-com-git-lfs · JSON · compare

Free tier	10 GiB free storage PER PROJECT on the Free tier, and that 10 GiB explicitly covers 'the project's repository and Large File Storage (LFS)'. Premium/Ultimate: 500 GiB per project. CONFIRMED: LFS is IN the quota while containers, packages, build artifacts, snippets, uploads and wikis are OUT. unit GiB; metered on stored-bytes
Price	none stated
Per-object cap	not stated
Retention	not stated
Egress	Unmetered — GitLab does not bill or publish any LFS bandwidth quota. The only transfer-side control is a rate limit: 'Git LFS requests are subject to authenticated web request rate limits ... 1000 requests per minute per user. Each Git LFS object uploaded or downloaded generates an HTTP request'.
Identity	email (placeholder) not published
Binding	none no constraint in the record binds at this scale; the record carries no limit of a kind the vocabulary names
Interface	rest, git git
Tooling	git-lfs. Also Oras-style raw access is not available; LFS is protocol-only. GitLab REST API v4 for project/namespace management (useful for automating project-per-shard).
Composes with	10 GiB per PROJECT, and projects are free and unlimited within a namespace — GitLab's own excess-storage example totals 30 GiB across three projects with no namespace-level cap. 50 projects = 500 GiB, 100 = 1 TiB. This is the cleanest 'trivially repeatable' LFS case because each project is an independent 10 GiB bucket behind the same account, unlike GitHub where the 10 GiB is per account.
Reliability	Read-only state is reversible only by purchasing storage, so a blown project is stuck. The 1000 req/min limit bites hard on many-small-files datasets during clone, and GitLab's own docs warn multi-file projects 'may encounter an HTTP rate limit error' in CI.
Notes	10 GiB free storage PER PROJECT on the Free tier, and that 10 GiB explicitly covers 'the project's repository and Large File Storage (LFS)'. Premium/Ultimate: 500 GiB per project. CONFIRMED: LFS is IN the quota while containers, packages, build artifacts, snippets, uploads and wikis are OUT.
Evidence rung	reported One page read moves it to documented.
Checked	2026-10-21 (inherited); stale on 2026-11-04

Evidence (5)

date	source	what it proved
2026-10-21	docs.gitlab.com/user/storage_usage_quotas/	'Only the project's repository and LFS are included in the storage limit. The container registry, package registry, and build artifacts are not included' + 'Each project in a Free tier namespace on GitLab.com has 10 GiB of free storage'
2026-10-21	docs.gitlab.com/administration/settings/account_and_limit_se	'It includes repository files and Git LFS objects (even when stored in external object storage), but does not include: Artifacts, Containers, Packages, Snippets, Uploads, Wikis'
2026-10-21	docs.gitlab.com/rate_limits/git/	'1000 requests per minute per user' for LFS
2026-10-21	docs.gitlab.com/user/gitlab_com/	'Repository size including LFS \| 10 GB'; 'Maximum push size \| 5 GiB'
2026-10-21	gitlab.com/gitlab-org/gitlab.git/info/lfs/objects/batch	probe: POST -> HTTP 200

Unknown or withheld values (7)

$.free_tier.notes process
$.identity_cost.detail defaulted
$.identity_cost.kind identity-defaulted
$.per_object_cap.notes not-extracted
$.per_object_cap.stated not-extracted
$.retention.notes not-extracted
$.retention.stated not-extracted

GitLab.com snippets Storage

caveatemail?card?R

docs.gitlab.com/user/snippets/ · registry · storage/gitlab-com-snippets · JSON · compare

Free tier	No documented per-snippet storage cap; snippets are git-backed and unlimited in count, but contribute to namespace storage accounting unit unlimited; metered on stored-bytes
Price	none stated
Per-object cap	not stated
Retention	not stated
Egress	Free, Cloudflare-fronted like all of GitLab.com; snippets are cloneable and downloadable via API.
Identity	email (placeholder) not published
Binding	none no constraint in the record binds at this scale; the record carries no limit of a kind the vocabulary names
Interface	git, cli git
Tooling	Snippets API (POST /snippets), git clone of the snippet repo, glab CLI, VS Code extension. Rate limited to 300 creates/hour/authenticated user.
Composes with	Snippets are versioned git repos -> unlimited snippets x unlimited versions. The 300/hour creation limit is the only throttle, which is trivially high for a bulk loader. Storage counts toward namespace storage but is NOT enforced.
Reliability	Snippets are visible/searchable by other users when public; storage is accounted at namespace level so it is the most likely subject to be capped first if GitLab ever enforces namespace quotas.
Notes	No documented per-snippet storage cap; snippets are git-backed and unlimited in count, but contribute to namespace storage accounting
Evidence rung	reported One page read moves it to documented.
Checked	2026-10-21 (inherited); stale on 2026-11-04

Evidence (3)

date	source	what it proved
2026-10-21	docs.gitlab.com/user/storage_usage_quotas/	'The cost factor applies to the project repository, LFS objects, job artifacts, packages, snippets, and the wiki' (snippets are namespace-accounted)
2026-10-21	docs.gitlab.com/api/snippets/	'Creating snippets is rate limited to 300 requests every hour for each authenticated user'
2026-10-21	docs.gitlab.com/user/snippets/	'They can contain multiple files', 'use version control', 'clone ... and download'

Unknown or withheld values (7)

$.free_tier.notes process
$.identity_cost.detail defaulted
$.identity_cost.kind identity-defaulted
$.per_object_cap.notes not-extracted
$.per_object_cap.stated not-extracted
$.retention.notes not-extracted
$.retention.stated not-extracted

GitLab Snippets / GitLab.com projects Storage

caveatemail?card?R

gitlab.com · paas · storage/gitlab-snippets-gitlab-com-projects · JSON · compare

Free tier	10 GiB free storage per project on GitLab.com Free tier (repo + LFS); snippet files up to 50 MB each (50,000,000-byte default admin limit); projects per account and accounts are free. unit GiB; metered on stored-bytes
Price	none stated
Per-object cap	not stated
Retention	not stated
Egress	unmetered, served from gitlab.com; no egress line item exists on any GitLab.com plan.
Identity	email (placeholder) not published
Binding	none no constraint in the record binds at this scale; the record carries no limit of a kind the vocabulary names
Interface	rest, git, rclone, cli git
Tooling	glab CLI (glab snippet create), VS Code extension, REST /api/v4/snippets, plain git clone/push for project repos. rclone has a 'gitlab' backend (yes — rclone supports GitLab as a Git remote type via backend 'git').
Composes with	10 GiB free per project x unlimited projects per free account x unlimited free accounts. Snippets add a parallel 50 MB-per-object path that does not require a project. 10 TiB hot = ~1000 projects at 10 GiB, spread over accounts.
Reliability	Read-only lockout is automatic and immediate on exceeding 10 GiB, and it blocks pushes rather than deletes data. Snippets are counted in namespace storage, so they are not a separate free pool.
Notes	10 GiB free storage per project on GitLab.com Free tier (repo + LFS); snippet files up to 50 MB each (50,000,000-byte default admin limit); projects per account and accounts are free.
Evidence rung	reported One page read moves it to documented.
Checked	2026-10-21 (inherited); stale on 2026-11-04

Evidence (4)

date	source	what it proved
2026-10-21	docs.gitlab.com/user/storage_usage_quotas/	'Each project in a Free tier namespace on GitLab.com has 10 GiB of free storage', 'the project is set to a read-only state'
2026-10-21	docs.gitlab.com/administration/snippets/	'The default limit is 52428800 bytes (50 MB)'
2026-10-21	about.gitlab.com/pricing/	Free tier: '10 GiB adjustable storage'
2026-10-21	gitlab.com/api/v4/snippets/public?per_page=2	probe: GET -> {"message":"401 Unauthorized"} (authenticated endpoints only; public snippet read via web returned 200)

Unknown or withheld values (7)

$.free_tier.notes process
$.identity_cost.detail defaulted
$.identity_cost.kind identity-defaulted
$.per_object_cap.notes not-extracted
$.per_object_cap.stated not-extracted
$.retention.notes not-extracted
$.retention.stated not-extracted

GitLab Runners Compute

fails: identitycardcardphoneDwrite-gated

docs.gitlab.com/ci/pipelines/compute_minutes/ · CI runner · compute/gitlab-runners · JSON · compare

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
Per-object cap	not applicable
Retention	Quoted: 'Ephemeral runner VMs serve a single job and are deleted right after the job execution.' Nothing on the VM survives the job.
Egress	not published on any page read: no egress quota, shaping tier or per-byte price is stated for GitLab.com hosted runners
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.
Limits	volume-quota 400 compute minutes a month on the Free tier, with a cost factor of 1 on the default `small` Linux x86-64 runner, 2 on `medium`, 3 on `large`, 6 on `xlarge`, 12 on `2xlarge` source retention-clamped Quoted: 'Jobs handled by hosted runners on GitLab.com time out after 3 hours, regardless of the timeout configured in a project.' source write-gated Quoted: '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'. source write-gated A card gates the free minutes. Quoted: '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.' Verified by 'a one-dollar authorization transaction. No charge will be made and no money will transfer.' source volume-quota On quota exhaustion, instance runners stop processing new jobs; running jobs continue until the namespace is over quota by 1,000 compute minutes, then they are dropped source 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 is not an option for a client with no hardware.
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 the client does not want to pass. Even past the card, 400 minutes a month is 6 hours 40 minutes.
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 a client with no hardware can spend the 400 minutes. So the kind is `card`, with a USD 1.00 authorisation hold and release. This is the answer to the operator's question about whether GitLab's free tier now requires identity verification: the risk-scored three-stage scheme exists and is documented, and 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. The corpus's earlier `400 minutes` figure was right and is confirmed.
Evidence rung	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.
Checked	2026-10-25 (live); stale on 2026-11-24
Parsed numbers	`$.limits[1].value` limit:retention-clamped 3.0 hours

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 (18)

{
 "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; recorded here to stop the double count",
 "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 today.",
 "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.",
 "census_rows": [
  "gitlab-runners"
 ],
 "wave3": {
  "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"
  ],
  "corrected": "verdict paid-only -> fails-identity, and identity_cost.kind email -> card. The card is required for GitLab.com shared runners, which is the only way to reach the free minutes without hardware.",
  "new": "the risk-scored three-stage identity verification (email / phone / card) is documented and is a second, independent gate"
 }
}

Unknown or withheld values (5)

$.egress.metered egress-unknown
$.interface interface-unknown
$.per_object_cap.notes process
$.per_object_cap.stated not-applicable
$.reliability_note none-observed

GitLab Pages (gitlab.io) Storage

fails: quotaemail?card?R

gitlab.com/groups/pages · git · storage/gitlab-pages · JSON · compare

Free tier	1 GB maximum site size on gitlab.com (tied to the 1 GB max artifact size); 200,000 file entries per site; unlimited projects. unit objects; metered on unstated
Price	none stated
Per-object cap	not stated
Retention	not stated
Egress	No egress charge published; rate limits are 1,000 requests/50s per IP and 5,000 requests/10s per Pages domain — generous enough for real serving but a hard ceiling if sharded heavily onto one domain.
Identity	email (placeholder) not published
Binding	none no constraint of a named kind was recorded; the verdict rests on the quota sentence rather than on a named limit
Interface	git, rclone git
Tooling	git push + a `pages` job in .gitlab-ci.yml (a 'pages' artifact); the git-pages v2 API also accepts a direct HTTP upload. No rclone backend.
Composes with	1 GB x unlimited projects x unlimited namespaces. 20 TiB = 20,480 projects. Per-project cap is 2x GitHub Pages but still fails a 500 GB unit test on its own.
Reliability	Self-managed default is a 100 MB Pages cap, but gitlab.com is 1 GB — do not confuse the two. CI minutes are free but shared runners now require a card on file for gitlab.com.
Notes	1 GB maximum site size on gitlab.com (tied to the 1 GB max artifact size); 200,000 file entries per site; unlimited projects.
Evidence rung	reported One page read moves it to documented.
Checked	2026-10-21 (inherited); stale on 2026-11-04

Evidence (4)

date	source	what it proved
2026-10-21	docs.gitlab.com/user/gitlab_com/	'Maximum site size \| 1 GB', 'The maximum size of your Pages site depends on the maximum artifact size'
2026-10-21	docs.gitlab.com/administration/instance_limits/	'total number of file entries (including directories and symlinks) is limited to 200,000 per GitLab Pages website'
2026-10-21	docs.gitlab.com/user/gitlab_com/rate_limits/	'GitLab Pages requests for an IP address \| 1,000 requests every 50 seconds'
2026-10-21	gitlab-org.gitlab.io/gitlab-pages/	probe: curl -D - -> HTTP 302 chain, Server: cloudflare (live serving path)

More fields (1)

{
 "dead_end": {
  "failure_class": "quota",
  "why": "1 GB maximum site size on gitlab.com (tied to the 1 GB max artifact size); 200,000 file entries per site; unlimited projects.",
  "retry_when": null,
  "first_recorded": "2026-10-21"
 }
}

Unknown or withheld values (8)

$.extras.dead_end.retry_when process
$.free_tier.notes process
$.identity_cost.detail defaulted
$.identity_cost.kind identity-defaulted
$.per_object_cap.notes not-extracted
$.per_object_cap.stated not-extracted
$.retention.notes not-extracted
$.retention.stated not-extracted

gitlab pages Storage

fails: quotaemail?card?R

docs.gitlab.com/user/gitlab_com/ · rejected-provider · storage/gitlab-pages-2 · JSON · compare

Free tier	Hard 1 GB maximum site size on GitLab.com regardless of tier, plus a 200,000 file-entry cap and a 150 custom-domain cap. The 1 GB limit is a product-wide constant that an open GitLab issue a unit none; metered on none
Price	none stated
Per-object cap	not recorded
Retention	not recorded
Egress	not recorded
Identity	email (placeholder) not published
Binding	none no constraint of a named kind was recorded; the verdict rests on the quota sentence rather than on a named limit
Interface	unknown
Tooling	not recorded
Composes with	not recorded
Reliability	Hard 1 GB maximum site size on GitLab.com regardless of tier, plus a 200,000 file-entry cap and a 150 custom-domain cap. The 1 GB limit is a product-wide constant that an open GitLab issue a
Notes	Hard 1 GB maximum site size on GitLab.com regardless of tier, plus a 200,000 file-entry cap and a 150 custom-domain cap. The 1 GB limit is a product-wide constant that an open GitLab issue a
Evidence rung	reported
Checked	2026-10-21 (inherited); stale on 2026-11-04

Evidence (3)

date	source	what it proved
2026-10-21	docs.gitlab.com/user/gitlab_com/	Hard 1 GB maximum site size on GitLab.com regardless of tier, plus a 200,000 file-entry cap and a 150 custom-domain cap. The 1 GB limit is a product-wide constant that an open GitLab issue a
2026-10-21	docs.gitlab.com/administration/instance_limits/	cited as the basis of the rejection: Hard 1 GB maximum site size on GitLab.com regardless of tier, plus a 200,000 file-entry cap and a 150 custom-domain cap. The 1 GB limit is a product-wide constant that an open GitLab issue a
2026-10-21	gitlab.com/gitlab-org/gitlab/-/issues/426601	cited as the basis of the rejection: Hard 1 GB maximum site size on GitLab.com regardless of tier, plus a 200,000 file-entry cap and a 150 custom-domain cap. The 1 GB limit is a product-wide constant that an open GitLab issue a

More fields (1)

{
 "dead_end": {
  "failure_class": "quota",
  "why": "Hard 1 GB maximum site size on GitLab.com regardless of tier, plus a 200,000 file-entry cap and a 150 custom-domain cap. The 1 GB limit is a product-wide constant that an open GitLab issue a",
  "retry_when": null,
  "first_recorded": "2026-10-21"
 }
}

Unknown or withheld values (15)

$.chaining not-recorded
$.confidence_note withheld
$.egress.terms not-recorded
$.extras.dead_end.retry_when process
$.free_tier.notes process
$.identity_cost.detail defaulted
$.identity_cost.kind identity-defaulted
$.interface interface-unknown
$.interface_detail withheld
$.limits_note process
$.per_object_cap.notes not-recorded
$.per_object_cap.stated not-recorded
$.retention.notes process
$.retention.stated not-recorded
$.tooling not-recorded