Code ownership and licensing for AI
Repositories look simple to license and are often the hardest to clear. Ownership is rarely as tidy as the commit history suggests.
Who owns the code
Employees' work is usually the company's, but contractors, agencies and acquired code may carry different terms. Check assignment clauses before anything else.
Open-source inside your repo
Dependencies and copied snippets bring their own licences, and some restrict how derivative material can be used.
- Third-party libraries and vendored code
- Copyleft licences with sharing obligations
- Snippets pasted from forums or tutorials
- Generated code and its provenance
Secrets and customer data
Scan history for keys, tokens, customer records and internal URLs. Removing them from the latest commit is not enough; history keeps them.
What buyers value
Review threads, issue discussions and fixes alongside the commits often matter more than the code alone.
How the process works
A conversation about software and code follows four stages, and you can stop at any of them. Each stage ends with a clear decision, so nothing moves forward by default.
Most people finish the first stage in a few minutes and take a week or two to decide about the rest. That pace is normal: the slow part is usually finding out who has authority to say yes.
- Estimate: you share a few headline numbers and get an indicative range. Nothing is uploaded.
- Review: we look at what you hold, who owns it and what restricts its use, then reply with a first view.
- Sample: a redacted sample goes to an interested buyer only after terms are signed.
- Licence: scope, permitted use, term and payment are written down before anything is delivered.
What buyers look at
Buyers care less about headcount than about how much real reasoning your software and code contains. A small team with ten careful years can be worth more than a large one with two noisy ones.
They also look for evidence that the material is complete. Gaps, such as a migration that dropped older records, lower interest because they make the history harder to trust.
- Depth: how many years the history covers and how consistent it is.
- Structure: whether the records connect a problem to a decision and an outcome.
- Cleanliness: how easily an export can be de-identified and checked.
- Rights: whether you can show clear permission to license it.
- Diversity: whether the material spans several situations rather than one repeated pattern.
Rights and consent in practice
Owning the system that stores your software and code is not the same as holding the right to license what is inside it. Rights usually sit in three places: your own agreements, the terms of the tool vendor, and the expectations of the people who appear in the records.
Start with the documents you already have. Employment agreements, customer contracts, privacy notices and vendor terms each say something about secondary use. A short summary of what each allows, written in plain language, saves weeks later.
- Your contracts: check for confidentiality or data-use clauses with customers and partners.
- Vendor terms: confirm the tool lets you export and reuse your own content.
- People in the records: employees, customers and third parties may have notice or consent requirements depending on where they live.
- Co-owners: investors, parents and acquirers sometimes hold a veto.
What shapes the price
Estimates start from a published method: staff count, years of history and how many systems hold the records. A real offer then moves up or down based on the factors below.
Treat the first range as a starting point for a conversation. Offers can differ widely between buyers because each one needs different material.
- Volume and span of the material.
- How well the records capture reasoning rather than routine notices.
- Exclusivity: a licence that is not exclusive generally earns less than one that is.
- Permitted use and term: narrower scope and shorter terms cost less.
- How much cleaning work a buyer must do before the material is usable.
What not to send early
Keep the first exchange light. These items can wait until terms are agreed, or never need to be shared.
If you are unsure whether something is safe to send, leave it out and ask. A missing attachment can be fixed in a minute; a leaked one cannot.
- Customer names, contact details or payment data.
- Passwords, tokens or access credentials.
- Raw exports before terms are signed.
- Anything covered by a confidentiality clause you have not checked.
What to prepare before a review
A short written note is enough. You do not need to upload anything confidential.
If you can answer most of the questions below, a first view can come back faster and be more specific.
- The tools involved and roughly how long you have used them.
- A rough volume for each, such as messages, tickets or invoices.
- Whether an admin can export a complete copy.
- Who can approve licensing, including any investors or advisers.
- Any contract or notice that limits secondary use.
Next steps
Start with the free estimate. If the range looks worth pursuing, add your tools on the inventory page so a review can be sharper.
You can also ask a question first using the support page. There is no obligation at any point.
Questions
Often yes, if you own it and have cleared third-party code and secrets. Review is read-only and needs your approval.
For anything beyond a first look, yes. Licensing terms, personal data and third-party rights are legal questions, and we are not your adviser.
A first view usually comes back within a few working days. Timing depends on how much there is to look at and how quickly rights questions are answered.
No. An estimate is indicative. Whether a buyer is interested depends on review, rights and demand at the time.
Yes. Scope is negotiable, and many deals cover a defined slice, period or function rather than everything.