Your agency's old code is an untapped asset.

Yes. You grant a non-exclusive license, but you keep ownership and can continue using, modifying, and developing your code.

Yes. Your ability to use, modify, deploy and maintain the code remains unaffected.

No. Standard licences are non-exclusive, which means the same codebase may be licensed more than once. Any exclusive licence or full acquisition would require your separate written agreement on pricing.

Yes. Only submit private code that you own or have the right to license. Do not submit client-owned, previously public or forked code, or anything containing confidential data or conflicting third-party rights.

The estimate considers eligible source code, supporting files and Git history. Generated files, vendored code, binaries, data dumps and third-party code are excluded. You can see what was counted for each repository.

Your initial estimate is available immediately. Preparing and grading the codebase can take from a few hours to four weeks, depending on its size and complexity. Once ready, it is presented to buyers in upcoming batches. Buyer timelines vary, and licensing is subject to demand rather than guaranteed, but normally between 2 and 16 weeks.

Once the buyer’s payment is received, you are paid within 15 days to your nominated payout account. You will need to complete the required tax and payment details first.

Yes. You can withdraw a codebase at any time before it has been sent to AI labs for licensing.

Once it has been presented to a lab, it cannot be withdrawn from that active licensing process. However, you can withdraw it from any future licensing opportunities with 30 days’ notice. Any licensing process already underway may continue, including for up to 90 days after the agreement ends. Any licences already completed remain valid.

You are responsible for ensuring that you own or have the right to license every codebase you submit, and for disclosing any relevant third-party rights or restrictions. If that warranty is incorrect, you may need to return payments and cover resulting claims. This obligation is uncapped because buyers rely on the same ownership assurance. You are not responsible for issues caused by a buyer modifying, mishandling or using the code outside the agreed licence.

Yes. We will provide the complete agreement for you and your legal counsel to review before you sign.

Access to your Git provider is read-only and limited to the repositories you select. Nothing outside your selection can be accessed, and no changes are ever written back to your repositories. You can change or revoke access through your Git provider at any time.

Your code is encrypted in transit and at rest. All grading, scrubbing and preparation takes place on a separate copy, leaving your original repositories untouched.

During grading, an AI lab reviews a copy of the code against a fixed rubric. The provider operates under commercial data-protection terms and does not train on anything it receives. If a buyer later licenses the codebase, it may use the code to train or evaluate its models. This only happens after a licensing agreement is completed, and you are paid for it.

Before any code reaches a buyer, the working copy is scrubbed for secrets, credentials and personal data across both the current code and its Git history. Contributor identities are also pseudonymised. You should still disclose anything sensitive that you know about so it can be handled appropriately.

Not during grading. Grading uses read-only analysis of the source code and Git history without installing or building the project.

If a lower-scoring repository needs refinement, additions such as documentation, tests or CI may be tested in an isolated environment. Your original repository remains unchanged, and you can review what was added.

No. Submit it as it is. Removing legitimate source code or history may reduce the eligible token count and estimated value.

We handle scrubbing and preparation on a separate copy. Your responsibility is simply to choose appropriate repositories and disclose anything you know is sensitive.

One encrypted copy is retained while the codebase remains available for licensing. Temporary working copies are deleted after each review or preparation run. You can request deletion in writing, subject to limited exceptions such as routine backups, active licensing processes and copies already held by buyers under completed licences.

Your selected Git provider, established cloud infrastructure providers and the AI providers used for grading and classification. They operate under commercial data-protection terms. Buyers only receive the code after a licensing agreement is completed and under confidentiality and licence restrictions. Your participation is not disclosed publicly without your consent.