Business data licensing
License your development history—not your GitHub login.
Commits, pull requests, reviews and issue threads can show how software problems were solved. Your company may be able to license that history if it has the necessary permissions and can protect sensitive content. Public repository access does not automatically grant every commercial reuse right.
Free assessment · No data upload · No obligation
What can be considered
- Company development history with an identifiable origin.
- Linked issues, reviews, commits and tests, where they exist.
- A willingness to check employee, contractor and external contributor rights separately.
What buyers may evaluate
- Connections between reported problems, discussion, changes and outcomes.
- Authentic review context rather than manufactured or bulk-generated history.
- Coverage with known gaps and reliable links between records.
- An export scope that preserves useful context while excluding restricted content.
Rights and licensing restrictions
Repository administration is not proof of ownership of every contribution or discussion. Author emails, review comments and attachments can contain personal or customer data. Secrets can survive in old commits. Review platform terms, applicable licences, IP agreements and privacy obligations before any export; an NDA alone does not clear rights.
Licensing vs selling ownershipPublished data-partnership ranges mostly describe operational datasets, not codebases, so they aren't a guide to code licensing value. What drives licensing value →
How to explore the opportunity
- 01
Describe the available history
Tell us roughly how old the records are and whether engineering history is available. No account connection is required.
- 02
Flag rights and sensitivity
Mark uncertain permissions or personal data honestly. The preliminary read identifies what needs checking.
- 03
Discuss a bounded next step
With your permission, explore relevance and a scoped review. Agree access, use and retention before sharing any material.
AssetGate is an early-stage exploratory brokerage in Europe, starting with the Nordics and UK.
Common questions
- Does a public repository mean I can license everything?
- No. Public visibility, software licence permissions and ownership are different questions. Contributions and personal data need separate consideration.
- Do you need GitHub access?
- No. The initial assessment is description-only. Never share account passwords or production access.
- Can history be licensed separately from the current code?
- A separate scope may be possible, but it still needs rights review and enough permitted context to be useful.
See whether your data could earn licensing revenue.
Free assessment · No data upload · No obligation
Prefer to talk? Send a short message.