Skip to content
Outrich Data

Source code · SaaS

License a SaaS company's source code for AI training

A software company can license private source code for AI training while it keeps operating, provided it owns the code and limits the scope with care. Outrich Data is a direct buyer that checks IP assignment and open-source obligations, excludes secrets and security-critical modules, and pays through escrow under a license you approve.

The records at this intersection

A SaaS code base is a production system: application services, a web client, infrastructure definitions, database migrations, tests and the continuous integration setup that ties them together. Alongside the code sit pull requests with review comments, design documents and incident postmortems.

For a company that is still selling its product, the code is also its main trade secret. That is the difference between this page and a sale by a closed company. The question is how to license parts of the repository history for model training without handing over what makes the product hard to copy.

A worked example

Consider a workflow software company with one large application repository and a set of internal tools. Leadership is comfortable licensing the internal tools and older, stable services, and not the core scheduling engine.

The title search confirms assignment agreements for employees and finds two early contractors without them, so their commits are identified and the affected files are removed. The scheduling engine is excluded by path. History is rewritten on a copy to strip secrets and vendored code. The license limits use to training and evaluation, and the data card lists languages, history span and every exclusion.

The example is illustrative. It does not describe a completed transaction.

Rules that bite here

What the title search looks at.

Invention assignment agreements
The company must own what it licenses. Employee and contractor agreements should assign code to the company. State laws such as California Labor Code section 2870 limit how far assignment reaches for work done on personal time, and missing contractor agreements are a common gap.
Open-source licenses
Third-party code stays under its own license. Copyleft licenses such as the GPL and AGPL attach conditions to distribution or network use. Only code the company owns is licensed, and the dependency list is reviewed with counsel.
Trade secret law
Under the Defend Trade Secrets Act and state law, protection depends on reasonable measures to keep the information secret. Licensing under confidentiality and use restrictions is designed to be consistent with that, but counsel should confirm the terms.
Customer contracts
Source code escrow agreements, custom development clauses and security exhibits can restrict disclosure of code or assign custom work to a customer.

This page is general information, not legal advice. Whether your company can license a given dataset depends on your contracts, your privacy notices and the law where you and your customers are. Review it with your own counsel before signing anything.

Removed before licensing

What comes out first.

  • Secrets in the working tree and in every historical commit
  • Authentication, billing, anti-abuse and licensing modules your security lead flags
  • Customer-specific branches, feature flags and custom work a customer owns
  • Customer data in fixtures, snapshots and seed files
  • Vendored and third-party code
  • Author names and emails in commit metadata
  • Open security findings and unpatched vulnerability details

Value

What raises or lowers the value.

FactorEffect on value
Scope of the grantA broader slice of the repository is worth more. Carving out core modules lowers the price and lowers the risk.
Review and test historyCode with substantive reviews and a passing test suite is worth more than code alone.
Never publicRepositories that were never open-sourced are what labs are paying for.
Clean ownershipComplete assignment records and a light third-party footprint make more of the code clear to license.

Publicly reported deals for context

Reported by the sources linked. These are other parties' deals, not offers, and not a prediction of what your data is worth.

Questions

Source code in saas: what companies ask.

Does licensing our code put our trade secrets at risk?
It is a real concern, and the answer is scope and contract. You choose which repositories and paths are included, the license restricts use and onward disclosure, and core modules can stay out. Discuss the trade secret position with counsel before agreeing a scope.
Do we have to be shutting down to do this?
No. The publicly reported code base deals cited on this page involved closed startups, but an operating company can license selected code under a non-exclusive license and keep building on it.
What if we used AI coding tools to write some of it?
Tell us. Ownership of generated code is unsettled, and some labs prefer human-written code. The share and location of generated code is recorded on the data card.

Find out if your data qualifies.

Eleven questions, about five minutes, no call required. You get an answer on screen and a written follow-up.

esc