Questions before
you license your code.

AI developers need examples of real software to improve coding models. If your company owns suitable code, it may be possible to license it for agreed AI development purposes and receive a payment. Stackworth22 helps you assess the opportunity and connect with an appropriate licensing partner.

Start with a conversation about your software. If an assessment is relevant, your technical lead completes the assessment form and runs local checks. We use this information to help assess suitability and obtain an indicative valuation.

If there is interest on both sides, you can review the proposed agreement, prepare the agreed material and decide whether to proceed. Stackworth22 acts as an intermediary. The contracting parties, recipient and payer are confirmed for each transaction.

We help companies understand the opportunity, collect information for an initial assessment and connect with relevant licensing partners. We can coordinate discussions while you evaluate the proposed terms. Stackworth22 acts as an intermediary and does not itself buy or license your source code.

Requesting an initial discussion or estimate does not itself require you to license your code. Any obligations arise from documents you choose to sign. Review their terms before agreeing to them.

Discuss your codebase with us first. If an assessment is relevant, we will explain the information needed and the next steps.

The website is currently a review prototype. Use sample details in the form. Submissions remain in your browser and no email is sent. Use stackworth@flow22.ai for a conversation. Confirm the appropriate return channel before sharing assessment material.

The intended structure is a non-exclusive licence: your company retains ownership of its code and intellectual property. The signed agreement defines the rights granted, permitted uses and any restrictions. Review the actual agreement before deciding.

The proposed non-exclusive model is intended to allow your company to continue operating, selling and developing its products. Confirm this in the proposed agreement and review existing customer and third-party agreements before including any code.

Code that your company owns or has the necessary rights to license may be suitable. This can include proprietary applications, platforms, internal tools, individual modules and discontinued products. The software does not need to be live.

For the current opportunity coordinated with Human Edge, eligible material is private, proprietary code written by people. AI-generated code, open-source code and third-party components are excluded from the eligible amount. Suitability depends on the buyer’s requirements and review.

Only include material you have the necessary rights to license. Review client contracts, employee and contractor rights, open-source licences and third-party restrictions. Client-developed code requires the necessary rights or the client’s permission.

Exclude material with unclear rights until its position is confirmed. The same principle applies to code from a previous business.

Agree the scope before any transfer. Identify repositories or components you want assessed, and flag material that must be excluded. Final inclusion depends on buyer requirements and the agreement.

Different client implementations can be assessed if you hold the necessary rights. Repeated code is deducted when assessing eligible value.

The current Human Edge draft assessment excludes codebases built on WordPress, Drupal, Magento, Shopify or similar CMS platforms. If your software combines a CMS with separately owned proprietary systems, clarify the eligible scope before completing the assessment.

A non-exclusive licence may allow additional licensing, subject to its precise terms, restrictions in other agreements and buyer requirements. Confirm this in the agreement before proceeding. Additional licensing opportunities are not guaranteed.

The opportunity is for AI model development, including training, as specified in the relevant agreement. The contract should define permitted uses, the recipient, any onward sharing and use restrictions. Ask for clarification before sharing material if any of these points are unclear.

Stackworth22 helps assess and coordinate opportunities with specialist licensing partners. The actual recipient, contracting entity and payer must be confirmed for your transaction.

Agree confidentiality and handling requirements before any code is transferred. Preparation should identify and remove credentials, secrets, personal data, customer information and other confidential material.

Confirm who is responsible for preparation and review, who may access the material, and which security measures apply. These requirements should be set out in the agreement. Complete removal of sensitive material should not be assumed without appropriate checks.

AI models can sometimes generate outputs resembling material in their training data. The actual risk depends on the model, the data and how it is used.

Ask the proposed recipient about its safeguards and review the agreement’s provisions on use, outputs and remedies. No absolute guarantee against reproduction should be assumed.

Withdrawal, termination, retention and deletion rights depend on the contract and the stage of the process. Model training may already have taken place. Review termination and post-termination provisions before signing, including what can practically be withdrawn or deleted.

Agree disclosure and publicity rights in writing. Ask how company names, code metadata and customer references will be handled, and whether any public announcement requires consent.

Value depends on eligible size, languages, technical quality, uniqueness, duplication, development history, documentation and buyer demand. Information you provide can support an initial indication. The final amount depends on assessment and agreement.

The website estimator shows an illustrative USD amount based on your answers. Where fuller Git history or passing tests could improve the submission, it also shows a conditional higher payment and explains what is needed. Formal sizing and review determine eligibility and the final amount. The draft assessment spreadsheet contains no pricing rates.

An approximate count of lines of code by language is a useful starting point. The draft form uses scc to collect logical lines of code and a language breakdown, and jscpd to assess duplication. Generated code, duplicates and components you cannot license must be considered when reviewing the eligible amount.

Run the checks locally and keep source code on your systems. Open the step-by-step assessment guide

No source code is needed for the current initial assessment. Run the checks locally on your own systems and return the completed spreadsheet with statistics-only reports.

Any later request for code, samples or repository access should be discussed and agreed in advance, including confidentiality, permissions and security arrangements.

Both can affect interest, alongside the purpose, quality and structure of the software. Share the main languages, development history and a brief description so the opportunity can be assessed. Older code and discontinued systems can be considered when rights and buyer requirements allow.

Commit history and related development information may be relevant to some buyers. Any additional value depends on demand, rights, quality and agreed scope. Full Git history does not guarantee a higher payment.

Flag personal data and confidential material in commit metadata, branches, tags and history for review before any transfer.

Your CTO, technical lead or someone with access to your repositories should complete it. Use one row per codebase, combining repositories when they are delivered and priced as one package. The draft has room for up to 50 codebases.

It collects repository count, logical and non-authored lines of code, duplication ratio, non-merge commits, Git availability, builds/tests, publication history, primary language, human or AI authorship and software purpose. Rights and sensitive-data preparation are reviewed alongside these metrics.

Download the draft assessment spreadsheet

Return the completed spreadsheet, scc-report.json and jscpd-summary.json containing statistics only. The full jscpd report can contain code excerpts and must stay on your systems. Do not include source code, credentials or customer records.

Use the confirmed return channel supplied by your contact. The current prototype has no report-upload facility or live email delivery.

Start with a conversation about your software. If you choose an assessment, your team provides basic information, confirms rights and runs local measurements. Completing the initial form and checks usually takes around 15–30 minutes for a straightforward codebase. Larger collections can take longer.

Later preparation and review can require additional work. Agree responsibilities and costs in advance.

Timing depends on initial review, rights checks, negotiations, technical preparation and buyer approval. We will discuss the expected steps with you. No fixed completion timeline is guaranteed.

For the current assessment process, we submit assessment forms and technical reports every Wednesday. After review, we can share an initial valuation range. That estimate may change after full technical review and the AI lab’s final approval.

For the current opportunity, the target is to send the next batch to Meta by mid-December 2026. This depends on Meta’s confirmation and completion of technical and legal reviews. Submission does not guarantee acceptance or a transaction.

The amount, payment trigger, payment timing and payer must be stated in the signed agreement and may differ by transaction. Ask for the full commercial terms before committing.

For the current opportunity, if your code is selected and the price is agreed, your company would sign directly with Dialectica and receive payment from Dialectica. Payment is currently expected within 45–60 days after completion of the related Meta transaction, subject to your agreement. That period starts after the related transaction is completed.

For the current opportunity coordinated with Human Edge, your company pays no separate commission or fee to Stackworth22. Confirm any preparation responsibilities, costs and commercial terms before proceeding.