In short
Inovatree advises technology companies on software licensing and free and open source software (FOSS) compliance. Combining legal and technical expertise, we assess licence risk factor by factor, audit codebases and dependencies, set up compliance models and policies, and train teams so obligations under licences such as GPL, AGPL, Apache and MIT are met on time.
What we do
Software licensing
Advice at every stage of a company's software use and supply: drafting and reviewing licences, end user agreements and SaaS terms, and helping you acquire, protect and optimise software while preparing for identifiable risks.
Free and open source compliance
For start-ups and established corporations alike, we adapt compliance models to identify and mitigate open source risk, recommend strategies and help manage obligations on time.
Licence audits
A review of your codebase and dependencies to identify licences, flag conflicts and copyleft obligations, and set out what must be fixed before release, funding or sale.
Policy and training
An open source policy covering approval, attribution, contribution and distribution, with practical training for engineering and product teams.
How we work
- 1Identify
Which software you use, ship or host, and under which licences.
- 2Weigh the risk
Each risk factor is weighted by its importance to your business model.
- 3Fix and document
Remediation steps, notices and records that stand up in due diligence.
- 4Keep it current
A process and training so compliance continues with every release.
Frequently asked questions
When do GPL obligations apply?
The GNU GPL's main obligations, such as providing corresponding source code under the same licence, are triggered when you distribute the software or a derivative work to others. Purely internal use generally does not trigger them.
Is using AGPL software in a SaaS product risky?
It can be. The AGPL extends the GPL's source-sharing obligation to users who interact with modified software over a network, so a SaaS business that modifies AGPL code may have to offer its source code to users.
Can permissive licences like MIT and Apache be used commercially?
Yes. MIT and Apache 2.0 allow commercial use and closed-source products, but you must keep copyright and licence notices. Apache 2.0 also includes an express patent licence and requires notice of changes.
Why does open source compliance matter in funding or M&A?
Investors and acquirers review whether the code they are paying for can be owned and licensed as planned. Unresolved copyleft obligations or missing notices can delay a deal or reduce its value.