Free & Open-Source ERP: The True Cost
Open-source ERP is free the way a puppy is free. Where the money actually goes, the three roles a self-hosted deployment quietly requires, and the two situations where it is genuinely the right answer in Kenya.
The open-source ERP conversation in Kenya usually starts with a number: zero. It is a true number about licensing and an almost meaningless one about cost, because software licences were never the expensive part of running an operations system. The expensive parts are implementation effort, somebody who understands it, and the day something breaks — and all three are unchanged by the licence.
This is not an argument against open source. It is an argument for pricing it properly, because the businesses that regret it are the ones that priced the licence and nothing else.
Where the money goes instead
What a self-hosted deployment actually requires
The licence
This part is true and it is worth something — no per-user tax, no tier that caps your growth, no vendor able to change the price at renewal.
Hosting and operations
A server, backups you have tested rather than configured, TLS certificates, monitoring, and somebody who notices when the queue worker stops. That last one is not a setup task, it is a standing responsibility.
Implementation
The same data cleaning, counting day and training as any system, plus configuration that is generally deeper and less opinionated. More flexibility means more decisions, and every decision is your time.
A person who understands it
Either a staff member with the aptitude and the time, or a local implementation partner on a retainer. In Nairobi that is KES 30,000–120,000 a month depending on depth. This is the line item that decides whether open source is cheap or expensive.
Localisation
eTIMS, PAYE bands, NSSF and SHA, M-Pesa. Some communities have modules for some of these, of varying maintenance. Whatever is missing or stale is your project, on the authority's timetable.
The three roles nobody staffs
A hosted subscription quietly performs three jobs on your behalf. Self-hosting means somebody in your organisation does them, and the failure is not that they are hard — it is that they are nobody's job until the day they are urgent.
-
The person who applies updates
Including security updates, on a version that may have diverged from upstream because of your customisations. A deployment two years behind is a deployment nobody dares to update, and that is the normal end state of an unstaffed installation.
-
The person who restores from backup
Note: restores, not configures. A backup that has never been restored is a belief. This role is invisible until the morning it is the only thing that matters, and the test costs an hour a quarter.
-
The person who fixes it at 6pm on a Friday
Not "the community". A forum answer arrives in three days and the till is down now. This is the role most often assumed to be covered by a retainer that turns out to be business hours.
The licence is free. The person who understands it is the price, and they are the same price whether the software cost anything or not.
A five-year comparison
Self-hosted open source versus hosted subscription, 40 staff
Read the ranges rather than the midpoints. A capable technical person already on your staff who enjoys this work moves the open-source figure toward the bottom of its range and makes it genuinely competitive. Not having that person moves it toward the top and adds a category of risk that does not exist on the other side. Hosted subscription has a narrow range because there is less for you to get wrong.
Where open source genuinely wins
Strong case
You already employ the capability
A developer or senior IT person on staff who wants to own this changes the arithmetic completely. The marginal cost is their time rather than a retainer, and you get flexibility no product will give you.
Strong case
Data residency is a hard requirement
Some donor agreements and sector regulators require data to remain on infrastructure you control. That is not a preference to be argued with, and self-hosting is the answer regardless of the cost comparison.
Weak case
You want to avoid per-user pricing
Understandable, and check the arithmetic before acting on it. Add-on seats at KES 525 a month mean a five-user growth costs KES 31,500 a year — considerably less than one month of an implementation retainer.
Weak case
Nobody technical, and the licence looked free
This is the version that ends badly. Eighteen months later the deployment is unpatched, the backups are untested, the person who set it up has left, and the business is paying more for less than a subscription would have cost.
If you go this way, three conditions
Non-negotiable for a self-hosted deployment
- Name the person, and free up their time. Same rule as any implementation, with a higher stake: they own operations as well as configuration. If you cannot name them, do not start.
- Restore a backup before go-live, and once a quarter after. Actually restore it, to a separate environment, and check the data is there. An hour a quarter, and it is the difference between a backup and a hope.
- Write down what you customised, as you customise it. Every deviation from upstream is a future update you cannot apply blindly. This document is what determines whether you are still updating in year three.
On our own bias
We sell a hosted subscription, so read the comparison above with that in mind and check the figures against quotes you get yourself. The part we are most confident about is not the totals — it is the shape: open source has a much wider cost range than hosted software, and which end you land on is decided almost entirely by whether one specific person exists in your organisation.
Our take
Open source is genuinely cheaper if you already employ someone who wants to own it, and genuinely more expensive if you do not — and the licence is not the variable in either case. Decide by answering one question honestly: who applies the security update in eighteen months, by name. If there is no name, the free licence is the most expensive thing on the quote.
Price the person, not the licence
If you have the technical capability in-house, open source may well be right and we will say so. If you do not, the comparison is a hosted subscription against a retainer — and that is a much closer race than the word "free" suggests.
See plans & pricingFrequently asked questions
Is open-source ERP actually free?
The licence is, and that is worth something real — no per-user tax and no renewal price rise. But licences were never the expensive part. Hosting, backups you have tested, monitoring, localisation for eTIMS and statutory payroll, and above all a person who understands the deployment are all unchanged by the licence, and together they are most of the cost.
What does self-hosting cost over five years?
Somewhere between KES 1.75 million and 6.5 million for a forty-staff business, against roughly KES 840,000 to 1.26 million for a hosted subscription. Read the ranges rather than the midpoints: a capable technical person already on staff moves open source toward the bottom of its range, and not having one moves it toward the top and adds risk that does not exist on the other side.
What roles does self-hosting require?
Three that a subscription performs invisibly: someone who applies updates including security patches, on a version that may have diverged because of your customisations; someone who has actually restored a backup rather than configured one; and someone who fixes it at 6pm on a Friday. The community is not that third person — a forum answer arrives in three days and the till is down now.
When is open source the right choice in Kenya?
When you already employ the capability and that person wants to own it, which changes the arithmetic completely. Or when data residency is a hard requirement from a donor agreement or sector regulator, in which case it is the answer regardless of the comparison. Wanting to avoid per-user pricing is a weaker reason than it feels — five extra add-on seats cost less per year than one month of an implementation retainer.
What conditions should we set if we self-host?
Name the person who owns it and free up their time. Restore a backup to a separate environment before go-live and once a quarter afterwards — an hour a quarter, and the difference between a backup and a hope. And write down every customisation as you make it, because that document is what decides whether you can still apply updates in year three.
