ERPNext (Frappe)
A full open-source ERP covering accounting, stock, buying, selling, manufacturing and HR. Installed with the bench tool on Python, MariaDB, Redis and Node.js, with background workers and a scheduler that must stay running.
ERPNext & Odoo hosting Kenya
One ERP server for every branch and warehouse
Put ERPNext, Odoo, Dolibarr or iDempiere on a VPS that head office, branches and your accountant all reach over HTTPS. You get root access to size workers, schedule backups before period close and keep a staging copy for upgrades, with free setup and free support.
20 users
We suggest
VPS V2
KES 5,000/mo
The usual starting point for ERPNext or Odoo. 8 GB of RAM covers the database, Redis and several workers comfortably for a single company with a few branches.
Order VPS V2An ERP is something the business runs on
An ERP is the system a business runs on, not one it visits now and then. Once stock, purchasing, sales invoices and payroll inputs live in ERPNext or Odoo, every branch depends on the server being up at eight in the morning and responsive at month-end, when accountants are reconciling and storekeepers are counting stock at the same time.
Many Kenyan firms begin with the ERP on a desktop at head office. That holds until a second branch opens in Nakuru or Eldoret and needs live stock levels, or until a power cut on the last day of the month stops invoicing. Moving the ERP to a VPS lets every branch, the external auditor and the director on the road work from the same records.
ERPs are heavier than websites. ERPNext runs MariaDB, Redis, background workers and a real-time socket service; Odoo runs several Python workers on PostgreSQL; iDempiere needs a Java runtime with its own memory allowance. With full root access you can size those processes, back up the database before closing a period, and keep a staging copy for testing upgrades. We set up the server and operating system; installation is handled by you or your implementation partner, with free support from us on server questions.
The problem
Where ERP projects struggle without the right server
Branches working from different numbers
When each branch keeps stock in its own spreadsheet, head office only learns about shortages and transfers at the weekly reconciliation. A central ERP on a VPS gives every location the same live stock, price list and purchase orders.
Month-end grinds to a halt
Stock valuation, depreciation runs and financial reports all hit the database in the same few days. On an underpowered machine pages time out and users retry, which makes it worse. Enough cores and memory keep closing week workable.
Upgrades that break customisations
Major Odoo and ERPNext releases can break custom modules and reports. Without a backup and a staging copy, an upgrade becomes a gamble with live data. Root access lets you clone the system, test the upgrade, then switch.
Tax invoices that must reach KRA
Invoices raised in the ERP increasingly need to pass through KRA eTIMS. An integration that runs on an office PC stalls whenever that PC is off. An always-on server keeps invoice transmission from queuing up behind outages.
What runs on it
ERP systems our customers run
These open-source ERPs all run on Linux with full root access. Pick the one your implementer knows best.
Odoo Community
Modular ERP where you add apps for inventory, purchase, accounting, manufacturing and POS. Python on PostgreSQL, run in multi-worker mode in production, so CPU cores and RAM both matter as users increase.
Dolibarr
A lightweight PHP ERP and CRM for small businesses: invoices, stock, orders and projects. Runs on MySQL, MariaDB or PostgreSQL and is happy on a small server, which makes it a good first ERP.
iDempiere
Community-driven Java ERP descended from Compiere and ADempiere, strong on multi-organisation accounting and supply chain. Runs on PostgreSQL with a Java application server, so it needs generous memory for the JVM.
Tryton
A modular Python ERP on PostgreSQL with a desktop client and a web client. Popular with developers who want a clean framework for accounting, stock and sales that they can extend themselves.
Sizing
Size your ERP server
Estimate the number of staff logged in at the busiest time of month, usually during closing and stock take.
- 1–3 users VPS V1 Only for Dolibarr or a short trial. One core and 1 GB of RAM is too little for ERPNext, Odoo or iDempiere in production, so plan to move up before go-live.
- 4–25 users VPS V2 The usual starting point for ERPNext or Odoo. 8 GB of RAM covers the database, Redis and several workers comfortably for a single company with a few branches.
- 26–70 users VPS V4 Six cores let you run more workers for busy branches and month-end reports, and 480 GB of SSD holds attachments and backups. Its 24 GB of RAM leaves room for extra workers.
- 71+ users VPS V5 Ten cores and 40 GB of RAM for multi-company groups, manufacturing or heavy reporting, where the database needs a large cache and many workers run at once.
Treat this as a starting point: the number of modules, size of your item catalogue, custom reports and integrations affect load more than headcount, so watch memory after go-live.
VPS V1
KES 2,000/mo
- 1 Core
- 1 GB RAM
- 40 GB NVMe
- 1 TB transfer
VPS V2
KES 5,000/mo
- 2 Cores
- 8 GB RAM
- 160 GB SSD
- 8 TB transfer
VPS V3
KES 7,000/mo
- 4 Cores
- 16 GB RAM
- 320 GB SSD
- 16 TB transfer
VPS V4
KES 15,000/mo
- 6 Cores
- 24 GB RAM
- 480 GB SSD
- 24 TB transfer
VPS V5
KES 20,000/mo
- 10 Cores
- 40 GB RAM
- 800 GB SSD
- 40 TB transfer
Before you go live
Before your ERP goes live
0 of 8 done. Tick them off as you go.
Built for Kenya
ERP considerations specific to Kenya
eTIMS needs an always-online system
KRA's eTIMS requires businesses to generate tax invoices through the system, and businesses with their own ERP can integrate it directly. That integration only works while the server is online, so hosting the ERP off-site avoids a backlog of untransmitted invoices after office outages.
Branches on mobile data
Upcountry branches often connect over Safaricom or Airtel 4G routers. A browser-based ERP uses far less bandwidth than remote-desktop sessions into a head office PC, and keeps working when a single branch link is slow rather than taking everyone down.
Employee and customer data obligations
An ERP holds payroll inputs, ID numbers and customer details, all covered by the Data Protection Act 2019. Controlling the server lets you limit who sees salary data, log access and keep records only as long as you need them.
Questions
ERP: your questions, answered
Can ERPNext run on a 1 GB VPS?
It can be installed, but it will not run well in production. ERPNext needs MariaDB, Redis, Node.js and several Python workers at the same time, and 1 GB leaves no room for them. Start on VPS V2 with 8 GB of RAM, and use VPS V1 only for something lighter such as Dolibarr.
Can I host Odoo Enterprise on my own VPS?
Odoo Community is open source and free to self-host. Odoo Enterprise can also run on your own server, but you need a valid subscription from Odoo for the Enterprise modules. In both cases a VPS gives you the PostgreSQL database and worker setup Odoo expects.
Do ERPNext and Odoo work with KRA eTIMS?
There are Kenyan-built eTIMS integration apps for both ERPNext and Odoo. Check with your implementer which one they support and that it follows KRA's current specification. The integration runs on the same server as the ERP, so a reliable VPS matters.
How do branches with poor internet use a hosted ERP?
A web ERP only sends small pages and data, so a 4G router is usually enough for a branch. Give each branch a backup connection from a second network if sales depend on it. If one branch link drops, the others carry on because the server is not in any branch.
Can I move from QuickBooks or Sage to ERPNext or Odoo?
Yes, usually by importing your chart of accounts, customers, suppliers, items and opening balances from CSV files, then starting fresh transactions from a cut-off date. Most firms do not migrate full transaction history. Run the import on a staging copy first and agree balances with your accountant.
How should I back up an ERP before an upgrade?
For ERPNext, run bench backup with the files option to capture the database and attachments. For Odoo, dump the PostgreSQL database and copy the filestore. Copy both off the server, then restore them onto a staging copy and test the upgrade there before touching production.
Also on VPS Hosting