What “open source” actually changes about an ERP purchase — and the costs it does not remove.
An open-source ERP is one whose source code is published under a licence that lets you read, modify and run it without paying a per-user licence fee. iDempiere, Odoo Community and ERPNext are examples. The code is free; the implementation, hosting, customisation and support are not — and those are where the real budget goes.
The phrase causes more confusion than almost any other term in enterprise software, because people hear "free" and budget accordingly. The licence genuinely is free, and on a hundred-user deployment that is a substantial recurring saving. But the work of configuring the system to your processes, migrating your data and supporting it afterwards costs the same whether the licence was free or not.
Published under a recognised open-source licence. You may run it on as many servers and for as many users as you like without paying for seats.
Available to read and modify. In practice most changes are configuration, but the ability to inspect behaviour is genuinely useful when something is wrong.
Chargeable, and the largest line in the budget. Configuration, data migration, integration, testing and training.
Yours to arrange — cloud or on-premise. Modest for most deployments compared with per-user SaaS pricing.
A support agreement with whoever implemented it, or an internal team. Not free, but not tied to a licence renewal either.
Take a hundred-user mid-market business comparing a proprietary ERP against an open-source one. The proprietary quote is often presented as a single annual figure; the open-source quote looks dramatically smaller. Both presentations are misleading, for opposite reasons.
Over five years the proprietary side carries licence or subscription fees that recur every year and typically rise, plus implementation, plus support. The open-source side carries zero licence, the same implementation effort, hosting you now pay for directly rather than through a subscription, and support from whoever you hire. The licence line genuinely disappears. The implementation line does not shrink at all — the work of configuring a chart of accounts and migrating twenty years of items is identical whichever system receives it.
The practical consequence is that implementation quality becomes almost the whole decision. On a proprietary system a poor implementation leaves you with an expensive system that works badly. On an open-source one it leaves you with a cheap system that works badly and no vendor to escalate to. The saving is real; it is simply concentrated in the line item you were going to negotiate hardest on anyway, and absent from the one that decides success.
| Term | What it means |
|---|---|
| GPL / GPLv2 | The licence most open-source ERP ships under. It gives you the right to use, modify and redistribute the source, and it is what removes the per-user fee. |
| Fork | A copy of the codebase taken in its own direction. Useful when deliberate; a serious problem when it happens accidentally because somebody modified the core. |
| Community edition | The freely available version. Watch for products where it is deliberately crippled so that the paid edition is the only usable one — that is open core, not open source. |
| Open core | A free centre with the features you actually need sold as proprietary add-ons. Legitimate as a business model, but it is not the same deal, and it is often marketed as though it were. |
| Commit history | The public record of who changed what and when. For open-source ERP this is the closest thing to a partner certification, because it cannot be claimed without evidence. |
Budget the implementation properly. A poorly implemented free ERP costs far more than a well-implemented paid one.
The question is whether the system fits your processes. Licence cost is one input, not the decision.
An open-source system with nobody who knows it is a liability. Confirm the support arrangement before you commit.
Modifying core code rather than extending it makes every future upgrade painful. Use the extension mechanism the platform provides.
| Metric | What it tells you | What distorts it |
|---|---|---|
| Five-year total cost | The only comparison that means anything. Licence, implementation, hosting, support, upgrades. | Quoting year one, where implementation dominates and the recurring licence has only been paid once. |
| Core modification count | How much of your system sits outside the upgrade path. Should be zero or close to it. | Counting files rather than behaviour — one modified core class can be worse than fifty plugins. |
| Upgrade lag | How many versions behind current you are running. Growing lag is how an open-source system becomes legacy. | Nothing; it is simply uncomfortable to look at, which is why it goes unmeasured. |
| Bus factor | How many people understand your implementation. If the answer is one, the licence saving is not your largest risk. | Counting people with access rather than people with understanding. |
We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.