GNU LGPL 2.1
LGPL-2.1Weak copyleftOSI-approved open-source licence
Weak copyleft. Changes to the covered code must stay open if you distribute them. Internal use is unaffected.
Verify with a lawyer. This is guidance, not legal advice. Check with a lawyer before deciding.
What the licence means per use case
The verdict applies to the licence family (Weak copyleft). An individual product can have its own terms; you get the full per-product analysis when you sign in. Confidence: high.
| Use case | Verdict | What it means |
|---|---|---|
| U1 Self-hosted, internal use, unmodified | Allowed | Free to use internally. |
| U2 Self-hosted and modified | Allowed | Changes only need sharing if you distribute them (covered files only). |
| U3 Novro hosts it for you (single-tenant) | Allowed | Allowed to host for customers. |
| U4 Shared multi-tenant instance | Allowed | Allowed in a shared instance. |
| U5 In your cloud, managed by Novro | Allowed | Allowed. Ship the licence notices. |
| U6 Redistribution (builds, images, appliances) | Conditions apply | Source for modified covered files must be provided. |
| U7 Commercial use | Allowed | Commercial use is allowed. |
| U8 AI acceptable use (AUP, EU AI Act) | Not applicable | Not applicable to this licence type. |
Building on it: what may you do?
Short answers based on the licence, for the version in the catalog.
- B1 Change the code for internal use in your company Yes Yes.
- B2 Build your own product or service on top and offer it to customers as SaaS Yes Yes. Running it as a service is not distribution.
- B3 Make a closed-source derivative and sell or distribute it Yes, with conditions Yes, if your code stays separate (e.g. the library linked, your own files). Changes to the licensed code must be shared.
- B4 Use the project's name and trademark No No, not without permission. The licence covers the code, not the name or logo.
This is guidance, not legal advice. Check with a lawyer before deciding.
Common pitfalls
- If you link the library into a product you distribute, the recipient must be able to replace the LGPL part (dynamic linking is easiest).
- Changes to the library itself must be shared under the LGPL if you distribute them.
The licence text
Last reviewed:
Products in the catalog under LGPL-2.1
This is guidance, not legal advice. Check with a lawyer before deciding.