ERPNext

Last reviewed Aug 26, 2026 · 825 words

Installing ERPNext takes an afternoon, 4 GB of RAM and about 10 containers. Configuring it takes months, because it is a full ERP: accounting, inventory, manufacturing, HR, payroll, CRM and projects in one Python application built on the Frappe framework. The install is roughly 10 percent of the project. Anyone who tells you otherwise has not tried to close a financial year in it.

The Docker path is the only one I'd recommend

Frappe maintains an official frappe_docker repository, and its pwd.yml compose file is the sane starting point: MariaDB, 2 Redis instances, the Python backend, a websocket service, the scheduler, 2 queue workers and an nginx frontend. Clone it and bring it up:

git clone https://github.com/frappe/frappe_docker
cd frappe_docker
docker compose -f pwd.yml up -d

Give it 5 minutes on first boot for the create-site container to build the site, then open port 8080 and log in as Administrator with the password admin. Change that before you do anything else. The bare-metal alternative, the bench CLI on Ubuntu, works and is how the Frappe team develops, but it entangles Python, Node, MariaDB and supervisor on one host in a way you will regret at upgrade time.

The 4,096 MB minimum in the catalogue is a real minimum. With a handful of users and a few thousand transactions I would plan for 8 GB and 2 to 4 cores; the queue workers and MariaDB both want memory, and a starved instance shows up as reports timing out rather than an obvious crash.

Setup wizard decisions you cannot easily undo

The first-login wizard asks for company name, fiscal year start, currency and chart of accounts. The chart of accounts is the one to think about: ERPNext offers country-standard charts, and switching later means remapping every ledger. Pick the one your accountant recognises. Fiscal year and base currency are likewise near-permanent.

After the wizard, resist module sprawl. Enable accounting and, if you sell physical goods, stock. Leave manufacturing, HR and payroll alone until the basics are producing a correct trial balance. Each module adds its own doctypes, workflows and permissions, and the learning curve compounds rather than adds.

Upgrades are the ongoing tax

Frappe and ERPNext release a major version roughly yearly, with version-N branches receiving fixes. Moving between majors runs database migrations across hundreds of doctypes. It usually works; when it does not, you want a backup and a scratch copy to rehearse on. The command set is small:

docker compose -f pwd.yml exec backend bench --site frontend backup --with-files

That produces a database dump plus public and private file archives under the site's private/backups directory. Copy them off the host on a schedule and, before each major upgrade, restore into a throwaway stack and click through the reports you rely on. Custom apps written against Frappe's API are where upgrades most often break, so keep customisations minimal and in version control.

When ERPNext is the wrong size

For a freelancer or a 3-person shop that needs invoices and expense tracking, this is a container ship for a river crossing. Invoice Ninja does that job in a tenth of the RAM. Dolibarr sits in the middle: a PHP monolith that runs happily on 1 GB, covers CRM, invoicing and basic stock, and is far easier to keep alive as a solo admin. Odoo is the closest peer in scope; its community edition has the more polished interface but keeps more features behind the paid line, whereas ERPNext is GPL-3.0 end to end with no enterprise fork holding anything back. The wider CRM and ERP category lists the lighter options if you are unsure.

Where ERPNext earns its complexity is a business with inventory across locations, manufacturing bills of materials, multi-currency accounting or 10-plus staff who need role-based access. At that size the alternative is NetSuite at a per-seat price that makes an 8 GB VPS look free.

Hosted is a legitimate choice

Frappe runs Frappe Cloud, a managed host for the same open-source code, and the money goes to the people who write it. If the business depends on the books and nobody on staff enjoys Docker, that is the honest answer: the data stays exportable, the software stays GPL, and the 3 a.m. MariaDB problem belongs to someone else.

What I'd do

For a real business: frappe_docker on a VPS with 8 GB, accounting and stock only, the accountant's chart of accounts chosen on day one, nightly bench backup --with-files shipped off-box, and a rehearsed restore before every major upgrade. Budget 2 to 3 months of evenings to get from install to a trustworthy trial balance. For anything smaller than a warehouse, start with Dolibarr and move up only when you outgrow it.