Technology
Systems built to be operated by someone else.
Technology developed for licensing has to survive contact with an operator who did not write it. That shapes how it is built, documented and maintained.
Applications
Complete software applications, developed as products with a versioned release history rather than as one-off deliveries.
Data and infrastructure components
Components for collection, processing, storage and reporting of high-volume data, designed to be deployed into an operator’s own environment.
Interfaces and integration
Documented interfaces so a licensed system can be integrated with an operator’s existing platform without bespoke rework each time.
Maintenance and development
Continued development, correction and support over the life of a licence, on terms agreed in the licence itself.
How it is built
Documentation is part of the asset.
A licensed system is only as valuable as the record that comes with it. Source, build process, interfaces, dependencies and the provenance of each component are maintained alongside the code, so that a licensee can operate it and an adviser can examine it.
Third-party components are tracked with their licences, so the position on what may be sublicensed, and on what terms, is a matter of record rather than of recollection.