How to Sell Startup Assets to Model Labs
TL;DR
- Shutting-down startups can sell codebases and internal data to AI labs for real cash.
- Companies often sell the same repo to multiple labs.
- HUD runs the end-to-end process, from NDA to payout.
Intro
Most founders winding down a startup don't realize their codebase has a buyer. Even if there's no acquisition offer, model labs are paying money for well written codebases as training data.
This guide walks through how code asset sales work, what makes a codebase valuable to a model lab, how to package and sell your repos, and how multi-buyer licensing lets you sell the same asset more than once.
Asset Sale vs Acquisition
An asset sale is a routine liquidation move, not a sign you failed at the exit. Founders wind down companies through IP assignments, acqui-hires, and asset sales all the time, often in combination. Asset sales sell the pieces that hold value in your business on their own, and a codebase with years of production history is one of those pieces.
AI model labs and foundation model teams want private code that never made it onto public GitHub, because they have already scraped everything public. Repos, tickets, and internal docs are proprietary and scarce training material they cannot get anywhere else.
What Makes a Codebase Valuable to AI Labs
Production history. Labs pay for this above everything else. A codebase that ran in production carries real commits, real bugs fixed, and real decisions about scale that no synthetic dataset reproduces. Repo age, commit density, real test suites, and a substantial PR history all tell a buyer this was a working system. The signal underneath all of it is the same: did engineers make hard decisions here over time?
Engineering context. Jira or Linear tickets show the work behind why a change happened. Internal docs, Slack threads, and runbooks connect the code to the reasoning behind it. A repo shipped with that paper trail can be worth several times one shipped bare. Buyers are paying for the decisions, not just the files.
Private data. Public GitHub was scraped years ago. What labs will pay for is the code that never left your infrastructure, and scarcity is exactly what sets the price. A private repo with two years of production history is something a lab cannot get anywhere else.
How to Package and Sell Your Private Repos
A clean sale runs in four steps. It's important to work through them in order. Skipping the rights check or the NDA is where most first-time sellers lose money or kill a deal.
Step 1 — Inventory
List every repo you own. For each one, note the primary language, the line count or size, whether it ran in production, and how sensitive its data is. A repo that served real traffic for two years is worth far more than a weekend prototype, so be honest about which is which.
Step 2 — Rights check
Confirm you actually own what you plan to sell. Your employee IP assignments should be clean, with no founder or contractor retaining rights. Check that no third-party code sits in the tree without a compatible license, and find any personally identifiable information that needs scrubbing before a buyer sees it. Sort this out before outreach, never after.
Step 3 — Packaging
Export each repo with its full commit history intact. The repo history is the product you're selling, so a flattened snapshot loses most of the value. Attach exports of your Jira or Linear tickets, snapshots of internal docs, and a one-page context brief per repo that explains what the system did, how it scaled, and what made it hard.
Step 4 — Delivery
Sign an NDA before any data moves. Agree on milestones and payment terms before you grant access, so the buyer commits to a structured process instead of browsing your code for free.
Multi-Buyer Licensing: Sell the Same Repo More Than Once
You can sell the same repo to more than one lab, and nothing about that breaks the first deal. Each sale grants a non-exclusive license. The lab gets the right to use your data for training, but no lab gets to lock anyone else out.
Exclusive deals pay more because the buyer is also buying scarcity. That premium costs you every repeat sale you could have made. Most labs assume non-exclusive terms unless they negotiate and pay for exclusivity.
State the non-exclusive status upfront. Labs price it in and rarely push back.
How HUD Enables Code Sales to Model Labs
HUD's vendor platform is built to handle codebase-first asset sales to model labs end-to-end. We handle packaging, pricing, licensing, and delivery to frontier labs.
- Apply — Short intake form, ~5 minutes, reviewed within 5 business days.
- NDA — HUD countersigns before any asset details are shared.
- Scope— Align on what you're bringing, target buyers, and success criteria.
- Build + deliver — Stage-by-stage milestones with verification cycles and acceptance criteria checked at each step.
- Payout — USD wire or ACH on a predictable invoicing schedule. Optional ongoing licensing available after closeout.
Apply as a vendor at vendor.hud.ai to start the process.
Conclusion
Three facts should change how you think about winding down. Selling your codebase to an AI lab is a legitimate liquidation path, not a fire sale or an admission of failure. Founders assign IP and run acqui-hires every week, and asset sales sit right alongside them.
Your codebase carries real training value because of what public scrapers can't reach. The production history, the bug fixes at scale, the tickets and docs and runbooks around the code all signal engineering reality that labs pay for. Private repos are scarce, and scarcity sets the price.
Multi-buyer licensing is the lever that turns one sale into recurring revenue. A non-exclusive grant lets you license the same repo to multiple labs without breaching anything. Unless a buyer pays a premium for exclusivity, you keep that right.
Start with a free codebase check at vendor.hud.ai. HUD grades your repos on production signal, context richness, and rights cleanliness, then makes an offer you can act on.
Frequently Asked Questions
How much do codebases sell for?
Prices depend on production history, surrounding context, and how clean your rights are. HUD grades each repo before making an offer, so the number reflects what the code actually demonstrates.
How long does a typical asset sale take?
Most deals move from NDA to payout in a few weeks, depending on how fast you can package repos and confirm rights.
Do I need a lawyer to complete the sale?
A lawyer helps you review the license terms, though HUD provides standard agreements that cover most asset sales.
Can I sell a codebase that used open-source dependencies?
Yes, as long as the licenses are compatible and the provenance is clear. HUD's grading flags dependency issues before they kill a deal.
What happens to user data stored in the repo?
Scrub any PII before delivery. HUD will not accept repos containing unscrubbed personal data.
Does selling to one lab prevent me from selling to others?
No. Non-exclusive licensing lets you sell the same repo to multiple labs, and HUD supports this by default.