Problem
Nexus ERP is positioned around bringing finance, manufacturing operations, supply chain, quality, inventory and engineering into one product for industrial teams.
Scope
The inspected GitHub repository contains a multi-page product website and feature/roadmap content. It catalogs 17 ERP modules and describes an AI document workflow, while its roadmap identifies module screens, forms, granular permissions and real-time dashboards as work in progress or planned.
Solution
CloudMonkey built the Nexus ERP project and its public product website, organizing the product around a connected industrial ERP. CloudMonkey presents the project as open source. The reviewed repository labels a core finance and document workflow as shipped, but contains no ERP application backend, database schema or operational workflow code with which to verify those behaviours. The supplied repository has no LICENSE file, so the project's open-source licensing terms are not established by the reviewed source.
Stack
- React 19 and TypeScript
- TanStack Start and TanStack Router
- Tailwind CSS and Vite
Platform features built
- Verified in the inspected repository: responsive Home, About, Contact, Modules, Platform and Pricing pages, plus an XML sitemap.
- The product module catalogue covers Accounts Receivable, Accounts Payable, General Ledger, bank integrations, work orders, OEE and machine uptime, ISO compliance, NCR management, purchasing, three-way matching, warehousing, stock control, Sales and CRM, B2B self-service portals, engineering and BOM, carbon footprint, and consumption tracking.
- The product website describes multi-company data isolation; AI extraction from PDFs, images and RFQs into vendor bills or quotations; finance dashboard totals; sequenced invoices; bills shown alongside source documents; payment marking with bank-balance updates; and per-company user, currency and VAT settings. These ERP behaviours are product claims in the website content and are not verifiable from this marketing-site repository.
- The published roadmap distinguishes planned or in-progress Excel imports, statement generation, shop-floor and supply-chain screens, quality/engineering/inventory forms, department permissions, validation and real-time dashboards from the listed shipped core.
Implementation
- Built the public product website using the React, TypeScript and TanStack Start stack present in the repository.
- Structured the product narrative into six routes with reusable module, AI-document-pipeline, security, pricing and roadmap content.
- Reviewed the complete tracked repository and commit history: the repository contains the marketing site, not the ERP application's backend or workflow implementation.
- The source review is published with this case study. The supplied GitHub repository was not publicly viewable and nexuserp.xyz did not complete a TLS connection during review; the page therefore makes no claim that visitors can currently access the source or live product.
No verified quantitative result is published for this case study.