DataPacts

GitLab Export and Licensing Repository Data

Checked

At a glance

A company can export its GitLab projects and license them for AI training, because GitLab's Subscription Agreement leaves all right, title and interest in Customer Content with the customer, but a project export file is deleted within 24 hours and leaves out CI/CD variables and tokens (GitLab documentation, read November 16, 2026).

Independent reference. Every buyer is covered on the same terms, every figure carries its source and check date, and no buyer pays to be listed or placed higher.

Request an independent introduction

Tell us what data your company holds. We reply with the buyers that fit and what their terms leave out. Your details reach a buyer only after you agree to a named introduction.

IndependentYour details stay with us until you agreeNot selling is a valid outcome

GitLab projects are one source in AI training data licensing, and five programs on record name GitLab in their data lists, listings or process (checked November 9, 2026). GitLab states that it "does not train generative AI models", so the license decision is the company's alone, and not licensing is a valid result.

The DataPacts Editorial Team dates every term and program statement below; the method is in how we source, date and check every figure.

Why AI Buyers Ask for GitLab Projects

AI buyers ask for GitLab projects because a project carries code together with its history: commits, merge request discussions and issues that show how engineers worked.

GitLab Inc. hosts the code and is not a party to a license between the company and a buyer. Mercor states in its Software Company listing that it names GitLab among the tools it works with, and asks for private repositories with three or more years of commit history from at least 10 engineers.

Mercor states a range of USD 50,000 to 500,000 to the company, more for large codebases or exclusive terms (listing published October 17, 2026, checked November 9, 2026); the range is Mercor's claim. Turing lists "source code (GitHub, GitLab)" among the data it takes.

Code as a data type, with acquirers, rates and eligibility, is covered in selling or licensing source code and codebases; this page stays on GitLab's export, terms and scanners.

How GitLab Data Leaves GitLab

GitLab data reaches a buyer as a project export file the company generates, or through a read-only connection that a program sets up.

What a Project Export File Includes and Leaves Out

A GitLab project export file includes the project and wiki repositories, issues with their comments, and merge requests with their diffs, comments and reviewers, and GitLab states that not all items are exported.

The table compares what the export includes and leaves out (as of 2026-11-16).

Item In a project export file? Note Source
Project and wiki repositories yes code and wiki history docs.gitlab.com
Issues yes with comments, iterations and state events docs.gitlab.com
Merge requests yes diffs, comments, reviewers, approvers; only the latest diff and pipeline kept docs.gitlab.com
Commit comments, snippets, releases, labels, milestones yes docs.gitlab.com
LFS objects, uploads, design files yes docs.gitlab.com
Archived CI/CD pipelines yes job traces and artifacts are not docs.gitlab.com
Direct project members yes, with the Maintainer or Owner role for the project's group docs.gitlab.com
CI/CD variables, webhooks, secure files, encrypted tokens no docs.gitlab.com
Package and container registry images no docs.gitlab.com
Activity logs for Git-related events no for example pushes and tag creation docs.gitlab.com
Links between issues and linked items; links to related merge requests no docs.gitlab.com

The manifest lists what the export leaves out, so a buyer does not assume a complete copy of the project.

The 24-Hour File Clock, Roles and Rate Limits

GitLab deletes project export files every 24 hours, so an export is generated when the company is ready to hand it over.

GitLab states default limits of 6 project exports per minute per user and 1 file retrieval per project per minute (checked November 9, 2026).

On GitLab.com the maximum import file size is 5 GB, and Self-Managed instances default to no limit (read November 16, 2026). A project export needs the Maintainer or Owner role, so who may generate it is an authority question as much as a role setting.

Scoping an Export and GitLab's Warning on Backups

Issues, merge requests or uploads can be left out of an export only through the project export API's excluded_relations option, not from the export button.

GitLab also states "You should not use project export files to back up your data", and after an export or import only the latest diff version and the latest pipeline in merge requests are visible. A licensed copy is therefore a scoped extract, not a restorable backup.

Group Exports, Direct Transfer and Read-Only Connections

GitLab deprecated group export files in GitLab 14.6 in favor of direct transfer, which moves groups between GitLab instances rather than producing a file to license.

Programs set up their own routes. Pangea.ai, a marketplace, states that owners connect GitHub, GitLab or Bitbucket read-only; Troveo states "No OAuth into your systems. No platform to install." (re-read November 16, 2026); Avelence states no default system access (Pangea.ai and Avelence checked November 9, 2026).

The token scopes behind these connections are not stated, so the seller asks each program in writing what access is granted and when it is revoked. The comparison of routes sits in buyer connectors vs native exports.

What GitLab's Terms Say About Customer Content

Two GitLab documents bear on a license: the Subscription Agreement, which governs Customer Content, and the GitLab Duo AI Terms, which govern AI features and what they produce.

The table compares what GitLab's own documents state (as of 2026-11-16).

Term What it says Date Source
Subscription Agreement 8.4 customer retains all right, title and interest in Customer Content, subject to a limited license to GitLab necessary to provide the Software and for its development and improvement current terms; apply to Free users and purchases on or after 2026-01-12 handbook.gitlab.com subscription agreement
Subscription Agreement 8.5 customer content made public under a license is licensed under that license; customer represents it has the rights same handbook.gitlab.com subscription agreement
GitLab Duo AI Terms 2.4 Input and Output are additional Customer Content; customer retains ownership current terms handbook.gitlab.com GitLab Duo AI Terms
GitLab Duo AI Terms 3.3 customer will not use AI Functionality to create, train or improve a similar or competing model or generative AI service current terms handbook.gitlab.com GitLab Duo AI Terms
GitLab Duo data usage GitLab states it "does not train generative AI models"; model sub-processors restricted from training on input and output read 2026-11-16 (page undated) docs.gitlab.com GitLab Duo data usage
Project export file deleted every 24 hours checked 2026-11-09, re-read 2026-11-16 docs.gitlab.com

Ownership Under Subscription Agreement Section 8.4

Section 8.4 of GitLab's Subscription Agreement states that the customer retains all right, title and interest in Customer Content, subject to a limited license to GitLab necessary to provide the Software and for its development and improvement.

The agreement defines Customer Content as all software, information, content and data provided by or on behalf of the customer or made available through the use of the Software, and the rights audit for data you want to license checks the layers beyond hosting.

The text read for this page contains no clause that says GitLab allows or forbids a license of Customer Content to a third party; other GitLab documents were not read, so the company's counsel checks them.

Public Licenses Applied Under Section 8.5

Where a customer applies a license to publicly available Customer Content on GitLab, section 8.5 says the content is licensed under that license and the customer represents it has the rights to do so.

Buyers draw the line at public and forked code: Pangea.ai accepts owned private code only, and Mercor lists forks and copies of open-source projects as not a fit (both checked November 9, 2026). The conditions of outside code are covered in open-source license contamination when licensing a codebase.

GitLab Duo: GitLab's Training Statement and the Competing-Model Clause

GitLab states that it "does not train generative AI models" and that its AI model sub-processors are restricted from using model input and output to train models (GitLab Duo data usage page, undated, read November 16, 2026).

Section 2.4 of the GitLab Duo AI Terms treats Input and Output as additional Customer Content and leaves ownership with the customer. Section 3.3 bars the customer from using AI Functionality to create, train or improve, directly or indirectly, a similar or competing foundational or large language model or other generative AI service.

Whether a repository that holds GitLab Duo output can be licensed to an AI developer without touching section 3.3 is a question for the buyer and counsel; no source read for this page answers it. Mercor states that code mostly written by AI tools is not a fit (checked November 9, 2026).

Secrets in GitLab History: What GitLab's Scanners Find and Miss

A secret committed to a GitLab repository stays in its history after the file is fixed, and GitLab's own scanners catch it only if a historic scan is run.

  • Secret push protection (Ultimate) scans only the diffs of commits pushed over HTTP(S) and SSH; a secret already present in a file and not part of the changes is not detected.
  • Pipeline secret detection (all tiers) by default scans only the current state of the repository; secrets in its history are not detected unless a historic scan of all commits and branches is run.
  • Client-side detection scans issue and merge request descriptions and comments.

The export leaves out CI/CD variables and tokens, but secrets written into code, issues and comments travel with it.

GitLab states that exposed secrets should be revoked and replaced as soon as possible, and that a secret pushed to a remote repository is no longer secure. Names and other personal data in history are handled under PII removal and de-identification.

The order that follows from these gaps is a historic scan, revocation of every finding, and a fresh export, because an export generated before the scan carries the secrets.

Authors and Outside Code in a GitLab Project

Commit history names every author of a GitLab project, and each author's employment or contract status decides whether the company owns what it licenses.

Mercor lists code owned outright as a requirement and single-author repositories as not a fit, and Pangea.ai accepts no client-owned code (checked November 9, 2026). The assignments are covered under who owns the code you want to sell.

Programs That Name GitLab

Five programs on record name GitLab in their data lists, listings or process, each listed here with its role and the date its page was checked.

The table lists them alphabetically with the route or term relevant to GitLab data (as of 2026-11-09, with later re-checks dated); it carries no payout column by design.

Program Role Where GitLab appears (program's wording) Route or term relevant to GitLab data Checked Source
Avelence seller advisory intermediary (broker) data list "GitHub/Snowflake/GitLab" no default system access; de-identification on a separate copy 2026-11-09 avelence.com
Mercor, Software Company listing data buyer tools named GitHub, GitLab, Bitbucket, Jira, Linear, Confluence private repositories never public; 3+ years of history from at least 10 engineers; not a fit: forks, code mostly written by AI tools, single-author repositories 2026-11-09 api.data.mercor.com
Pangea.ai code licensing intermediary (marketplace) process: "connect GitHub/GitLab/Bitbucket read-only" non-exclusive; owner keeps ownership; owned private code only 2026-11-09 pangea.ai/code-licensing/companies
Troveo business data licensing intermediary (marketplace) data list "GitHub, Snowflake, Databricks and GitLab" "No OAuth into your systems. No platform to install."; seller retains ownership; exclusivity "time-limited and it has to be earned" 2026-11-09; FAQ and access wording 2026-11-16 troveo.ai/business-data
Turing Project Lazarus human-data platform data list "source code (GitHub, GitLab)" license to Turing exclusive for the first 6 months; Turing may license the record to more than one lab in that term; ownership does not change hands 2026-11-09; re-read 2026-11-17 lazarus.turing.com

Intermediaries place, broker or resell data on the holder's behalf and do not acquire it.

Pangea.ai states a non-exclusive license in which the owner keeps ownership. Turing states that the license to Turing is exclusive for the first 6 months after signing, during which it may license the record to more than one lab, and that ownership does not change hands (re-read November 17, 2026), and Troveo states that exclusivity is time-limited and has to be earned. Payouts sit with AI data partnership payouts and program terms compared, each dated.

Licensing GitLab Repositories: Benefits, Risks, Downsides and Alternatives

Licensing GitLab repositories can earn income from code and history a company already holds while it keeps ownership, and it also releases secrets, names and design decisions that a trained model cannot give back.

Benefits

  • Ownership stays with the company in the terms Pangea.ai, Troveo and Turing state.
  • Turing states that de-identification and preparation are on its side, with nothing upfront (re-read November 16, 2026).

Risks

  • Secrets in history that GitLab's default scans do not reach.
  • Labelbox Prism states that models already trained on the data cannot be unlearned (checked November 9, 2026).
  • The open question on GitLab Duo output and section 3.3.

Downsides

  • The 24-hour file clock and the relations an export leaves out.
  • Exclusivity, such as Turing's 6-month exclusive license, that limits other sales.

Alternatives

  • Not licensing at all.
  • Licensing some projects only.
  • Code without issues and merge requests, scoped through the export API.
  • Internal use only.

GitLab Among Code Hosts, Source Systems and the Seller Steps

GitLab is one of three code hosts a company may license from, and its export comes after the readiness check and inventory and before de-identification and the choice of buyer.

The parent page compares export rights and mechanics by source system. GitHub's own terms, archive clock and Copilot policy are covered in GitHub repositories and their export rights, the Bitbucket export has its own page in preparation, and issue history in Jira sits under Jira data export rights. The sector view is software companies licensing code and product data.

  1. Data sale readiness
  2. Data inventory for an AI data sale
  3. The data manifest
  4. Choosing a buyer for your data
  5. AI data licensing agreement
  6. Delivering licensed data to an AI buyer
  7. Should you sell or license your data

GitLab Projects of a Closed Company

A closed company can license its GitLab projects only while someone with authority still holds the Owner or Maintainer role, and each export file must be retrieved within GitLab's 24-hour window.

Turing states that it accepts companies shut down within or beyond 90 days (re-read November 16, 2026). The route is covered in selling data from a shut-down or defunct company, and the vendor deletion deadlines before shutting down are tracked separately.

Program Pages Named on This Page

The program terms above come from each program's own page, checked November 9, 2026, with later re-checks noted. The overviews are company data partnership programs and who buys AI training data.

Frequently Asked Questions

How long does a GitLab project export stay available?

GitLab deletes project export files every 24 hours, so the file is saved as soon as it is generated. Default limits are 6 exports per minute per user and 1 file retrieval per project per minute.

Does a GitLab export include CI/CD variables and tokens?

No; CI/CD variables, webhooks, secure files and any encrypted tokens are not exported, but secrets written into code, issues or comments travel with the export. A historic scan before export finds them.

Does GitLab train AI on code hosted on GitLab?

GitLab states that it does not train generative AI models and that its AI sub-processors may not train on model input and output. The statement is GitLab's, on an undated page read November 16, 2026.

Can a company license its GitLab repositories for AI training?

Yes, a company can license projects it owns, usually non-exclusively and through data programs and intermediaries, once secrets and personal data are dealt with.

No public price exists for GitLab data as such; the general methods are in how much company data is worth to AI companies.