Software codebases
Production source code in a real business domain.
Value factors
- Years in production
- Language and framework mix
- Test coverage
- Clear IP ownership
Data types
What data can be licensed.
Buyers look for authentic, well-documented material with a clean rights chain. These are possible candidates, not a guarantee of demand or eligibility. Start with a description; any later technical review requires agreed permission.
Engineering development history
Commits, pull requests, code reviews and issue threads.
Value factors
- Issue-to-fix linkage
- Review depth
- Contributor diversity
- Authentic, unsynthesised history
Business operations & workflows
SOPs, process logs and historical decisions.
Value factors
- Recorded outcomes
- Consistency over time
- Domain rarity
- Anonymisation feasibility
Internal documentation
Specs, wikis, runbooks and design docs.
Value factors
- Technical depth
- Link to code or outcomes
- Currency
- Confidentiality scope
Specialized industry datasets
Domain records collected through operations.
Value factors
- Volume and coverage
- Label quality
- Regulatory status
- Exclusivity potential
Archived or discontinued software
Products no longer sold but still owned.
Value factors
- Completeness
- Historical significance
- Rights chain
- Build reproducibility
Personal and third-party data. Data containing personal information, customer-owned content or regulated records is not automatically excluded, but requires legal review, a lawful basis under GDPR and appropriate privacy safeguards before any licence. Pseudonymised data can still be personal data; anonymisation does not remove contractual or IP restrictions.
Find out what your data could be worth.
Free assessment · No data upload · No obligation
Prefer to talk? Send a short message.