Pangea: Code licensing

Pangea licenses private source code and git history to AI labs at $100 and $40 per million tokens. The license is non-exclusive, so you keep the code.

Published October 19, 2026. Last checked October 20, 2026

What Pangea takes

•Source code from private repositories
•Git history (commits, branches, the record of how the code changed)

What Pangea asks for

•Code you own, or have the right to license
•A repository that was never public
•Not a fork, and not work done for a client
•No confidential data or conflicting third-party rights inside

What Pangea pays

•$100 per million tokens of source code and $40 per million tokens of git history, indicative, changeable on 30 days' notice
•Roughly $1,000 to $1,500 per repository at typical depth, Pangea's own illustration, not a quote
•Grading takes a few hours to four weeks. Licensing typically takes 2 to 16 weeks and is not guaranteed
•Paid within 15 days of the buyer's payment, once your tax and payout details are complete

From Pangea's own pages, checked October 20, 2026.

Check if your code qualifies Apply on Pangea's site We may earn a fee if you sign up. How we get paid

Six questions, about two minutes. You see whether Pangea would take your code.

Details on who qualifies

Companies and individuals can both license code they own. Agencies and consultancies can’t license work they did for clients.

Pangea takes repositories as they are, so you don’t need to clean them up first. Generated files, vendored code, binaries, data dumps and third-party code are left out of the valuation.

Details on pay

Git history is priced on its own, so a repository with years of commits, branches and merges earns more than the same code squashed into one commit. Rate changes never apply retroactively. Pangea’s page also shows about $6M earned on the platform in the last 60 days across 11,069 licensed repositories, figures it calls illustrative.

What Pangea does with your code

The license is non-exclusive. You keep ownership, keep using the code, and can license the same codebase more than once. An exclusive license or a full acquisition would need a separate written agreement on pricing.

Pangea grades a separate copy of each repository and strips secrets, customer data and personal data before any buyer sees it. Accepted repositories go to labs in batches.

You can withdraw a codebase before it goes to labs. After that it stays in the active process, and you can remove it from future opportunities with 30 days’ notice. Pangea keeps one encrypted copy while the code is available for licensing, and you can ask for deletion in writing, with limited exceptions.

How it works

Request access. You give your details and connect Git. Pangea returns an estimate.
Sign and connect. Pangea gives you the full agreement to review with your lawyer before you sign. You grant read-only access to GitHub, GitLab or Bitbucket and pick the repositories.
Grading. Pangea scrubs and grades a separate copy.
Licensing. Accepted repositories go to labs in batches.
Payment. Pangea pays within 15 days of the buyer paying.

Before you apply

Confirm nobody else holds rights to the code: a former co-founder, a contractor without an IP assignment, an acquirer. Pangea’s agreement makes you responsible for owning what you submit, with no cap, so settle any doubt with a lawyer first.
Check that the repository was never public, even briefly.
Leave the history alone. Don’t squash, rewrite or prune it.

Our guide to selling source code to AI companies covers what raises the price.

Sources

Pangea, code licensing for companies checked October 20, 2026

Estimate what your private repositories would earn at Pangea's rates with the worth calculator. It runs in your browser.