Trace software to its source
The shared core and the brand-specific part are not the same asset.
Most multi-brand software is one platform with several faces. Recording the shared core, the brand modules and their relationship is what makes it possible to sell one brand without accidentally selling the engine underneath every other one.
Software Products & Components
- Product & component hierarchy
- Shared core IP
- Brand-specific modules
- Release relationships
How it helps
What you get with Software Products & Components
Products and their parts
A product is composed of components, and components can belong to more than one product without being copied.
Shared core stays visible
Core IP used across the group is marked as shared, so a transaction reaches for a licence instead of an assignment.
Releases connect to rights
Component versions link to the repositories, contributors and agreements behind them, which is where chain of title actually lives.
Software Provenance
The rest of Software Provenance
Connect repositories, contributors, agreements, components, releases and SBOM data to legal ownership.
Repositories
Inventory repositories, organizations, releases and technical custody.
Learn moreContributors & Agreements
Connect contributor identities and contribution periods to the agreements that cover their work.
Learn moreSBOM & Third-Party Components
Import open-source and third-party component data from established standards.
Learn moreAI Models & Datasets
Track models, training and fine-tuning datasets, evaluation sets and related rights.
Learn moreBuild the ownership record before somebody asks for it.
Register what exists, connect the relationships, attach the evidence. The answer you need under deadline is the one you maintained beforehand.
Evidence-backed relationships Multi-entity by design Built for transfer and diligence