A GitLab Pages Alternative Without CI Config

Looking for a GitLab Pages alternative with preview links and a simple bill? What Free and Premium include, who should stay, and six hosts compared, Nov 2026.
The OxyPages Team · · 9 min read
Your team's code already lives on GitLab, so the docs site or the marketing page went on GitLab Pages. A pages job in .gitlab-ci.yml, a public folder, and it was live. That part is genuinely good.
Then someone asked for a preview link on a merge request so the designer could check a change before it shipped. You went looking and found that GitLab's parallel deployments, the feature that gives each merge request its own URL, are listed for Premium and Ultimate only. Premium is $29 per user a month, billed annually.
That's the moment most small teams start looking for a GitLab Pages alternative. Not because Pages is bad, but because the one feature they wanted is priced per head.
This post covers what Pages gives you on Free, what previews cost on Premium, who should stay, and six hosts that serve the same build with a different bill. Every vendor figure was checked on the vendor's own pages in November 2026. For the full field, every static host compared side by side has the bigger table.
TL;DR: GitLab Pages is free on every tier, with a 1 GB site limit, up to 150 custom domains, automatic Let's Encrypt certificates and a _redirects file. Builds share your 400 free CI minutes a month with everything else. Merge request previews (parallel deployments) need Premium at $29 per user a month billed annually, so a four-person team pays $116 a month. Stay if you rely on private Pages tied to GitLab permissions or you're already on Premium. If you want previews without per-seat pricing, Netlify connects to GitLab and builds a preview for every merge request, and Pro is a flat $20 a month for unlimited members.
What GitLab Pages Does Well
GitLab Pages is static hosting built into GitLab: a CI job builds your site, and GitLab serves the output folder. It handles plain HTML, CSS and JavaScript, static site generators and WebAssembly. It doesn't run server code, so PHP or ASP pages won't work.
The free tier is generous for a site host bundled into a code host:
- 1 GB per site on GitLab.com.
- 150 custom domains per site, each with an automatic Let's Encrypt certificate.
- A
_redirectsfile with up to 1,000 rules. - Access control, so a Pages site can be limited to project members.
- No credit card to sign up, though GitLab may ask for a phone number or payment method before you can use its hosted runners.
Let's Encrypt explains how those free certificates are issued, and you never renew anything by hand. That's a fair deal for an open-source project's docs. The trouble starts when more than one person reviews changes.
Why Small Teams Look Elsewhere
Small teams leave for three reasons, and only one of them is about Pages itself.
Previews are a Premium feature. GitLab's docs list parallel deployments as "Tier: Premium, Ultimate." That's the feature you set up with a path_prefix like mr-123 so each merge request gets its own URL. Those deployments expire after 24 hours by default unless you change it.
CI minutes are shared. The 400 free compute minutes a month cover every pipeline in your namespace: tests, linting and the Pages build. A busy repo can burn through them before the site deploys.
Premium is billed per user, per year. At $29 per user a month billed annually, every new teammate adds $348 a year. You also get 10,000 compute minutes, which is real value if you use GitLab CI heavily.
What Preview Links Cost A Small Team
Say you're a team of four: two developers, a designer and a product person who signs off on copy. Everyone needs to open preview links, and in GitLab everyone who works in the project is a user.
On Premium that's 4 × $29, or $116 a month and $1,392 a year, paid up front. Add a fifth person and it's $145 a month.
If you also use GitLab for issues, code review and CI, that buys a lot more than previews. If previews are the only reason to upgrade, you're paying for a full DevOps platform to get one link per merge request.
Who Should Stay On GitLab Pages?
Stay on GitLab Pages when the things that make it awkward don't apply to you. Here's when moving would cost more than it saves.
- You're already on Premium. Parallel deployments are included, so the main reason to leave is gone.
- You use private Pages. Access control tied to GitLab project permissions is hard to copy. Other hosts protect sites with a shared password or a separate sign-in service instead.
- Your site is open-source docs on Free. Free hosting with custom domains and HTTPS is hard to beat when nobody needs previews.
- GitLab CI is your whole pipeline. If tests, builds and deploys already run there, adding a second platform adds a second place for things to break.
- You self-host GitLab. Pages runs on Self-Managed and Dedicated too, which matters if your code can't leave your own servers.
If none of those fit, you're paying per seat for a folder of static files.
Picking A GitLab Pages Alternative For A Small Team
Pick on two things: whether the host gives you preview links for merge requests, and whether the bill grows with your headcount. All prices are monthly and as of November 2026.
| Host | Free tier | Paid from (monthly) | Preview links | Per-seat billing | The catch |
|---|---|---|---|---|---|
| GitLab Pages | 1 GB site, 400 CI minutes shared | Premium $29 per user, billed annually | Premium and Ultimate only | Yes | Previews priced per head |
| Netlify | 300 credits, hard limit, 1 member | Pro $20, unlimited members | Every merge request, from GitLab | No (Pro) | Deploys and bandwidth spend credits |
| Cloudflare Pages | Unlimited static requests, 500 builds | Workers Paid $5 per account | Branches and pull requests | No | Docs push new projects to Workers |
| Vercel | Hobby: 100 GB transfer, 1 seat | Pro $20 per deploying seat | Every pull request | Yes | Hobby is non-commercial |
| DigitalOcean App Platform | 3 static apps, 1 GiB transfer each | Extra static apps $3 each | Not covered here | No | Overage billed at $0.02 per GiB |
| OxyPages | 1 site, 25 MB, 5,000 page views | Lite $5 ($48 a year), Starter $10 | No per-merge-request URLs listed | No | Builds from GitHub, not GitLab |
| Codeberg Pages | Free, custom domains | None (donation funded) | No | No | Open licence required |
Netlify
Netlify suits a small team that wants previews on day one. It connects to GitLab repositories, and when you open a merge request it builds a Deploy Preview at an address like deploy-preview-42--yoursite.netlify.app, with a status on the merge request. Deploy previews don't consume credits.
The free plan allows commercial projects but only one team member. Pro is $20 a month flat with unlimited members and 3,000 credits. The catch is the credit meter: each production deploy costs 15 credits and each GB of bandwidth costs 20. Sites pause at zero unless you turn on auto-recharge, which is off by default.
Cloudflare Pages
Cloudflare Pages suits a team with spiky traffic. It connects to GitHub and GitLab, builds preview URLs for commits on any branch, and serves static requests free with no cap. The free plan includes 500 builds a month, and Workers Paid starts at $5 a month per account, not per person.
The catch is the product split. Cloudflare's Pages docs now tell new projects to start on Workers, and each file is capped at 25 MiB.
Vercel
Vercel suits teams moving towards Next.js. It deploys from GitLab and builds a preview for every pull request, with comments on previews. Hobby is limited to personal or non-commercial use and one developer seat with no team collaboration. Pro is $20 a month per deploying seat, so four developers pay $80 before usage. The Vercel alternatives post covers that trade in detail.
DigitalOcean App Platform
DigitalOcean suits a team that wants a predictable free tier with no seat limit. It deploys from GitHub and GitLab, includes three static-site apps with custom domains and unlimited team members, and charges $3 a month for each extra static app. Each free app gets 1 GiB of transfer a month, overage is billed at $0.02 per GiB, and sign-up uses a payment method to verify you.
OxyPages
We make this one, so I'll be plain about the fit. It has no per-seat pricing: Lite is $5 a month ($48 a year) for two sites with custom domains, password protection and commercial use, and Starter is $10 a month for five sites. It hosts built React, Vue, Svelte, Vite and Astro output with _redirects, _headers, version history and rollback.
The catch for GitLab users is real. It builds from GitHub, not GitLab, so you'd deploy from a CI job with its command-line tool, as in the next section. Its previews work only with GitHub repositories, so a GitLab project gets no merge request previews. If previews are the whole point, Netlify or Cloudflare fit better. And it runs no server code, so OxyPages is the wrong pick for anything that needs a backend.
Codeberg Pages
Codeberg Pages suits open-source projects that want a non-profit, EU-based host. It's free with custom domains. Its terms require a free or open licence, and they bar projects that mostly consist of code written by generative AI tools. Codeberg's older Pages server stops serving sites that haven't migrated on 31 December 2026.
Deploying To Another Host From GitLab CI

You don't have to leave GitLab to leave GitLab Pages. Keep your code and pipeline, and swap the pages job for a deploy job that pushes the build elsewhere. It takes about 15 minutes.
- Create an API key on the new host. Most hosts with a command-line tool offer one for CI.
- Store it as a masked CI/CD variable. In GitLab, go to Settings, then CI/CD, then Variables, and tick "Mask variable" so it never prints in a job log.
- Replace the
pagesjob. Build the site, then run the host's deploy command on the output folder. Here's a version for a Vite build, using one host's CLI as the example:
deploy:
image: node:20
stage: deploy
script:
- npm ci
- npm run build
# OXYPAGES_TOKEN is the masked CI/CD variable from step 2
- npx oxypages deploy dist --no-build --project my-site
rules:
- if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH
- Name the project explicitly. CI runners start from a clean folder each time, so pass the project name or ID. Otherwise some CLIs create a new project on every run.
- Carry over your redirects. If your
_redirectsfile sits inpublic, check that your build still copies it into the output folder. - Test, then move the domain. Open every route, refresh each one, then point your domain's DNS at the new host and remove the old Pages domain.
If refreshing an inner page returns a 404 after the move, your single-page app needs a fallback rule. Why a refresh returns a 404 and how to fix it walks through it.
What To Do Next
Count the people who need to open preview links, then multiply by $29. If that number makes you wince and you don't use the rest of Premium, move the site and keep the code on GitLab.
If previews on every merge request are the must-have, Netlify Pro at $20 a month flat is the closest match. If you just need a simple flat bill for a few static sites with custom domains, compare the plans and pricing and test one build before you switch the domain.
If you're already on Premium, or you depend on private Pages, stay put. You won't find a GitLab Pages alternative that does those two things better.
FAQ
Is GitLab Pages Free?
Yes. Pages is available on GitLab's Free, Premium and Ultimate tiers, with a 1 GB site limit and up to 150 custom domains on GitLab.com. The build uses your CI minutes, and Free includes 400 a month shared with every other pipeline. Merge request previews are not included on Free.
Can GitLab Pages Show A Preview For Each Merge Request?
Yes, through parallel deployments, which GitLab lists for Premium and Ultimate only. You set a path_prefix such as mr-123 in the Pages job, and the preview is deleted when the merge request is closed or merged. By default each deployment expires after 24 hours.
How Much Does GitLab Premium Cost For A Small Team?
Premium is $29 per user a month, billed annually, as of November 2026. A team of four pays $116 a month, or $1,392 a year up front. It also includes 10,000 compute minutes a month.
Can I Keep My Code On GitLab And Host The Site Elsewhere?
Yes. Netlify, Cloudflare Pages, Vercel and DigitalOcean connect to GitLab repositories directly. For a GitLab Pages alternative that only builds from GitHub, add a deploy job to .gitlab-ci.yml that runs the host's command-line tool with a masked API key.