IDURAR ERP & CRM Review

Overview

IDURAR is an open-source ERP and CRM on the MERN stack - Node.js and Express with MongoDB behind an Ant Design React frontend - and it is smaller than its 8,700-plus GitHub stars suggest. The license file is verbatim AGPL-3.0 with no custom clauses, and the README answers the commercial question directly: free for personal or commercial use. The same README also calls the project fair-code in one line and open source in another, and the backend package.json still says Fair-code License, so the licensing story is untidy even though the license itself is standard AGPL. The feature set needs the most correction before you commit: the README claims exactly four modules - invoice, payment, quote, and customer management - and the code backs that up. Quotes are not a separate entity but an invoice with a quote type, converted through a dedicated endpoint, and recurring invoices are a field on the invoice model rather than a billing engine. There are no expense, lead, product, or inventory models in the open-source code, and the role model ships with a single owner role, so this is a one-admin invoicing core rather than a departmental suite. The paid tiers on the vendor site make the same point by omission: a Professional lifetime license at $5,000 and an Enterprise license at $10,000, which add multi-company, multi-currency, multiple languages, a headless API, and support windows. Every entity gets auto-generated REST routes (create, read, update, delete, search, filter, summary) but there is no Swagger spec and the docs subdomain does not resolve, so plan to read the source. Installation is two npm terminals rather than a container; there is no Dockerfile in the repository. We have not run IDURAR; this assessment is from the repository, the license file, and the vendor site.

How to install

1. From INSTALLATION-INSTRUCTIONS.md, backend first: git clone https://github.com/idurar/idurar-erp-crm.git, cd idurar-erp-crm, cd backend, then npm install, npm run setup and npm run dev. npm run setup runs src/setup/setup.js.
2. Frontend in a second terminal: cd frontend, npm install, npm run dev. The doc says open http://localhost:3000; the Vite dev server proxies /api to the backend on port 8888.
3. Backend configuration lives in /backend/.env. The required value is DATABASE (your MongoDB connection string); the checked-in template also carries JWT_SECRET, NODE_ENV and PUBLIC_SERVER_FILE, with RESEND_API and OPENAI_API_KEY commented out.
4. There is no Dockerfile or docker-compose file in the repository, so containerizing is on you. The install doc includes a legacy OpenSSL workaround (export NODE_OPTIONS=--openssl-legacy-provider) for older Node, or recommends Node.js v20.
5. npm run upgrade and npm run reset exist alongside setup for schema and data resets; read them before running against data you care about.

Requirements

Node.js 20.9 and npm 10.2 are the pinned engines, with MongoDB as the only database (Mongoose 8 on the backend, Express 4, React 18, Ant Design 5, Redux Toolkit and Vite on the frontend). PDF output uses html-pdf with pug templates, which needs the pdf engine available on the host. There is no official container image, so a bare host or your own image is the deployment path.

Best for

Developers on the MERN stack who want a working starting point for a custom invoicing, quoting and payments product: the CRUD API, PDF generation and Ant Design UI are real, and the codebase is small enough to read end to end in an afternoon.

Not for

Sales teams looking for a CRM to configure: there is no lead or pipeline model in the open-source code, one user role, and no documented API reference. Teams needing multi-company, multi-currency or headless API access are pointed at paid licenses rather than code.

Hands-on notes

Assessed from the repository, the license file, the installation doc and the vendor site; we have not run an instance. The most useful evaluation step is reading backend/src/models/appModels: exactly three application models exist (Client, Invoice, Payment), which settles in one glance what the open-source edition is. Quotes are an invoice with a quote type and a /quote/convert/:id endpoint, and the recurring field on the invoice model is a schedule enum, not a billing engine.

The vendor site and the repository disagree, and the difference matters commercially. The site's comparison table caps the Community Edition at one admin user and marks core features as excluded, while the AGPL-3.0 license in the repo places no such limit, and the README invites free commercial use. The site sells a Professional lifetime license at $5,000 and Enterprise at $10,000 covering multi-company, multi-currency, languages, a headless API and support. Read the license, not the marketing table, before deciding what your install may do.

Some feature pages on the vendor site describe capabilities that do not exist in the open-source code at all: purchase orders, supplier management, barcodes, a general ledger and webhooks appear in the localized marketing pages but have no models or routes in the repository. Treat the site's feature copy as aspirational and the repository as the product.

The REST API is real but undocumented: routes are generated per entity for create, read, update, delete, search, list, filter and summary, plus mail endpoints and quote conversion. There is no OpenAPI spec in the repo and docs.idurarapp.com does not resolve, so integration work means reading backend/src/routes. AI features: none. The openai dependency in backend/package.json is unused, and the only other AI reference in the repo is a maintainer CV written for AI agents.

Verdict

A compact AGPL starting point for custom MERN invoicing and payments work, not a deployable CRM suite: read the three model files before you believe any feature list.

Similar Tools