Softwr

ERP · head to head

iDempiere vs OpenBOM

iDempiere logo

iDempiere

ERP

Community-governed open source ERP, CRM and supply chain built on Java, OSGi and PostgreSQL

From
Free
Rated
-
Full reviewWebsite
OpenBOM logo

OpenBOM

Manufacturing

Cloud bill of materials and part catalogue management priced per seat, with free read-only users

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: iDempiere there is no vendor, so there is no support contract, no service level agreement and nobody to escalate to; you either build the skills internally or you depend entirely on a local partner whose quality you must judge yourself.; OpenBOM pricing has three axes, editing seats plus data record count plus per-seat CAD add-ins at $25 to $45 each, so the real annual cost is well above the advertised per-seat figure.
  • They diverge on capability: iDempiere covers Application dictionary, OpenBOM covers Multi-level BOMs.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which iDempiere and OpenBOM actually diverge.

Attributes where iDempiere and OpenBOM differ
AttributeiDempiereOpenBOM
Pricing modelOpen source, no licence feePer user per month
PlatformsWeb, Self-hosted, Docker, Linux, WindowsWeb, Windows, macOS, API
CategoryERPManufacturing

Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in iDempiere

  • Application dictionary
  • OSGi plug-in architecture
  • Multi-organisation accounting
  • Materials management
  • Manufacturing
  • Workflow engine
  • Report and print engine
  • No paid edition

Only in OpenBOM

  • Multi-level BOMs
  • Part catalogue
  • CAD add-ins
  • Change management
  • Free read-only users
  • REST API

What people use each for

The jobs each tool is most often brought in to do.

iDempiere

  • A distributor wants multi-organisation, multi-currency accounting and warehouse costing without a per-user ERP licence that scales with headcount.not OpenBOM
  • An organisation that has been caught by an open core vendor moving features into a paid tier wants an ERP with no company that can make that decision.not OpenBOM
  • A team needs heavy customisation of screens, fields and approval workflows that must survive version upgrades, which the application dictionary makes possible without forking.not OpenBOM
  • A public sector or university body in Latin America or Indonesia needs a locally supportable ERP where the source and the implementation skills are both available in-country.not OpenBOM

OpenBOM

  • A hardware startup replacing a shared BOM spreadsheet before its first contract manufacturing runnot iDempiere
  • A contract manufacturer sharing structured BOMs with customers who should see but not edit themnot iDempiere
  • An electronics team pulling BOMs straight out of Altium and mechanical CAD instead of retyping themnot iDempiere
  • A small manufacturer that needs part numbering and revision discipline but cannot fund a PLM projectnot iDempiere

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

iDempiere

  • There is no vendor, so there is no support contract, no service level agreement and nobody to escalate to; you either build the skills internally or you depend entirely on a local partner whose quality you must judge yourself.
  • It demands real Java, OSGi and PostgreSQL administration, so the running cost is a systems engineer rather than a subscription, and that engineer is harder to hire than a PHP developer.
  • The ZK-based interface is dense and dated, with a data-entry feel inherited from Compiere that staff used to modern software find hostile, which drives up training cost.
  • Localisation depends on community contribution, so tax, payroll and statutory reporting for your country may be absent, out of date or maintained by one person, and you may end up funding it yourself.
  • The documentation is a community wiki with gaps and stale pages, and much of the practical knowledge sits in forum threads and partner heads rather than in anything you can hand to a new administrator.

OpenBOM

  • Pricing has three axes, editing seats plus data record count plus per-seat CAD add-ins at $25 to $45 each, so the real annual cost is well above the advertised per-seat figure.
  • Paying yearly nearly halves the seat price, from $55 to $30 and $165 to $90, so monthly billing carries an unusually heavy penalty for teams that want flexibility.
  • Change management, revision control and CAD file management are absent from the entry Team plan, so the cheapest tier is a catalogue rather than a working PLM.
  • It lacks the approval workflows, effectivity dating and audit depth that regulated medical and aerospace suppliers need, so companies pursuing ISO 13485 or AS9100 typically migrate away.
  • Record count is metered separately and a large imported part library can push a small team into a higher data tier without adding a single user.

Pricing, plan by plan

iDempiere

Free
  • iDempiereFree
    • Full ERP, CRM and supply chain source
    • Unlimited users and organisations
    • No enterprise edition and no feature gating
  • Implementation partner$undefined/year
    • Local partners provide installation, configuration, training and support
    • Priced per engagement, not published
    • Realistically the only viable route for a production deployment

OpenBOM

Free
  • FreeFree
    • Up to 2,000 data records
    • Basic BOM and catalogue management
    • Non-commercial and educational use
  • Professional Team$55/month
    • $30 per seat per month billed yearly
    • BOM management, part catalogue, inventory
    • RFQ and purchase orders
  • Company$165/month
    • $90 per seat per month billed yearly
    • Everything in Team
    • CAD file management and revision control
  • Enterprise$undefined/year
    • Single sign-on
    • Custom integrations
    • Private or custom hosting

Which should you pick?

Choose iDempiere if

  • You need application dictionary.
  • You want to start without paying.
  • You work on Web, Self-hosted, Docker, Linux, Windows.
  • You also want osgi plug-in architecture.
iDempiere review

Choose OpenBOM if

  • You need multi-level boms.
  • You want to start without paying.
  • You work on Web, Windows, macOS, API.
  • You also want part catalogue.
OpenBOM review

Questions people ask

Is iDempiere or OpenBOM better?
Neither clearly leads. iDempiere starts at Free and OpenBOM at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, iDempiere or OpenBOM?
iDempiere starts at Free and OpenBOM at Free.
Does iDempiere or OpenBOM run on more platforms?
iDempiere runs on Web, Self-hosted, Docker, Linux, Windows. OpenBOM runs on Web, Windows, macOS, API.
Can I use iDempiere for free?
Both have a free tier, so you can try either at no cost before committing.
What is iDempiere best used for?
iDempiere is most often used for a distributor wants multi-organisation, multi-currency accounting and warehouse costing without a per-user erp licence that scales with headcount., an organisation that has been caught by an open core vendor moving features into a paid tier wants an erp with no company that can make that decision., a team needs heavy customisation of screens, fields and approval workflows that must survive version upgrades, which the application dictionary makes possible without forking., a public sector or university body in latin america or indonesia needs a locally supportable erp where the source and the implementation skills are both available in-country.. Of those, a distributor wants multi-organisation, multi-currency accounting and warehouse costing without a per-user erp licence that scales with headcount. and an organisation that has been caught by an open core vendor moving features into a paid tier wants an erp with no company that can make that decision. are not what OpenBOM is typically brought in for.
What can iDempiere do that OpenBOM cannot?
iDempiere covers Application dictionary, OSGi plug-in architecture, Multi-organisation accounting, Materials management. OpenBOM covers Multi-level BOMs, Part catalogue, CAD add-ins, Change management.

Answered from the vendors’ own pages

iDempiere: Is iDempiere the same as ADempiere or Compiere?

It shares the lineage. iDempiere forked from ADempiere in 2011 to rebuild the platform on OSGi, and it is the branch that remains actively developed.

OpenBOM: Is OpenBOM free?

There is a genuine free tier limited to 2,000 data records and aimed at non-commercial and educational use. Commercial teams start at $30 per seat per month billed yearly.

iDempiere: Is there a paid or enterprise edition?

No. There is no commercial owner and no feature gating. Money is spent on implementation partners and hosting, not on licences.

OpenBOM: Do I pay for people who only look at BOMs?

No. Read-only users are unlimited and free on every paid plan, which is the main reason the total cost undercuts seat-for-seat PLM tools.

iDempiere: What does it actually cost to run?

Nothing in licence fees, and a great deal in skills: expect a partner implementation and ongoing Java and PostgreSQL administration, which for a mid-sized company is comparable to a commercial subscription.

OpenBOM: Are the CAD add-ins included?

No. They are $25 per seat per month billed yearly, $45 monthly, and require an active Team or Company subscription.

iDempiere: Which database does it need?

PostgreSQL or Oracle. PostgreSQL is the mainstream community choice and the one most partners deploy.

OpenBOM: Can OpenBOM replace a full PLM?

For a startup, usually yes. For regulated manufacturing needing controlled workflows and full audit trails, no.

Share

Related pages

More on iDempiere

More on OpenBOM

Keep looking

Other head to heads