Software Engineers - Licensing Your Git Repositories for AI Training

Location: India, Pakistan, Bangladesh, Vietnam, Indonesia, Philippines

Department: Talent Solutions

Workplace: remote

Description

We are connecting with software companies, development agencies, product teams, and independent engineers that own original codebases and want to explore a new revenue stream through AI training licenses.

It is a licensing opportunity for organizations and individuals that already have valuable repositories they own and are legally able to license.

Eligible repositories can include active products, archived projects, internal tools, legacy systems, unsuccessful products, or other original codebases that still hold technical value.

How it works?

• 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, current reference rates are:

• $100 per 1M source-code tokens
• $40 per 1M Git-history tokens

Each repository is assessed individually, and you can review the estimated value before deciding whether to move forward.

If you have repositories that are no longer generating value commercially, this can create an additional revenue stream from code you already own — without selling the IP 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.