Skip to Content
This question has been flagged
2 Replies
654 Views
Avatar
Robert Taylor

Hi guys.

Preamble:

  • I have read a great deal of the documentation.
  • I have read the Community vs Enterprise comparison page and read a bunch of discussions on the topic.
  • I have 17 and 18 installed on prem in a vm.
  • I have familiarized my self with Odoo from the user side by configuring it to a reasonable degree.
  • I have familiarized my self with Odoo from the sysadmin perspective by configuring it from scratch.
  • I have read up a bit on creating new modules and programming for Odoo.
  • I have tried the cloud demo.
  • I have looked at buying a monthly enterprise license for on prem but this is not allowed and Odoo requires me to buy a full years subscription.  This leaves me without any way to really test and compare. 

Question:  Is the community edition considered a "subset" of the enterprise edition or is it considered a "completely separate project / codebase"?

I have run into the description that "the community edition is completely separate from the enterprise edition" but that doesn't look quite right and seems like an oversimplification.  To me it looks like the community on prem edition is a subset codebase and just purchasing the enterprise on prem license will downlaod+install the missing modules. Is that the correct understanding?

Any insights and guidance is appreciated.


Avatar
Discard
Robert Taylor
Author

Oh I see.  I greatly appreciate the detailed explanation.  That helps tremendously.

Thank you.

Ray Carnes (ray)

Test Odoo Enterprise for 15 days at odoo.com/trial

Avatar
Rajprasad Joshi
Best Answer

Here's the general architecture:

  1. Core/CE:
  • Both editions share the same core foundation
  • Bug fixes and security patches typically affect both editions
  • Basic features are maintained in parallel
  1. Enterprise Features:
  • EE builds on top of CE with additional modules/features
  • These aren't just "locked" features in CE - they're additional codebases
  • Some EE features require architectural components not present in CE
  1. Development Model:
  • CE is developed in public, open source repositories
  • EE features are developed in private repositories
  • Changes to shared components need to be synchronized between editions


CE = Core Modules
EE = Core Modules + Enterprise Modules



When you purchase an EE license, you're not just "unlocking" features - you're getting access to additional code modules and often different architectural components.
Avatar
Discard
Avatar
Juan Luis Cano
Best Answer

Thanks @Rajprasad for the answer. Would like to ask some follow-up clarifications.

From your quoted text:

CE = Core + Community Features
EE = Core + Community Features + Enterprise Features + Enterprise Modifications

Applying some basic substitution rules...

EE = (Core + Community Features) + Enterprise Features + Enterprise Modifications =
   = CE + Enterprise Features + Enterprise Modifications

I know I'm being a bit pedantic but does this mean that the "Enterprise Modifications" affect or tweak the Core (potentially in a way that makes other 3rd party add-ons incompatible)? Could you describe a bit more?

Avatar
Discard