I think this may take some unpacking.
A full-fledged ERP is a massive beast and not something that I personally would want to see come across my desk as a Node-RED application (in my day-job as head of architecture for a major public sector health organisation). However, as @kuema mentions, seeing Node-RED as an element in an ERP would be something I'd be delighted to see.
Also, an ERP is more than just a "web application". It will involve significant back-end infrastructure, backup/recovery, load-balancing, identity management, security, etc. Not all of these are easy to do in Node-RED and are very likely to be cheaper and more robust using specialist tooling.
Of course, all of this comes back to your actual use-cases. You will need to take into account commercials and finance, supportability and so-on.
Node-RED is a fantastic tool, great for prototyping, especially for certain types of processing that lend themselves to the message passing flow style of Node-RED. Also for quickly building data-driven user interfaces. It is amazingly stable for general use. All good stuff.
However, it is not without issues. If you ever come across a memory leak even in a simple flow - good luck! In a complex flow, it is likely to be impossible to debug without a serious investment of time and energy from Node.js experts. You may also find yourself relying on contributed nodes from amateurs like myself - talented though we are (
), we possibly don't develop these things professionally and can't provide loads of support hours. Do you want your (or your customers) ERP reliant on us?
Then there is security. While Node-RED has some basic security built in and I believe some organisations have tested it successfully, it certainly isn't hardened. User management is also limited and really requires external additions.
All things to think about.
