1. Mailing Lists
  2. Contributors
  3. Re: Licence question: using AGPL and Odoo proprietary modules on the same server

Contributors mailing list archives

contributors@odoo-community.org

Browse archives

Re: Licence question: using AGPL and Odoo proprietary modules on the same server

Re: Licence question: using AGPL and Odoo proprietary modules on the same server

Avatar

Re: Licence question: using AGPL and Odoo proprietary modules on the same server

by
DIXMIT Consulting SLU, Enric Tobella Alomar
- 08/09/2025 11:16:20
Hello Vincent,

From a legal standpoint, the issue centers on whether proprietary modules that are installed on the same Odoo instance as AGPL-licensed modules are to be considered derivative works of those AGPL modules. The AGPL license imposes its obligations (notably source code disclosure under AGPL terms) only when a work is derivative or based upon the AGPL-licensed code.

The OCA’s position—that AGPL and proprietary modules can coexist on the same instance provided there is no dependency relationship—is grounded in the following reasoning:

  1. Modularity and independence.
    An Odoo module is legally treated as a separate work. If a proprietary module does not include, link to, or depend on an AGPL module, it is not derivative, and the AGPL obligations are not triggered. Simply running them side by side in the same Odoo instance does not in itself create a derivative work. It is like having two processes, one AGPL and one private in your computer.

  2. Dependencies as the critical factor.
    If a proprietary module declares a dependency (via the depends key in the manifest) on an AGPL module, or reuses AGPL code, then it would be considered derivative and therefore must also be licensed under the AGPL. In contrast, if dependencies are only on LGPL modules (as is the case with the Odoo core and most OCA libraries), coexistence is legally permissible.

  3. Distinction with Odoo SA’s position.
    The 2015 Odoo SA statement reflects a more restrictive view, primarily aimed at encouraging module authors to relicense under LGPL. That stance is a policy choice rather than a strict reading of the AGPL. The legal baseline under copyright law is that AGPL requirements are triggered only by derivation, not by mere colocation on the same server.

In short: the AGPL license does not prohibit running AGPL and proprietary modules on the same instance, provided the proprietary modules do not depend on or incorporate AGPL code. This is the legal basis for the OCA FAQ.

If the propietary modules doesn't rely on the AGPL module, it shouldn't be a problem, as they can exist independently, so the private is not derivative of the AGPL and they can coexist.

Kind regards,


El lun, 8 sept 2025 a las 11:07, Vincent Hatakeyama (<notifications@odoo-community.org>) escribió:
I should have pointed out that I’m starting to believe my CEO is right.
Concerning professionnel legal advice, he told me that he never find out someone capable of replying to licence questions concerning open source.

I’m concerned, as the head of the department, of not doing something correctly and was curious about why it is written on the OCA website something that looks incorrect.

Regards,
--
Vincent Hatakeyama
Directeur du pôle développement " Orbeet
Tel +33 1 83 62 72 88 Email vincent.hatakeyama@orbeet.io
Adresse 27, boulevard Saint-Martin
75003 Paris 		Site web https://orbeet.io
Image bannière

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe



--
Enric Tobella Alomar
CEO & Founder

Reference