Softwr

ERP · head to head

iDempiere vs Rydoo

iDempiere logo

iDempiere

ERP

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

From
Free
Rated
-
Rydoo logo

Rydoo

Accounting

Expense management with per-user pricing and a five-user minimum, built for European multi-entity teams

From
$10/month
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.; Rydoo a five-user minimum means very small teams pay for seats they do not have, which removes Rydoo from consideration for firms of two or three.
  • They diverge on capability: iDempiere covers Application dictionary, Rydoo covers Receipt OCR.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which iDempiere and Rydoo actually diverge.

Attributes where iDempiere and Rydoo differ
AttributeiDempiereRydoo
Starting priceFree$10/month
Pricing modelOpen source, no licence feePer user per month
Free tierYesNo
PlatformsWeb, Self-hosted, Docker, Linux, WindowsWeb, iOS, Android
CategoryERPAccounting

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 Rydoo

  • Receipt OCR
  • Per diem engine
  • Mileage
  • VAT fields
  • Multi-entity
  • ERP export

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

Rydoo

  • A Belgian or German employer that must apply statutory per diem rates correctly across staff travelling in several countriesnot iDempiere
  • A group with five legal entities wanting one expense tool but separate approval chains and ledgersnot iDempiere
  • A company that already has a corporate card programme and refuses to change banks to get expense softwarenot iDempiere
  • A finance team recovering VAT on foreign travel and needing the fields captured at claim timenot 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.

Rydoo

  • A five-user minimum means very small teams pay for seats they do not have, which removes Rydoo from consideration for firms of two or three.
  • Pricing is per user rather than per active user, so organisations where most staff claim expenses twice a year still pay a full seat every month for them.
  • There is no card issuing, so real-time spend control and pre-authorisation are outside the product and remain with your bank.
  • Per diem and multi-entity handling sit on the higher tier, so the countries that most need Rydoo generally cannot buy the cheap plan.
  • Receipt extraction quality varies by language and receipt format, and finance teams still review a meaningful share of claims by hand.

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

Rydoo

$10/month
  • Essentials$10/month
    • Around 9 per user per month billed annually
    • Five-user minimum
    • Receipt capture, approvals and accounting export
  • Pro$12/month
    • Around 11 per user per month billed annually
    • Per diem engine and advanced policy controls
    • Multi-entity and multi-currency handling
  • Enterprise$undefined/month
    • Quoted pricing
    • Custom ERP and single sign-on work
    • Dedicated support and onboarding

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 Rydoo if

  • You need receipt ocr.
  • You work on Web, iOS, Android.
  • You also want per diem engine.

Questions people ask

Is iDempiere or Rydoo better?
Neither clearly leads. iDempiere starts at Free and Rydoo at $10/month, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, iDempiere or Rydoo?
iDempiere has a free tier; the other does not. Paid plans start at Free for iDempiere and $10/month for Rydoo.
Does iDempiere or Rydoo run on more platforms?
iDempiere runs on Web, Self-hosted, Docker, Linux, Windows. Rydoo runs on Web, iOS, Android.
Can I use iDempiere for free?
Yes. iDempiere has a free tier, so you can try it without paying. Rydoo starts at $10/month.
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 Rydoo is typically brought in for.
What can iDempiere do that Rydoo cannot?
iDempiere covers Application dictionary, OSGi plug-in architecture, Multi-organisation accounting, Materials management. Rydoo covers Receipt OCR, Per diem engine, Mileage, VAT fields.

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.

Rydoo: Does Rydoo issue cards?

No. It is expense software only; you keep your existing corporate card or bank programme.

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.

Rydoo: Is there a minimum?

Yes, pricing carries a five-user minimum, so the smallest bill is five seats regardless of headcount.

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.

Rydoo: Do I need the Pro plan?

If you operate per diems, multiple legal entities or multi-currency claims, yes. Essentials is for single-entity receipt and approval workflows.

iDempiere: Which database does it need?

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

Share

Related pages

Other head to heads