Three names, one lineage — and what it means if your business is still running the earlier branches.
Compiere was an early open-source ERP. A community disagreement over its commercial direction led to ADempiere, a community fork. ADempiere was later re-architected onto OSGi and a modern stack, and that became iDempiere. The data model is recognisably common across all three, which is why migration between them is a real option rather than a reimplementation.
A surprising number of businesses are still running Compiere or ADempiere instances implemented a decade or more ago, often unsupported and on obsolete infrastructure. Because the lineage is shared, moving to iDempiere is usually a migration rather than a fresh start — your data model, your configuration logic and often your reports have recognisable equivalents.
The original. A commercial open-source model whose licensing direction prompted the first fork.
The community fork, continuing development under a community governance model.
A re-architecture of ADempiere onto OSGi, ZK and a modern Java stack, with the plugin model that defines it today.
The application dictionary concept, the multi-organisation accounting model and much of the document structure.
The runtime, the UI framework and above all the extension mechanism — plugins rather than core modification.
A business evaluating open-source ERP encounters all three names, often from different vendors, and reasonably asks whether this is one product with three labels.
It is not, and the differences are practical. Compiere's open-source line effectively ended after commercial acquisition. ADempiere continues but with much reduced activity. iDempiere is the actively developed line, rebuilt on OSGi, with the plugin architecture that makes upgrade-safe extension possible. A vendor proposing ADempiere in the present day is proposing a less active codebase, and the right question is simply why — sometimes the honest answer is that it is what their team knows.
What all three share is the Application Dictionary, the metadata layer that makes so much configurable without code. That shared inheritance is why concepts transfer between them and why experience on one is genuinely relevant to another. It is also why the lineage is worth understanding rather than dismissing as history: it explains both what these systems are good at and why the active one is the one with the plugin framework.
| Term | What it means |
|---|---|
| Compiere | The original open-source ERP, from which the others descend. |
| ADempiere | The 2006 community fork, formed over disagreements about project governance. |
| iDempiere | The 2011 fork of ADempiere, rebuilt on OSGi with a modern technical architecture. |
| Fork | A branch of a codebase taken in its own direction, usually over governance rather than technology. |
| Application Dictionary | The metadata-driven architecture inherited through all three generations. |
Core data migrates well; custom code usually has to be rebuilt as plugins. Inventory it before costing the move.
An unpatched ERP on obsolete infrastructure is a security and continuity exposure, whatever its functional state.
Decide which transactional history genuinely needs to move. Carrying everything is expensive and rarely used.
Opening balances and stock valuation must reconcile to the source before the old system is switched off.
| Metric | What it tells you | What distorts it |
|---|---|---|
| Project commit activity | The most direct evidence of whether a codebase is maintained. Public, and rarely checked. | |
| Release cadence | Whether releases ship predictably. Long gaps are worth asking about. | |
| Distinct active contributors | Concentration risk. A project with one contributor carries the same risk as one supplier. | |
| Issue response time | How quickly reported problems get attention, which is the closest thing to a support signal. |
We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.