Rutba ERP

Most ERPs are one enormous application with features switched off. Rutba ERP inverts that: each functional domain is a separate Next.js application in an npm workspaces monorepo, and the applications cooperate through a shared Strapi 5 API rather than a shared codebase. A retailer can deploy point of sale and stock alone, add order management when they start shipping, and bring in manufacturing or payroll later — without carrying the weight of modules they never open, and without a migration each time.

The Seventeen Applications

The seventeen applications span commerce and sales (point of sale, storefront, order management, a customer My Orders portal), inventory and supply, manufacturing with work orders, bills of material and material lots, HR and payroll, accounting, CRM, a rider delivery app, CMS and social. Every module is a deployable application in its own right, sharing state through the central API.

Shared Infrastructure & Stack

Consistency across them comes from shared infrastructure rather than convention:

• A generated API client per application, so a schema change cannot silently drift.
• A shared UI component package.
• An OAuth-style authentication portal issuing per-application JWTs.
• A descriptor-driven permission layer, so a role defined once is enforced everywhere at the API rather than per front end.

The stack is Next.js 16, React 19, Strapi 5 and MySQL or MariaDB, deployable locally, via Docker, or on shared hosting.

Production & Open Source

The commerce modules are proved in production: the storefront, checkout, order pipeline and rider delivery applications run Rutba.pk, a live retail store operated by the same company, so edge cases surface there before they reach anyone else. Rutba ERP is published under the MIT licence at github.com/eharain/Rutba-ERP, and Tech Style Ltd offers implementation, customisation and support around it