fshy

Home / GitLab

gitlab pages

docs.gitlab.com/user/gitlab_com/storage/gitlab-pages-2JSONcomparereport an errorprovider JSON

Free allowance
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.
Verdict
fails: quotathe free allowance is too small to matter
Cost
not stated
Identity
email?placeholder, not evidence; card unknown, phone unknown
Binding limit
noneno named constraint binds
Evidence
reported3 sources; a third party said so
Freshness
stale on 2026-11-05checked 2026-10-21 (inherited); stale on 2026-11-05
Free tierHard 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…
unit none; metered on none
Pricenone stated
Identityemail (placeholder) not published
Egressnot recorded
Interfaceunknown
Toolingnot recorded
Evidence 3
datesourcewhat it proved
2026-10-21docs.gitlab.com/user/gitlab_com/the text of Free tier, above
2026-10-21docs.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-21gitlab.com/gitlab-org/gitlab/-/issues/426601cited 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…","retry_when": null,"first_recorded": "2026-10-21"}
Unknown values 7
  • chaining: no value was recorded for this field
  • egress terms: no value was recorded for this field
  • interface: the access interface was not established
  • per object cap notes: no value was recorded for this field
  • per object cap stated: no value was recorded for this field
  • retention stated: no value was recorded for this field
  • tooling: no value was recorded for this field