Industry
SaaS data licensing for AI
Outrich Data licenses a software company's own records, such as source code, engineering tickets and internal documentation, and supplies them to AI labs for training, fine-tuning and evaluation. Suppliers have 50 or more employees. Data you hold for customers under a DPA stays out unless the customer agrees in writing. You keep ownership.
SaaS data and AI labs
A software company's private repositories, code reviews, incident write-ups and design documents show how a working engineering team builds and maintains a product over years. Public code does not show that. AI labs training coding and agent models want long histories from real codebases.
The line a SaaS company must hold is between its own data and its customers' data. What customers put into your product is theirs. Your data processing agreements almost certainly say you process it only on their instructions. That data is not yours to license, however large the volume.
Outrich Data works with software companies that have at least 50 employees and two years of operating history. The focus is on what the company created and owns: code, internal tooling, engineering process records and its own support operation.
Records in demand
| Record | What AI labs use it for |
|---|---|
| Private source repositories with commit history | Training coding models on how a production codebase changes over time, after secrets and credentials are stripped. |
| Pull requests and code review threads | Teaching models what reviewers ask for and how authors respond before a change is merged. |
| Issue tracker and engineering tickets | Linking a bug report or feature request to the code change that closed it, for agent training and evaluation. |
| Incident postmortems and runbooks | Training on diagnosis and recovery steps written by the engineers who handled the outage. |
| Design documents and technical specifications | Fine-tuning on how engineers argue for an architecture and record trade-offs. |
| Build, test and deployment logs | Evaluating whether a coding agent can find and fix the cause of a failed build. |
| Your own help desk tickets | Training support agents on product questions, with customer names and any customer content removed. |
Rules that apply
What the title search looks at in saas.
- Customer data processing agreements
- A DPA limits the vendor to processing customer personal data on the customer's documented instructions, as GDPR Article 28 requires. Licensing that data to a third party is outside those instructions. Review your standard DPA and negotiated variants with counsel.
- Master subscription agreement terms
- Customer contracts usually state that the customer owns its data and that the vendor must keep it confidential. Some also restrict use of usage data. These clauses define what is off limits.
- Subprocessor commitments
- Most DPAs require notice or approval before a new subprocessor receives customer data. This is one reason customer data stays out of scope by default.
- Open source and third-party code licenses
- Repositories often include code under licenses such as the GPL, or vendored commercial libraries. Those terms travel with the code. Counsel should confirm which directories you own outright.
- Employee and contractor IP assignment
- Your right to license code depends on invention assignment agreements with the people who wrote it. Gaps are more common with early contractors and should be checked.
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.
Excluded
What we will not license.
- Customer data stored or processed in your product under a DPA, without the customer's written agreement.
- API keys, credentials, secrets and security configuration found in code or logs.
- Third-party and open source code you do not own, and custom work a customer owns under a statement of work.
- End-user personal data belonging to your customers' users, including minors.
Data types common in saas
Questions
SaaS: what companies ask.
Can a SaaS company license its customers' data for AI training?
Is it safe to license proprietary source code?
Our support tickets contain customer information. Can they be used?
Who needs to sign off?
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.