Blog
Longer notes on selling and licensing code to AI companies, written for the person who has to sign: who buys it, what it fetches, and which rights you actually hold.
Licensing your repo history vs selling the IP
Licensing repo history to an AI company vs selling the IP outright: what each grants, what you keep, exclusivity, and which suits a wound-down company.
Open-source dependencies: what can you license to an AI company?
Open-source dependencies in a private repo: what you can license to an AI company, what stays with its authors, and how to prepare a clean file tree.
Selling a wound-down startup's code: who buys it and what it fetches
Selling a wound-down startup's code to AI buyers: who buys it, what it fetched in a reported deal, who can sign after a shutdown and what to strip first.
Get a quote
ZIP, contact, then eight multiple-choice questions about the repos. Your answers get held up against every buyer's published rules, and the matches come back to you by email, by name.
No code, repo URLs, exports or samples here, please. Answers only; we do not want your data.
We run an introduction service, and a buyer you end up signing with may pay us for the introduction. You are not charged.
Answers in. The next moves:
- Each answer is compared with the published conditions of every buyer on this site.
- You get a short email: the fitting buyers by name, each with its reason, or a plain "no match today".
- A buyer only learns of you after you approve it, by name, in a reply. Your address is used for this request and then left alone.