The licence shape

Licensing git repositories for AI training: sale or licence?

Updated

2 buyers describe a non-exclusive licence and 3 leave the shape to the deal, a sale or a licence; 10 do not say.

Describe my codebase

Sale or licence, by count

Of the 15 buyers on the board, 2 describe a non-exclusive licence and 3 say exclusive or non-exclusive by deal. Among those, FileYield and License My Data also name a one-time sale or buyout as one of the options.

Why it matters before the price

A non-exclusive licence lets a company place the same repositories again; a buyout ends that. 10 buyers do not say which they take on the pages we read, so ask before any figure is discussed. Each buyer's licence wording is on its row of the board.

Tell us about the codebase

Describe the code, its history and who owns it. We tell you which buyers on the board take that kind of codebase and what to settle before you talk to one.

The code you own

What kind of codebase is it?

  • No repository access asked for
  • Every buyer answer quotes its own page

Holding years of repositories you no longer ship?

Describe the code, its history and who owns it. We tell you which buyers on the board take that kind of codebase and what to settle before you talk to one.

Sources

This site's own dataset, every figure quoted from its source and dated:

Describe my codebase