Using Enterprise Modules from odoo.sh: Rights and Responsibilities

1. General Legal Context

Odoo Enterprise is not open-source; it is provided under the Odoo Enterprise Edition License v1.0 and requires an active subscription. When you use Odoo Enterprise on odoo.sh, you are using the same proprietary Enterprise code, just hosted and managed by Odoo in their cloud.

Because of this:

• You may use and modify the Enterprise code only while you have a valid Enterprise subscription for the correct number of users.
• You do not “own” the Enterprise code; you only have the right to use it under the license and your subscription agreement.

2. Accessing Modules from odoo.sh

As an odoo.sh customer, you may have technical access to the server (shell access, code browsing tools) and therefore can see the Enterprise add-ons deployed with your project.

From a legal perspective:

• Where you obtain the Enterprise modules (official download page, installation package, or odoo.sh server) does not change your obligations.
• What matters is how you use that code and whether you respect the license terms.

In practice, Odoo expects customers to download Enterprise modules through the official download channels linked to their subscription (e.g. the Enterprise download page) when they need local copies for development or on-premise installations.

3. What You Are Allowed to Do

With a valid Enterprise subscription, you are allowed to:

• Run and use the Enterprise modules on your odoo.sh project and on other instances covered by your subscription (e.g. a local development or staging database).
• Modify and extend Enterprise modules for your own use (for example by inheriting models, adding fields, or changing behavior) as long as this usage remains within your licensed environments.
• Copy modules to a local environment (for development, testing, or migration) provided that:
  • the environment belongs to you or your company;
  • it is used only for your internal business;
  • it is covered by your Enterprise subscription (production or test/development).

You may also develop new modules that depend on Enterprise modules (use them as a library) and distribute those new modules under your own license, as long as you do not copy Enterprise source code into them and your license remains compatible with the Enterprise license.

4. What You Are Not Allowed to Do

The Enterprise license explicitly forbids certain actions. You must not:

• Publish the Enterprise source code or modified Enterprise code (for example on GitHub, GitLab, public websites, or file-sharing services).
• Distribute or resell copies of Enterprise modules or modified Enterprise modules to third parties (customers, partners, other companies) who do not have their own Enterprise subscription.
• Sub-license the Enterprise code (e.g. offer it as part of your own product license) or claim ownership of Odoo’s Enterprise code.
• Continue using Enterprise modules after your subscription has expired or been terminated, even if you still have a local copy of the files.

In short: you may use and adapt Enterprise modules for your own licensed systems, but you must not share the Enterprise code itself outside the scope of your subscription.

5. Responsibilities When Copying Modules from odoo.sh

If you technically copy Enterprise modules from odoo.sh (for example via shell access or backups), you have several responsibilities:

• License compliance
  You remain fully responsible for complying with the Enterprise license. Technical access does not give you any extra legal rights.
• Environment control
  Any environment where you deploy those modules must:
  • be under your control (company infrastructure or agreed hosting);
  • be covered by your Enterprise subscription (production or development).
• Confidentiality and access
  You must ensure that:
  • Enterprise code is kept in private repositories or secure storage;
  • access is limited to your team and trusted providers working for you;
  • you do not give raw Enterprise code to third parties who are not covered by an appropriate agreement or their own subscription.
• No blocking of customer’s rights (for partners)
  If you are an official Odoo partner providing services to end customers, you are not allowed to “hold hostage” Enterprise code or block the customer’s access to their licensed modules.

6. Recommended Best Practices

To stay on the safe side when dealing with Enterprise modules and odoo.sh:

• Prefer to obtain Enterprise modules from the official Enterprise download page linked to your subscription, rather than copying them directly from containers or servers.
• Keep Enterprise code in private, access-controlled repositories; do not make it public or share it casually.
• When you develop custom modules:
  • avoid copying Enterprise source code;
  • use inheritance and extension instead;
  • publish or sell only your own modules, not the underlying Enterprise code.
• If you plan to move from odoo.sh to on-premise or another hosting provider, perform the migration using official downloads and documented procedures, and ensure your subscription and user counts remain compliant.

7. Important Disclaimer

This page is a technical and business-oriented summary of public Odoo documentation and common practice in Odoo projects. It is not formal legal advice. For definitive interpretation of your rights and obligations, you should:

• Review the official Odoo Enterprise License and Subscription Agreement.
• Contact Odoo directly (account manager or support).
• Consult with a lawyer who is familiar with software licensing and cloud services contracts.

If you have questions about how we handle Enterprise modules and odoo.sh in your project, please contact us. We will be happy to explain our approach and make sure your implementation remains compliant with Odoo’s licensing terms.