License GitLab repos to AI: what we could verify
The short answer
License GitLab repos to AI? Troveo lists GitLab. Use Usage quotas to check storage. GitLab says Duo inputs don't train GitLab models. Open-source licenses, client code and export rules apply as they do for GitHub.
GitLab repositories raise the same rights questions as GitHub ones. The size and export routes differ, and the buyer evidence is thinner.
Who lists GitLab?
Troveo's page lists GitHub, Snowflake, Databricks and GitLab under data and code. Mercor's page names GitHub and describes repositories, commits, pull requests and issues. micro1's page mentions source code documentation and bug tracking.
I found no price for a GitLab repository and no case of one being licensed. All of this is buyer self-description.
How do you check the size?
In a project or group, go to Settings, then Usage quotas, then the Storage tab (GitLab docs). Users with the Maintainer or Owner role can see it at project level, and the namespace Owner role is needed at group level.
GitLab says only the repository and LFS count toward the storage limit, and container registry, package registry and build artifacts do not. The docs give no date.
How does a project leave GitLab?
GitLab's project export API produces an archive, and its download examples use *export.tar.gz files. The page notes you must move CI/CD variables and the container registry separately. I did not confirm GitLab.com's export limits.
What do GitLab's AI terms say?
GitLab's AI transparency center says no inputs to or outputs from GitLab Duo features are currently used to train GitLab models. That describes GitLab's own models, and it leaves your right to license the code to your contracts and licenses.
Which rights questions carry over?
Check open-source licenses inside dependencies, code written for clients, and export-control rules for code. Can I license source code to AI covers them, including the Ninth Circuit's 16 Sep 2026 ruling in Doe v. GitHub. Licensing GitHub data to AI covers the buyer side, and checking GitHub organization size the sizing side.
Run the rights check on code separately from documents. Talk to a privacy or commercial lawyer in your state before you sign.
micro1 may pay us a referral fee if a company we introduce goes ahead with it. How we are paid
Vaultfish helps you run the process. We are not lawyers and this is not legal advice. If you need counsel who knows this area, we can point you to one. Ask for a referral
