GitLab makes software development remarkably productive by combining the Git workflow with a powerful user interface — making it effortless to review and collaborate on code with your team.
Today, we are proud to announce our first-class integration with GitLab, Vercel for GitLab.
Vercel makes it easy for you to build and deploy code — whether you need serverless lambdas, a static website, or both combined.
If you use GitLab in your development workflow, you can take advantage of Vercel for GitLab and get automatic deployments with built-in CI/CD, DNS and TLS.

Vercel for GitLab

Before a feature branch is merged and deployed to production, it can be valuable for your team to be able to test progressive iterations via staging deployments.
With Vercel for GitLab, staging deployments are automatically taken care of, on every push — once your GitLab project is linked to Vercel.

Commits pushed to GitLab are automatically built and deployed with Vercel.

With only a few steps, you can set up automatic deployments to Vercel via GitLab:
  1. Connect to GitLab with one click and link your project.
  2. Every git push to your project triggers a Vercel deployment with a unique URL.
  3. The default branch (usually master) gets aliased to your chosen domain names.
Additionally, Vercel for GitLab supports instant rollbacks for aliases, when changes are reverted on the default branch.

Connect with GitLab

The first step in setting up the Vercel for GitLab integration is to Connect with GitLab. This makes the integration available to your GitLab projects, and, as an additional benefit, it also allows you to Log In to via GitLab.
To get started, visit the accounts page on your individual or team Vercel account, and click the Connect with GitLab button.

The Connect with GitLab button helps you connect your individual or team account with GitLab.

When GitLab requests an authorization, click Authorize.

Click Authorize to complete the GitLab connection process.

Once you authorize GitLab, it redirects you back to Vercel. This completes the account connection process, and you automatically activate the ability to Login with GitLab the next time.

Once you connect GitLab, you also activate the ability to Log In to Vercel with GitLab.

Link projects

After your GitLab account is connected through the Vercel accounts page, you can set up automatic deployments for a GitLab project by linking it to Vercel, with the help of a dropdown.

Select the GitLab project you would like to link to, from the provided dropdown.
Once linked, pushes made to the GitLab project will be automatically deployed with Now.

Once linked, the GitLab project is set up for automatic Vercel deployments.

What happens after linking

For every git push to a GitLab project, we build and deploy the latest commit with Vercel. The deployment is guided by a vercel.json file. It allows you to configure the deployments for domain name and choice of Builder, among other options.
You can learn more about configuring vercel.json on its docs page. If the vercel.json file is missing for a project, we instead deploy the project as a static directory.
By default, we deploy every push. This means that every git push done to a Merge Request branch is deployed — allowing collaborators to preview staging changes before they're merged and deployed to production.
Within a Merge Request, if Vercel is still building a commit from a previous push, that build is cancelled in favor of the most recently pushed commit. This allows collaborators the quickest access to fresh changes.

Aliases and rollbacks

When an alias is specified in the vercel.json file, introducing changes to the default branch causes the deployment to be aliased automatically, as soon as the deployment completes. All the aliases are immediately made live, with no extra steps necessary.
If the default branch receives a commit reverting changes, an instant rollback is performed on the aliases. When you deploy with Vercel, we map all your code and configuration to a single, unique URL and a new build is only performed when the underlying code receives changes. If you trigger a revert within GitLab on the default branch, the code and configuration perfectly matches a deployment URL Vercel previously had. This allows us to perform the alias within milliseconds.


Our mission at Vercel is to make the cloud accessible for everyone. The Vercel for GitLab integration was one of our most requested features. We are excited about this announcement, and hope that it makes your development workflow smoother.
All of our work is heavily driven by feedback from our users. For feature requests, or to suggest us ideas to make our platform and your experience better, please reach out to us us over chat or on Twitter.