Support for private git repository

Are there any plans to support third-party private git repositories, specifically Self-Managed GitLab?

Currently, our company relies on Self-Managed GitLab. Our frontend development utilizes a monorepo containing multiple applications, and managing builds and deployments via traditional pipelines for this setup can be quite challenging.

Based on my positive past experience with Vercel’s excellent monorepo support, we decided to use it for our projects. The ability for each application within our monorepo’s apps folder to become its own Vercel project seemed ideal, simplifying the management of deployment settings and environment variables significantly.

After creating a Pro team, we were surprised to discover that Vercel only integrates with the official cloud versions of GitHub, GitLab, and Bitbucket, with no apparent support for self-managed instances. This lack of integration feels like a missed opportunity, as it now forces us to cancel our Vercel plan and move to Netlify, which does offer support for Self-Managed GitLab.

Given this situation, could you let us know if there are any plans to introduce support for self-managed Git providers like GitLab Self-Managed in the future?

Hi @thecodedestroyer, welcome to the Vercel Community!

Thanks for your feedback. I’d recommend you to read through the Can I use self-managed GitLab with Vercel? and How can I use GitLab Pipelines with Vercel? guides?

1 Like

Hiya @anshumanb thank you for the kind welcome!

I did read those guides and from my understanding that flow requires you to build and deploy from GitLab pipelines and correct me if I’m wrong but I feel that that becomes really messy when trying to work with a monorepo like Turborepo and only building and deploying affected apps.
In case of adding a monorepo to Vercel via git cloud based provider Vercel detects its a monorepo project and offers specific path for the app and in that case only builds and deploys that app when it detects changes in that app or its dependencies.

I see. Thanks for explaining the use case. I’ll share this feedback with our team.