License private source code for AI
Separate code-only submissions from a full company record. Describe the repository, rights, history and runnable context without sending credentials or private files.
On this page
Choose the right track
Source-code licensing can involve a repository on its own or code alongside tickets, documents and company history. Turing says it reviews source-code-only submissions. A provider listing code among many formats does not necessarily offer the same standalone route.
Compare Turing, Pangea and Patronus by their specific tracks. Keep any published code pricing separate from company-record terms.
Describe the repository
Prepare an inventory of languages, approximate size, project age, version history, tests and documentation. Note which branches or periods are missing. Describe whether the project can run without production services or access to customer systems.
Keep secrets, access tokens, private keys and customer data out of the summary. Ask how the provider expects you to find and remove such material before any sample transfer. A scan result alone does not establish that every sensitive file is gone.
Map the rights by component
Separate original work from dependencies, generated files, client projects and licensed assets. Review employee and contractor agreements, acquisition records and previous licenses. The US Copyright Office's work-made-for-hire circular explains that ownership depends on the work and relationship; it does not resolve every repository's status.
Use the rights checklist to record unresolved components. Do not assume that possession of a private repository means the company can grant every proposed AI use.
Ask about tasks and environments
If the provider plans to create debugging tasks or runnable environments, ask which files it needs, how test results are scored and who may receive the resulting material. Review third-party software needed to run the project separately from the source files.
The derived-use guide covers these questions. Finish with a data summary that distinguishes the proposed licensed material from excluded dependencies and services.
Sources and limitations
Circular 30: Works Made for Hire Checked 2026-11-08
U.S. Copyright Office · Primary source
When it is created by an employee as part of the employee’s regular duties
U.S. copyright guidance only; work-for-hire status depends on the actual facts and applicable requirements. This does not determine rights in a visitor’s records.
Partnership Programs | Defined.ai Checked 2026-11-08
Defined.ai · Primary source
proper consent, documentation, and the right to commercialize the data for AI training
The program states these requirements; they do not establish permission for a particular dataset. Publication date not established.
Project Lazarus | Turing Checked 2026-11-08
Turing Project Lazarus · Primary source
Through revenue share … You owe nothing.
The no-sale FAQ answer addresses what the seller owes. The agreement sets the payment terms. Publication date not established.