Software Engineers - Licensing Your Git Repositories for AI Training

About the Role
We are seeking engagement with software companies, development agencies, product teams, and independent engineers who possess original codebases and are interested in exploring a new revenue stream through AI training licenses. This opportunity is available to organizations and individuals who have valuable repositories that they own and are legally able to license.
Eligible repositories can encompass:

• Active products
• Archived projects
• Internal tools
• Legacy systems
• Unsuccessful products
• Other original codebases with technical value

How it Works
The process for participating involves the following steps:

• Connect selected Git repositories for technical review.
• Submit only repositories you own or are authorized to license.
• Receive an assessment of repository size, structure, and licensing potential.
• Review the estimated value before deciding whether to proceed.
• Receive technical feedback where a repository needs improvement before it can qualify.
• Update and resubmit repositories where appropriate.
• Choose which approved repositories you want to make available for AI training.
• Receive payment when qualifying code is licensed and used.

Compensation
For standard non-exclusive licensing, the current reference rates are:

• $100 per 1M source-code tokens
• $40 per 1M Git-history tokens
  Each repository will be assessed individually, and you will have the opportunity to review the estimated value before making a decision to move forward.
  If you have repositories that are no longer generating commercial value, this opportunity can create an additional revenue stream from code you already own — without the need to sell the intellectual property outright. Your code remains yours under a non-exclusive licensing model, subject to the agreed licensing terms.

Requirements

• You must own the code or have clear legal authority to license it.
• Repositories should contain meaningful original software development work.
• You must be authorized to connect and submit the repository for evaluation.
• Code must not include third-party material that you are not permitted to sublicense.
• Repositories must pass technical and quality checks before licensing.
• Ownership or licensing rights may need to be verified.