Softwr

ERP · head to head

iDempiere vs Propel

iDempiere logo

iDempiere

ERP

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

From
Free
Rated
-
Propel logo

Propel

Manufacturing

PLM, quality and product information management built on the Salesforce platform

From
On request
Rated
-

The short version

  • Only iDempiere has a free tier, so it costs nothing to try first.
  • 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.; Propel your product data lives in a Salesforce org, so a future decision to leave Salesforce becomes a PLM migration as well as a CRM one, and the extraction is not trivial.
  • They diverge on capability: iDempiere covers Application dictionary, Propel covers Item and BOM management.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which iDempiere and Propel actually diverge.

Attributes where iDempiere and Propel differ
AttributeiDempierePropel
Starting priceFreeOn request
Pricing modelOpen source, no licence feequote
Free tierYesNo
PlatformsWeb, Self-hosted, Docker, Linux, WindowsWeb, iOS, Android, Cloud, API
CategoryERPManufacturing

Identical on both: 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 Propel

  • Item and BOM management
  • Change management
  • Quality management
  • Product information management
  • Supplier collaboration
  • Native Salesforce
  • Licence types

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 Propel
  • 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 Propel
  • 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 Propel
  • 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 Propel

Propel

  • A medical device company needing linked design control and CAPA records for an ISO 13485 audit without an on-premise PLM programmenot iDempiere
  • A consumer products firm publishing the same product record to engineering, packaging and e-commerce teamsnot iDempiere
  • A company already standardised on Salesforce that wants product data governed with the same admin skills as the CRMnot iDempiere
  • A hardware manufacturer routing customer complaints straight to the part revision and supplier that caused themnot 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.

Propel

  • Your product data lives in a Salesforce org, so a future decision to leave Salesforce becomes a PLM migration as well as a CRM one, and the extraction is not trivial.
  • CAD data management is handled through connectors rather than natively; Propel manages metadata and files well but is not a substitute for a CAD vault on large assemblies.
  • The published cost bands are extremely wide, from 10,000 to 500,000 US dollars a year, and setup can approach the annual licence, so early budgeting without a scoped quote is close to meaningless.
  • Licence roles are split across Performance, Quality, Enrichment, Collaboration and Partner types, and buyers frequently discover mid-project that a user needs a more expensive role than budgeted.
  • Salesforce platform limits such as governor limits, API call ceilings and storage allowances apply, and organisations with very large BOMs or heavy integration traffic hit them in ways a purpose-built PLM would not surface.

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

Propel

On request
  • Propel$undefined/year
    • Annual user-based licensing in role types
    • Salesforce platform access included in each licence
    • Indicative small deployment band of 10,000 to 150,000 USD a year plus 10,000 to 25,000 setup

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.

Choose Propel if

  • You need item and bom management.
  • You work on Web, iOS, Android, Cloud, API.
  • You also want change management.

Questions people ask

Is iDempiere or Propel better?
Neither clearly leads. iDempiere starts at Free and Propel at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, iDempiere or Propel?
iDempiere has a free tier; the other does not. Paid plans start at Free for iDempiere and On request for Propel.
Does iDempiere or Propel run on more platforms?
iDempiere runs on Web, Self-hosted, Docker, Linux, Windows. Propel runs on Web, iOS, Android, Cloud, API.
Can I use iDempiere for free?
Yes. iDempiere has a free tier, so you can try it without paying. Propel starts at On request.
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 Propel is typically brought in for.
What can iDempiere do that Propel cannot?
iDempiere covers Application dictionary, OSGi plug-in architecture, Multi-organisation accounting, Materials management. Propel covers Item and BOM management, Change management, Quality management, Product information 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.

Propel: Do I need to buy Salesforce separately?

No. Each Propel licence includes Salesforce platform access, and end users do not need their own Salesforce licences or Salesforce expertise.

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.

Propel: Does being on Salesforce lock me in?

Practically, yes. The application, its configuration and your product data all sit in a Salesforce org, which is a real consideration at renewal.

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.

Propel: What does it cost?

Propel publishes indicative bands rather than list prices: roughly 10,000 to 150,000 US dollars a year for a small deployment and 250,000 to 500,000 for a large one, plus setup.

iDempiere: Which database does it need?

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

Propel: Is it suitable for regulated medical devices?

Yes, that is a core segment; the quality module covers CAPA, non-conformance, audits and training records with electronic signatures.

Share

Related pages

Other head to heads