Yes, Pangea.ai is a legitimate code-licensing marketplace run by Digital Knights SARL, a Swiss company, with published rates of about $100 per million tokens of source code and $40 per million tokens of git history. It licenses code non-exclusively and pays within 15 days of the buyer paying. The caveats: no named buyers, self-reported totals and an uncapped ownership warranty.
- Pangea.ai is a real, named business: its terms say Digital Knights SARL owns and operates it, under Swiss law. Its main business is matching companies with AI engineers; code licensing is a newer line.
- It licenses private source code and git history to AI labs on non-exclusive terms, at indicative rates of about $100 per million tokens of source and $40 per million tokens of history.
- Owners are paid within 15 days of the buyer paying, and licensing normally takes 2 to 16 weeks. Pangea says licensing depends on demand, so a listed repo may not sell.
- The figures that make it look large ($6 million in 60 days, 11,069 repositories) are Pangea's own, and it names no buyer. The seller's ownership warranty is uncapped.
Is Pangea legit? The short answer
Yes. Pangea.ai is a named company with published terms, published rates and a written agreement it offers for legal review before you sign. It pays code owners after a buyer pays, and it takes no fee from the owner's share by its own account. Searches for "is Pangea legit" usually come from agency owners, founders of wound-down startups and engineering leads who have been told their old repositories are worth money.
Legitimate does not mean every claim on the page is proven. Pangea's headline totals are self-reported, no AI lab buyer is named, and a sale depends on demand. The contract also puts real risk on the seller through an uncapped ownership warranty. Each point is set out below with its source, so you can decide whether the terms fit your code.
What Pangea.ai is and who runs it
Pangea.ai started as a talent marketplace. Its homepage still leads with "Applied AI Talent, Matched in 72 Hours" (Pangea.ai). Its terms of service say the name "refers to Digital Knights SARL, who owns and operates Pangea.ai", and that the terms are "governed by and construed in accordance with the laws of Valais, Switzerland" (Pangea.ai terms). A Swiss operator matters for one practical reason: any dispute runs under Swiss law unless your agreement says otherwise.
Code licensing is a newer line with its own pages for companies and software agencies. Pangea has also started a broader data licensing section that says it "helps companies license the data AI companies train on, starting with company records and private code". This review covers the code program, which is the one with published rates and terms.
One name check before you search further: Pangea.ai is not Pangea Cloud. Pangea Cloud sells "Security Guardrails for AI Applications" and has nothing to do with code licensing. Reviews and Reddit threads about one are often about the other.
Source: Pangea.ai: terms of service
How Pangea code licensing works and pays
You request access, sign the agreement once, then give read-only Git access to the repositories you choose. Pangea scrubs and grades a copy, then presents it to buyers in batches. It says "licensing is subject to demand rather than guaranteed, but normally between 2 and 16 weeks", and that "Once the buyer's payment is received, you are paid within 15 days to your nominated payout account" (Pangea.ai).
Pay is per token. Pangea's referral page puts it plainly: owners "are paid roughly $100 for every 1M tokens of source code and $40 for every 1M tokens of git history" (Pangea.ai referral page). Its illustrative per-repo ranges are $700 to $1,000 for a light repo, "Typical $1,000 to $1,500" and "Deep $1,500 to $2,000". The rates sit in the agreement and "can change on 30 days' notice, never retroactively".
Because licences are non-exclusive, the same repository can be licensed again, and Pangea pays on each licence. How often that happens depends on demand, which Pangea does not forecast.
| Question | Pangea.ai code licensing (checked 10 Nov 2026) |
|---|---|
| What it buys | Private source code and its git history, plus supporting files; generated, vendored and third-party code is excluded |
| From whom | Companies, software agencies, founders of wound-down startups and individual developers who own the code |
| Who the end buyers are | AI labs building coding models; none is named |
| How it pays | About $100 per million source tokens and $40 per million history tokens, within 15 days of the buyer paying |
| Licence | Non-exclusive; you keep ownership and full use of the code |
| Requirements | You own the code outright; no client-owned, forked or previously public code |
| Timing | Estimate on connecting Git; preparation hours to 4 weeks; licensing normally 2 to 16 weeks |
What Pangea's numbers show, and what they do not
The companies page shows "$6M earned in the last 60 days" and "11,069 repositories licensed", and the referral page cites a largest deal of "326 repositories from a single company", paid $300,000 (Pangea.ai). These are Pangea's own figures. We found no buyer, auditor or news report confirming them.
The same page says two things about its numbers. Its proof section states: "Every figure here is licensed revenue, and because licences are non-exclusive a codebase can be licensed again." Its footer says "All figures shown are illustrative, conservative estimates" (Pangea.ai). Ask which figures are paid revenue and which are estimates, and ask for the payment history behind any example you are shown.
Do the arithmetic on your own code. At Pangea's typical range of $1,000 to $1,500 a repository, 20 repositories come to roughly $20,000 to $30,000 per licence. That is a useful sum for idle code, but it is priced per token, not on the business context. Buyers that take code together with tickets, documents and other company records price it per company instead; see company data buyers compared and selling source code to AI companies.
Source: Pangea.ai: referral partner program for code licensing
Pangea terms to read before you sign
Most of the risk in a code licence sits in the warranty and the exclusions, not the rate. These are the terms worth reading twice.
- The ownership warranty is uncapped. Pangea says that if your ownership warranty is wrong, "you may need to return payments and cover resulting claims. This obligation is uncapped because buyers rely on the same ownership assurance" (Pangea.ai).
- Client work is out. Pangea says not to submit "client-owned, previously public or forked code". Agencies should check each master services agreement before choosing repos.
- A copy is graded by an outside model. Pangea says "During grading, an AI lab reviews a copy of the code against a fixed rubric", under data-protection terms that bar training on it.
- Secrets and identities are handled on a copy. Pangea scrubs secrets and personal data from code and history, and says "Contributor identities are also pseudonymised." Still disclose anything sensitive you know about.
- Withdrawal has limits. You can withdraw a codebase before it is presented to buyers; after that, an active licensing process can continue.
- Get the agreement first. Pangea says it will provide "the complete agreement for you and your legal counsel to review before you sign". Read the payment trigger, the warranty and the rate-change clause.
Who Pangea suits, and what to compare it with
Pangea suits owners with many small or medium repositories they own outright and no other use for: agencies with internal tools, founders of closed products and companies with retired code. The non-exclusive licence means selling through Pangea does not stop you licensing the same code elsewhere, unless another buyer asks for exclusivity. Check that point before you sign with a second buyer: an exclusive offer elsewhere may require you to withdraw code from Pangea first, and Pangea says any licensing already under way can continue.
It suits companies less when the value is in the context around the code. A codebase with years of tickets, reviews, incident notes and the documents that explain decisions is worth more as a set, and per-token pricing does not capture that. Turing's Project Lazarus and the programs in our RL environment companies tracker buy that wider set.
Before you connect Git anywhere, run the checks in how to vet an AI data buyer and compare the other routes in our directory of AI data companies.
Next step
If you hold code and the records around it, get a view on what the full set is worth before you license the code alone at a per-token rate.
Not sure whether a buyer or an offer is sound? Origin checks who the buyer is, what the license allows and how the price compares with published deals before anything is signed. Get a free estimate and a second opinion.
Origin Data Partners works with companies that own data and helps get it bought. We are independent of the services on this page, and a buyer may pay us when a deal closes (how Origin is paid). See what your data is worth.
Common questions
Is Pangea legit or a scam?
Pangea.ai is legitimate, not a scam: it is operated by Digital Knights SARL under Swiss law, publishes its rates and terms, and offers the full agreement for legal review before signing. Its headline totals are self-reported and it names no buyer, so ask for evidence of past payments.
How much does Pangea pay for code?
About $100 per million tokens of source code and $40 per million tokens of git history, according to Pangea. Its illustrative range for a typical repository is $1,000 to $1,500, and the rates can change on 30 days' notice.
When does Pangea pay?
Within 15 days of the buyer paying Pangea, into the payout account you nominate, once your tax and payment details are complete. Pangea says licensing normally takes 2 to 16 weeks and depends on demand.
Is Pangea.ai the same as Pangea Cloud?
No. Pangea.ai is a talent marketplace with a code-licensing program; Pangea Cloud is a separate AI security company. Check which one a review or Reddit thread is about.
Is a Pangea code license exclusive?
No. Pangea's standard licence is non-exclusive, so the same codebase can be licensed more than once and you keep ownership and full use of the code. An exclusive licence or sale needs a separate written agreement.
Can an agency license client code through Pangea?
No. Pangea excludes client-owned, previously public and forked code, and the seller gives an uncapped ownership warranty. Agencies should license only internal tools, R&D and products they own outright.
Which AI labs buy code through Pangea?
Pangea does not name them. It says buyers are labs building frontier coding models and that code is presented to them in batches after grading.