GitLab Pages logo

GitLab Pages

GitLab Inc. · 🌐 Static Hosting

GitLab Pages publishes static websites directly from GitLab repositories using GitLab CI/CD pipelines.

Category
Static Hosting
Free tier
Available
Paid from
$29/user/month
Verified
2026-07-09

Overview

GitLab Pages publishes static websites from a GitLab repository through GitLab CI/CD. A pipeline builds the project, marks a Pages job, and GitLab serves the resulting files from a gitlab.io URL or a custom domain. It fits naturally when your source code, merge requests and deployment workflow already live in GitLab.

The free tier is tied to GitLab.com Free rather than a separate Pages plan. Current official pricing lists 400 compute minutes per month and 10 GiB project storage, while GitLab.com Pages settings list a 1 GB maximum site size. Default GitLab Pages domains are HTTPS-enabled, and custom domains can use SSL/TLS certificates.

GitLab Pages is best for documentation, open source sites, portfolios and static front ends that benefit from a CI/CD pipeline. It is not a serverless application platform: dynamic server-side processing is out of scope, and heavy build workflows can exhaust the free compute-minute allowance.

Pros

  • βœ“Built into GitLab projects, merge requests and CI/CD pipelines
  • βœ“Works with any static site generator or plain HTML, CSS, JavaScript and Wasm
  • βœ“Default gitlab.io domains are served over HTTPS
  • βœ“Supports custom domains, TLS certificates and access control

Cons

  • βœ•Free GitLab.com builds share the 400 compute minutes monthly allowance
  • βœ•GitLab.com Pages sites have a 1 GB maximum site size
  • βœ•No server-side runtime for dynamic PHP, ASP or long-running back ends
  • βœ•Less frontend-platform polish than Netlify or Vercel

Best for

  • β†’Project documentation hosted next to source code
  • β†’GitLab-first teams that want CI/CD-driven static deploys
  • β†’Open source projects, portfolios and simple marketing sites

Compare with

Getting started

  1. 1 Create or open a GitLab project
  2. 2 Add your static site source and a .gitlab-ci.yml pipeline
  3. 3 Configure a job with pages: true and publish the built output
  4. 4 Run the pipeline and open the generated gitlab.io URL
  5. 5 Optionally add a custom domain and TLS certificate

Related guides

Features

  • βœ“GitLab CI/CD deployments
  • βœ“Custom domains
  • βœ“HTTPS support
  • βœ“Access Control
  • βœ“Any static site generator
  • βœ“Parallel deployments

Frameworks

AstroHugoJekyllGatsbyNext.jsReactVue

FAQ

Is GitLab Pages free?

Yes. GitLab Pages is available on GitLab's Free tier and runs on GitLab-provided infrastructure at no additional cost, but builds consume the GitLab.com compute-minute allowance.

What are the main free-tier limits?

On GitLab.com Free, the pricing page lists 400 compute minutes per month and 10 GiB project storage. GitLab.com settings list a 1 GB maximum Pages site size.

Can GitLab Pages run server-side code?

No. GitLab Pages is for static output such as HTML, CSS, JavaScript and Wasm. Dynamic server-side processing like PHP or ASP is not supported.

Deploy these projects to GitLab Pages

Open-source projects and templates that run on GitLab Pages's free tier.

No projects linked yet. Submit one β†’