Pangea.ai — Code Licensing

Why now

Real-world code is the scarce ingredient.

The labs building frontier coding models need to train and evaluate them on genuine production code — not just the final source, but the git history behind it: how features shipped, how bugs were fixed, how a codebase matured over time. Verified, real-world code like that can't be manufactured, and it's in short supply right now. The projects you've already built are exactly what they're looking for.

Scarce input

Authentic production code is the one input labs can't generate synthetically, so they pay for the real thing.

Rising demand

Buyers are actively acquiring real-world codebases to train and evaluate their models, and that appetite keeps growing.

History counts too

Your commits, fixes, and tickets carry real signal: you're paid for the git history, not only the final source.

What you're paid

A straight payout per million tokens.

$100/M

You're paid this — per million tokens of source code

$40/M

You're paid this — per million tokens of git history

That's what you're paid: a straight payout per million tokens, on every sale.
Connect Git to see a live estimate for each repo in minutes, at no cost.

Proof it works

Companies are already earning. Recurringly.

Combined total↻ recurring

$600K earned to date

380repositories licensed

Token mix ~13.6B total

Source 609M · 4.5%History 13B · 95.5%

One company's haul↻ recurring

$130K earned to date

22repositories licensed

Token mix ~3.1B total

Source 99.7M · 3.2%History 3B · 96.8%

Git history carries most of the value, and you're paid for it, not just the final source. Every figure here is licensed revenue, and non-exclusive licences keep it growing.

Only the repos you select Zero upfront cost Paid on every re-license

The opportunity

Value that's already built, paid for, and sitting idle.

The projects you've already shipped hold value beyond the original build: the real, production code frontier AI labs are paying for.

Found money

Turn R&D, internal tools, and past projects into a new revenue line.

Paid repeatedly

Licences are non-exclusive, so the same repo is licensed again and again, so you’re paid recurringly, on every sale, not just once.

You stay in control

You keep full ownership and the right to keep using the code yourself, internally and in your own products.

The IP question, answered

"But this is proprietary code."

And it's yours, which is exactly what makes it licensable. Because you own the code, you decide what's shared: only the repos you choose, and only code you hold the rights to, whether that's R&D, internal tools, retired products, or anything you own outright. Secrets, customer data, and third-party code stay out of it, and you can scrub anything sensitive before you submit.

You pick what's sharedOnly the repos you select are ever touched. Nothing else.

You keep full ownershipKeep using, modifying, and shipping your code, internally and to customers. Unaffected.

Redact before submittingStrip secrets, keys, or customer data first.

Ballpark estimate

Roughly what could your codebases be worth?

A quick, illustrative ballpark, nothing more. Your real, per-repo number comes in minutes once you connect Git. Final value depends on analysis of your repos and buyer demand.

Your codebases

Drag to estimate from repo count. Know your token counts? Enter them instead.

Repositories you'd consider licensing

15

Typical project depth — rough size of an average repo

Source code tokens — in millions

Git history tokens — in millions (optional)

Illustrative ballpark: what you take home

$15,000 – $22,500

≈ $1,000 – $1,500 per repo · recurring, paid on every re-license

Illustrative only: a conservative per-repo ballpark by codebase depth. It’s what you take home, not a revenue split. Not a quote; your real per-repo estimate appears when you connect Git.

Get my real estimate →

How it works

Three steps. Almost no lift on your side.

1

Request access

Tell us who you are. We set you up and send everything you need.

2

Sign & connect

Sign one combined agreement, then connect GitHub, GitLab, or Bitbucket and pick only the repos you want to license.

3

Get paid — repeatedly

Your codebases are valued and sold, and you're paid within 15 days of each sale.

Answers

Everything you ask us first.

Do I keep ownership of my code?+

Yes. You grant an exclusive licence to market and sell the codebase to buyers, but you keep ownership, plus full internal and commercial use.

Do I need to own the IP?+

Yes. Only submit codebases you fully own: nothing under someone else's IP, no NDA restrictions, and no confidential data. You warrant you hold the rights and choose exactly which repos to include.

Can I keep using the code myself?+

Yes. You keep the right to use, modify, deploy, and maintain the code across your own products and services, internal and customer-facing. All unaffected.

Is the licence exclusive?+

While a codebase is listed, it's only sold through us, so you can't list the same one elsewhere in parallel. The exclusivity is about selling to buyers, nothing else.

When and how do I get paid?+

Once a codebase is licensed and the buyer pays, you're paid on Net 15 terms: within 15 days, into the payout account you set up directly.

Can I change my mind and pull a codebase?+

Yes. You can withdraw a codebase from future listing on 30 days' notice. That doesn't unwind a deal already in progress, but it stops new ones. Either side can end the overall agreement on 30 days' notice.

Want the full detail in writing? Ask for the complete FAQ & security overview →

Request access

See what your codebases are actually worth.

Tell us a little about you, and we'll set you up and send everything you need.

No fees to join Nothing deducted from what you earn No commitment

You're in — thanks!

Jaz will be in touch shortly with your next steps. Keep an eye on your inbox.