Home / Blog / Selling a shut-down startup's code and data to AI labs
Selling a shut-down startup's code and data to AI labs
A startup that has shut down can often license copies of its private codebase and business records to AI labs, which use them to train and evaluate coding and enterprise agents. The steps are: confirm who controls the IP, inventory what survives, agree a licence, remove secrets and personal data, and deliver a clean copy. The founders or investors usually keep ownership.
When a startup shuts down, its code and records usually sit untouched in a GitHub organisation, a Slack workspace and a few SaaS exports. For AI labs, that material is valuable: it shows how real software was built over years and how a real company actually worked. Public code and web text don't capture that.
What AI labs want from a shut-down company
- Code with real history. Private repositories with years of commits, many contributors, merged pull requests with reviews, issues and tests. A useful bar is 2+ years, 10,000+ lines, 1,000+ commits and 5+ contributors, never published publicly. See private codebases for AI training.
- Business operations records. Email, Slack or Teams, support tickets, CRM, docs and SOPs, project histories, financials and invoices, ideally linked across systems over 2+ years. See business operations data for AI agents.
Step 1: confirm who controls the IP
Before anything else, work out who can sign. It depends on how the company ended:
- Company still exists (dormant or acqui-hired): the company signs, usually with board approval. Check investor rights in your financing documents.
- Assets sold or assigned: whoever bought or received the IP signs.
- Formal insolvency or liquidation: the administrator, liquidator or trustee controls the assets and may need court or creditor approval.
Also check customer contracts. Some restrict how customer data can be used even after deletion of personal details, and those records stay out.
Step 2: inventory what survived
List the repositories (size, years, contributors, hosting), and each system's history: chat, email, ticketing, CRM, docs, accounting. Many SaaS tools delete data after an account closes, so export what you can as early as possible.
Step 3: license, don't sell outright
Most deals are licences: the buyer gets the right to train and evaluate models on a cleaned copy, and the IP stays with you. Terms to agree include field of use, exclusivity, duration, and what happens if a record must be removed later. Our rights checklist lists the questions buyers ask.
Step 4: remove secrets and personal data
- Scan the full git history for credentials, API keys and tokens, not just the latest commit.
- Remove customer data from fixtures, logs, seed files and support tickets.
- Pseudonymise employee and customer names, emails and account details so threads can still be followed without identifying anyone.
- Drop special-category personal data, such as health information, entirely.
Buyers usually pay for this cleanup, and it happens before anything leaves your control.
Step 5: sample, offer, deliver
Buyers review a small sample under NDA, make an offer, and the full copy is delivered once the licence is signed. Payment terms are set out in the licence.
How Datadhara helps
We take your code and records to several AI labs and data partners, bring you the best offer, and handle cleanup. You keep ownership, and you don't pay us: the buyer or platform does. See how it works or book 15 minutes.
This guide is general information, not legal or tax advice.
Questions
Can a shut-down startup sell its codebase to AI labs?
Often, yes. If the company, a successor or an administrator still controls the IP, it can license a cleaned copy of the private codebase to AI labs for training, while keeping ownership.
Who can sign a data licence after a startup shuts down?
The company itself (usually with board approval) if it still exists, whoever acquired the IP if it was sold or assigned, or the administrator, liquidator or trustee in a formal insolvency.
What company data do AI labs buy besides code?
Records of how the business ran: email, Slack or Teams, support tickets, CRM, docs and SOPs, project histories, financials and invoices, ideally linked across systems over two or more years.
Is personal data included?
No. Secrets are scanned out of the full git history, and customer and employee personal data is removed or pseudonymised before delivery.
Find out what your data could be worth
Tell us roughly what you have: repos, years of history, the systems you used. We'll give you a straight answer in 15 minutes.