Open-source ERP in 2026: revisit ERPNext, Odoo Community and Dolibarr before you move another business onto a new ERP

An ERP is the one application that touches almost everyone in a company. Sales raises the order, stores issue the material, production books the output, accounts raise the invoice and file the tax return, and management reads the numbers at month end. When the ERP is wrong, everyone feels it. When the ERP is changed, everyone feels that too.

Many small and mid sized Indian companies still run on a desktop accounting package plus Excel sheets, or on an ERP licence that was bought ten years ago and never upgraded. Open source ERPs offer a different path: you can read the code, run it on your own server or with a hosting partner of your choice, and keep the data in your own database. In 2026 three projects come up in almost every such discussion: ERPNext, built on the Frappe framework; Odoo Community, the open source edition of Odoo; and Dolibarr, a long running PHP ERP and CRM.

This post revisits all three calmly. We look at where each came from, licences and paid editions, how each is built, security record, operations, Indian GST relevance and when not to adopt each. We did not run a hands-on drill for this post, because an ERP test says very little without a full stack, a chart of accounts and real transactions. Facts below come from official repositories, release pages, licence files and security advisories, read on 3 November 2026. Where we write from general knowledge, we say so.

A scenario to keep us honest

To keep the discussion practical, we use an invented company. This company is illustrative only; any resemblance to a real firm is accidental.

Nashik Godavari Fasteners (invented) makes bolts, nuts and precision turned parts for automotive and agricultural equipment makers in Maharashtra and Gujarat. It has about 180 employees, two plants in an industrial area, and an IT team of three led by Prasad. Today:

• Accounts run on a desktop accounting package. GST returns are prepared by the accountant from exports and Excel.
• Production planning, stores and job work challans are kept in Excel sheets that are emailed between the two plants.
• Sales orders come by email and WhatsApp. Nobody can quickly say which order is waiting for which raw material.
• Two large customers have started asking for e-invoices with correct HSN codes and for better delivery commitments.

The owners want one system for orders, stock, production, purchase and accounts. They have heard of ERPNext and Odoo from other factory owners and Dolibarr from a consultant. They do not want a big bang project, and they cannot afford a failed month end.

The short version

• ERPNext is the strongest fit when you want a full manufacturing and accounting ERP under a single GPLv3 licence, with no separate paid edition of the code. Indian GST support comes through a separate open source app, India Compliance.
• Odoo Community is a polished, modular base under LGPLv3, but several things many companies expect, such as the full accounting app, Studio and some advanced modules, sit in the paid Enterprise edition. Read the edition comparison before you plan.
• Dolibarr is the lightest of the three, simple to host on a plain PHP and MySQL or MariaDB server, and suited to smaller firms with simpler processes. It is less deep in manufacturing and has no Indian GST layer of the same depth that we could verify.
• For Nashik Godavari Fasteners, we would pilot ERPNext with India Compliance first, keep Odoo as a serious second option if they are open to paying for Enterprise, and not move accounts until a full month end has been run in parallel.

Where things stand on 3 November 2026

ERPNext

• Repository frappe/erpnext on GitHub, created June 2011, about 40,900 stars, licence GPL-3.0.
• Two maintained major lines: version 16 (v16.53.0 published 28 October 2026) and version 15 (v15.124.3 published 30 October 2026).
• Built on the Frappe framework (frappe/frappe, MIT licence), with releases v16.54.0 and v15.125.0 published 27 October 2026.
• Releases are frequent, often weekly. That is good for fixes but means you must plan regular updates.

Odoo Community

• Repository odoo/odoo on GitHub, created May 2014, about 55,500 stars.
• The LICENSE file says Odoo is published under the GNU LGPLv3.
• The default branch is 20.0, and its release.py marks version 20.0 as final. It sets Python 3.12 and PostgreSQL 16 as minimums. The 19.0 branch sets Python 3.10 and PostgreSQL 13.
• Odoo does not publish GitHub releases the way the other two do. Updates arrive as commits on each stable branch and as nightly builds.

Dolibarr

• Repository Dolibarr/dolibarr on GitHub, created June 2011, about 7,800 stars, licence GPL-3.0.
• Latest GitHub release 24.0.1 published 7 September 2026, after 24.0.0 on 20 August 2026. A 24.0.2 tag exists, and the 24.0 branch ChangeLog already lists fixes for 24.0.3.
• Two security advisories were published on 21 October 2026: a remote code execution through an incomplete sandbox in computed extrafields, and an SQL injection in the third party class. Check the advisory pages for fixed versions before you deploy.

First questions before choosing

• Which processes must the ERP run on day one: accounts and GST only, or also stock, purchase, production and job work?
• Who will own the system after the partner leaves: an internal team, or a support contract?
• Are you willing to pay a per user subscription for an Enterprise edition, or do you want only open source code?
• Will you self-host on your own VM, use a managed host, or use the vendor cloud?
• How will you test upgrades before applying them to the live books?
• Who signs off that the GST returns produced by the system are correct?

How each one is built

ERPNext

ERPNext is an app on the Frappe framework. Frappe is a Python web framework with a metadata driven design: every business object is a DocType, and forms, lists, reports, permissions and the REST API are generated from that definition. A typical setup uses MariaDB as the database, Redis for cache and queues, background workers, a socket server for real time updates, and Nginx in front. Installation and updates are managed with the bench command line tool, and official Docker images exist under the frappe_docker project. Custom work is usually done as a separate Frappe app, so the core can be upgraded without touching your changes. (The component list is from general knowledge of the Frappe documentation; check the current install guide for your version.)

Odoo Community

Odoo is a Python application with its own ORM on PostgreSQL. Everything is a module: sales, inventory, manufacturing, website and many more. Modules can extend each other through inheritance, which is powerful but means a third party module may break when either the core or another module changes. Odoo ships a web client built with its own JavaScript framework. A large community ecosystem around the Odoo Community Association (OCA) publishes extra modules under open source licences. (OCA details are general knowledge.)

Dolibarr

Dolibarr is a classic PHP application that runs on a standard web server with MySQL, MariaDB or PostgreSQL. Features are switched on as modules from the setup screen: third parties, proposals, orders, invoices, stock, manufacturing orders, projects, HR and a point of sale (TakePOS). Its simplicity is its strength: it runs on ordinary shared or VPS hosting, and a non specialist can install it. (Supported databases are from general knowledge; confirm with the current documentation.)

Licences and editions

ERPNext

ERPNext is GPLv3, and the Frappe framework is MIT. There is no closed Enterprise edition of the code. Frappe Technologies sells hosting through Frappe Cloud and support, and partners sell implementation. If you modify ERPNext and distribute it, GPLv3 obligations apply; running it internally is not distribution.

Odoo Community and Enterprise

Odoo Community is LGPLv3. Odoo Enterprise is a separate, proprietary set of modules under the Odoo Enterprise licence, sold as a subscription, which runs on top of Community. In general, the Enterprise edition adds things such as Studio, the full accounting suite, some localisation and many vertical apps. (The exact split changes between versions; read the current official editions comparison page rather than trusting any blog, including this one.) The practical point: if your plan depends on a feature that is Enterprise only, you are no longer choosing a purely open source ERP.

Dolibarr

Dolibarr is GPLv3. There is no closed core edition. Extra modules are sold by third parties through the DoliStore marketplace, and hosted Dolibarr is available from several providers. (Marketplace details from general knowledge.)

Indian GST relevance

This is where many small firms make or break an ERP project.

• ERPNext: Indian GST features live in the India Compliance app (resilient-tech/india-compliance on GitHub, created December 2021, GPL-3.0, latest release v15.33.0 published 27 October 2026). From general knowledge, it covers GSTIN validation, e-invoice and e-way bill generation through a GST Suvidha Provider integration, and return preparation helpers. Some API based features are linked to a paid API service. Verify current features and charges on its documentation.
• Odoo: Odoo has an Indian localisation for chart of accounts and GST taxes. From general knowledge, e-invoicing and e-way bill integration for India are in Enterprise modules. Confirm on the current editions page and with an Odoo partner.
• Dolibarr: Dolibarr supports multiple tax rates and local taxes, but we could not verify a maintained Indian e-invoice or e-way bill module from primary sources. Treat Indian GST compliance as a gap to fill with a partner module or manual work.

Whatever you choose, have your chartered accountant check the first two months of GST outputs line by line against the old system. Software support for a rule is not the same as correct setup for your business.

Security, sign-in and permissions

Sign-in

All three support username and password with role based access. From general knowledge, Frappe supports two factor authentication and social or OAuth logins, Odoo supports OAuth and two factor authentication in Community with LDAP as a module, and Dolibarr supports LDAP. Check each for SAML or OIDC with your identity provider before promising single sign-on.

Permissions

• ERPNext uses roles and permission rules per DocType, plus user permissions that restrict records, for example by company or warehouse.
• Odoo uses groups, access rights per model and record rules.
• Dolibarr uses per user and per group permissions per module.

In each, the common failure is the same: everyone is made an administrator during the pilot, and nobody removes it.

Advisory record

All three projects publish security fixes. Dolibarr had two advisories on 21 October 2026, one of them remote code execution. ERPNext and Frappe publish advisories on their GitHub repositories. Odoo publishes security advisories through its own channels. (Odoo’s advisory process is general knowledge.) An ERP holds bank details, salaries and customer data, so:

• never expose the admin interface to the open internet without need;
• put it behind a reverse proxy with TLS, and ideally behind VPN for internal staff;
• subscribe to advisory notifications for your chosen product;
• keep a tested path to apply security patches within days, not months.

Operations and day two

Install

• ERPNext: bench on a Linux VM, or frappe_docker with Docker Compose, or Frappe Cloud.
• Odoo Community: packages, source with a Python virtual environment, or the official Docker image, with PostgreSQL.
• Dolibarr: a PHP web server with a database, packages for several Linux distributions, or Docker images.

Upgrades

• ERPNext releases often. Minor updates inside a major version are usually smooth with bench update, but custom apps must be tested. Major upgrades (15 to 16) need a test copy first.
• Odoo major version upgrades change the database schema, and community modules must be ported. From general knowledge, Odoo offers an upgrade service for Enterprise customers; Community users often use OCA OpenUpgrade scripts, which may lag new versions. This is the biggest operational cost of Odoo Community.
• Dolibarr upgrades run through an install wizard that migrates the database. Upgrade one major version at a time and test third party modules.

Backups

• ERPNext: bench backup takes a database dump plus public and private files. Copy them off the server and test a restore.
• Odoo: back up the PostgreSQL database and the filestore together; one without the other is not a backup.
• Dolibarr: back up the database and the documents directory.

For all three, a monthly restore test on a separate VM is the only proof that your backups work.

Hosting

A small company with under 50 active users can usually start on one VM, but sizing depends on transactions, reports and custom code. We do not quote numbers here because none of the three projects publishes sizing that we could verify for your load. Measure during the pilot.

Migration from an existing system

• Start with masters: chart of accounts, customers, suppliers, items with HSN codes, warehouses and bill of materials.
• Bring opening balances as of a clean date, ideally the start of a quarter or financial year.
• Do not import years of old transactions unless an auditor needs them inside the ERP; keep the old system read only instead.
• Clean the item master first. Duplicate items are the most common source of stock errors after go live.

Side by side

Best fit

• ERPNext: manufacturing and trading companies that want a complete open source ERP, with GST through India Compliance.
• Odoo Community: companies that like the Odoo ecosystem and either need only Community modules or are ready to pay for Enterprise.
• Dolibarr: small firms, services and trading companies with simple processes and a preference for plain PHP hosting.

Licence and cost model

• ERPNext: GPLv3 code, pay for hosting, support or a partner if needed.
• Odoo: LGPLv3 Community, proprietary Enterprise by subscription.
• Dolibarr: GPLv3 code, paid add-on modules and hosting from third parties.

Operations

• ERPNext: frequent releases, bench tooling, custom apps kept separate.
• Odoo: major upgrades are the main effort, especially with community modules.
• Dolibarr: simple stack, step by step upgrades, watch security advisories.

A worked plan for Nashik Godavari Fasteners

Month 1: prepare

• List processes for day one: orders, purchase, stores, job work, production, invoicing, GST.
• Clean the item master and assign HSN codes. Clean customer and supplier lists with GSTINs.
• Decide the go live date at a quarter start.

Months 2 and 3: pilot

• Install ERPNext version 16 with India Compliance on a test VM behind VPN, using bench or frappe_docker.
• Load masters and run one product family from order to invoice, including a job work challan.
• In parallel, give two people a short trial of Odoo with the modules they would actually buy, and note which features are Enterprise only.
• Ask the accountant to compare GST outputs from the pilot with the old system.

Month 4: decide

• If ERPNext handles the job work and GST flows with acceptable custom work, standardise on it.
• If the team strongly prefers Odoo and the Enterprise subscription fits the budget, move to Odoo with a partner.
• Dolibarr stays out for this company because of the manufacturing depth and GST gap, not because it is a bad product.

Months 5 and 6: go live

• Go live for one plant first, with the old accounting package running in parallel for one full month end.
• Set up daily backups with off site copies and run one restore test before go live.
• Fix an update window, for example one evening every two weeks, tested on a copy first.

What we do not recommend

• Moving accounts and production on the same day.
• Exposing the ERP login page to the internet without TLS, VPN or at least strict access rules.
• Building heavy custom code in the first three months.
• Assuming GST outputs are correct because the software claims support.

When not to adopt each

• ERPNext: if nobody in the company or partner network can manage a Python, MariaDB and Redis stack, and you do not want Frappe Cloud or another managed host.
• Odoo Community: if your must have features are Enterprise only and you do not want a subscription, or if you cannot plan for major version migrations.
• Dolibarr: if you need deep manufacturing planning or ready Indian e-invoicing.

When not to self-host at all

If your company has no IT person, no backup discipline and no budget for a partner, a managed host or a mature Indian SaaS accounting product may be safer than a self-hosted ERP.

A short history

• ERPNext was started by Rushabh Mehta and the team that became Frappe Technologies in Mumbai; the GitHub repository dates from June 2011. (Founder details are general knowledge.)
• Odoo began in Belgium in 2005 as TinyERP, later became OpenERP, and was renamed Odoo in 2014; the current repository dates from May 2014. (Early history is general knowledge.)
• Dolibarr was started in France in the early 2000s; the GitHub repository dates from June 2011. (Start date is general knowledge.)

Others we looked at

From general knowledge only: Apache OFBiz, iDempiere and Tryton are also open source ERPs, but they need more specialist skills and have smaller Indian partner networks.

Decision guide

• Need complete open source ERP with manufacturing and Indian GST: start with ERPNext plus India Compliance.
• Like Odoo and can pay for Enterprise: Odoo, with a partner.
• Small firm, simple flows, plain PHP hosting: Dolibarr.
• No IT capacity at all: managed hosting or SaaS.

Checklist before going live

• Masters cleaned and signed off.
• GST outputs checked by the accountant for at least one full month.
• Roles reviewed; no extra administrators.
• TLS, VPN and firewall in place.
• Daily backups copied off site, one restore tested.
• Update window and test copy process agreed.
• Old system kept read only for audit.

Common mistakes

• Choosing by demo instead of by your own order to invoice flow.
• Customising before learning the standard process.
• Forgetting the filestore or files directory in backups.
• Skipping updates for a year and then facing a painful jump.
• Treating the partner as the owner of your business data.

Hands-on check

We skipped a hands-on drill for this post. A useful check is to install each product on a test VM, load 500 items and 200 customers, and run ten orders through to invoice. Do this as part of your own pilot.

Unlearn and re-learn

• Unlearn: an ERP project is a software purchase. Re-learn: it is a process change project, with software as one part.
• Unlearn: open source means every feature is free. Re-learn: read the licence and the editions page; some ERPs keep key modules in a paid edition.
• Unlearn: go live is the finish line. Re-learn: upgrades, backups and security patches are the real long term work.

Sources

• ERPNext repository and releases: https://github.com/frappe/erpnext
• Frappe framework repository and releases: https://github.com/frappe/frappe
• India Compliance repository and releases: https://github.com/resilient-tech/india-compliance
• Odoo repository: https://github.com/odoo/odoo
• Odoo licence file: https://github.com/odoo/odoo/blob/20.0/LICENSE
• Odoo release.py (20.0): https://github.com/odoo/odoo/blob/20.0/odoo/release.py
• Odoo editions comparison: https://www.odoo.com/page/editions
• Dolibarr repository and releases: https://github.com/Dolibarr/dolibarr
• Dolibarr ChangeLog (24.0): https://github.com/Dolibarr/dolibarr/blob/24.0/ChangeLog
• Dolibarr security advisories: https://github.com/Dolibarr/dolibarr/security/advisories

Related on Revisit.Tech

• Self-hosted CRM in 2026
• Self-hosted helpdesk and ticketing in 2026
• Self-hosted e-signature in 2026
• No-code databases in 2026
• PostgreSQL backups in 2026
• Reverse proxies in 2026
• Keycloak and its alternatives