“No licence fees” is the line every open-source ERP pitch leads with, and it’s true, and it’s also not the whole story. A per-seat proprietary licence is an obvious, budgeted cost. An open-source implementation trades that obvious cost for a set of less obvious ones that are worth understanding before you commit, not after.
What “free” actually means
Frappe/ERPNext and Odoo are both genuinely free to run. No per-user fee, no annual renewal to a vendor, no forced upgrade cycle tied to a licence expiring. Over a five-year horizon against a comparable proprietary system charging even a modest per-seat fee, the difference compounds into real money, often enough to fund the entire implementation and then some.
That’s real and it’s why we lead with it too. But the software being free doesn’t mean the total cost of running it is zero.
Where the real cost lives instead
Implementation and configuration time doesn’t disappear because the licence is free, it’s still the majority of the actual project cost either way. Hosting is your responsibility, not a vendor’s, which is a cost and also a genuine advantage: you control where your data lives and what compliance regime it falls under, which matters a great deal for government and financial-sector clients specifically.
Ongoing maintenance is the part people underestimate most. Someone needs to apply updates, manage backups, and own the system when something breaks at an inconvenient hour. With a proprietary vendor, that’s bundled into the licence fee whether you want it bundled or not. With open-source, you’re choosing explicitly, in-house team, a support retainer with an implementation partner, or accepting the risk of neither. All three are legitimate choices. Only one of them is honest about being a choice.
Why we still recommend it almost every time
The reason isn’t that open-source is free, it’s that it’s yours. You’re not dependent on a vendor’s roadmap deciding your system stops receiving updates, or a pricing change landing on renewal with no negotiation. Customization isn’t a change request against someone else’s product, it’s a change to code you can read and, if it comes to it, a different partner can read too.
We tell clients the honest version of this before they sign anything: budget for implementation and for ongoing support, the same way you would with proprietary software, and treat the absence of a licence fee as what it actually is, one real cost removed, not the whole cost of ownership eliminated. That’s a more useful number to plan around than the marketing version, and it’s the number that’s actually held up on every implementation we’ve delivered.