Skip to Content

Contributors

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

Pedro,

Please don't assert things you can't possibly know about how other companies operate and why.

Best,

-Stéphane

On Fri, Sep 12, 2025 at 3:32 PM Pedro M. Baeza <notifications@odoo-community.org> wrote:
So you have provided the perfect example for confirming the hypothesis that going LGPL, the number of contributions will be reduced: how can it be that Tecnativa, having only 10 persons, contributes 4x more than companies like Camptocamp/Acsone, that have 40/50 persons?

They develop on top of enterprise modules, which they can't share, so they don't contribute to OCA.

They develop more private things, as they are allowed due to the license being LGPL, so they don't contribute back to OCA.

And again, remember the big vendor lock-in you are imposing on your customers installing enterprise modules, being the vendor Odoo S.A., not you. And even not advertising that to your customers (by ignorance or complacency). That's the big win of Odoo doing that the conversation doesn't turn around this.

Regards.

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


by Stéphane Bidoul - 03:55 - 12 Sep 2025

Reference

  • Licence question: using AGPL and Odoo proprietary modules on the same server
    Hi,

    After years of only working on Odoo community, we are starting to have several enterprise clients.

    The OCA website at https://odoo-community.org/resources/faq indicates:

    Can I run OCA AGPL modules and closed source modules on the same instance?
    Yes, as long as closed source modules do not depend on AGPL ones and respect the license of its dependencies defined in the “depends” key of its manifest file (and vice versa).


    Will we be able to use AGPL modules and paid ones?

    Odoo projects will be able to use AGPL modules or paid modules under proprietary licenses, but it is not possible to combine both. Combining LGLPv3 modules and proprietary modules is fine however, so we encourage current owners licensing under AGPL to move to LGPLv3 too, in order to avoid complications for end users.

    My CEO believes that this using both AGPL and proprietary modules, even if they do not have dependencies, is not allowed by the AGPL license.
    I’ve searched a bit on the mailing list (that started in 2015) but I have not found no discussion on the subject.
    On what basis does the OCA position comes from?

    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

    by "Vincent Hatakeyama" <vincent.hatakeyama@orbeet.io> - 10:36 - 8 Sep 2025