# Multiple node red instances

**URL:** <https://discourse.nodered.org/t/multiple-node-red-instances/18002>\
**Category:** General\
**Created:** [15 November 2019 13:50 UTC](https://discourse.nodered.org/t/multiple-node-red-instances/18002 "2019-11-15T13:50:36Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![kuema](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/kuema/32/6542_2.png) [@kuema](https://discourse.nodered.org/u/kuema)\
**Post date:** [15 November 2019 14:45 UTC](https://discourse.nodered.org/t/multiple-node-red-instances/18002/2 "2019-11-15T14:45:18Z")

</div>

It depends on your use case.

In my setups I am using one Node-RED installation and launch different workspaces with `-u`, each with their own dependencies, settings.js, flows.json and so on.

Structured like this:

```auto
.
├── apps
│ ├── node-red -> node-red_1.0
│ ├── node-red_0.19
│ ├── node-red_0.20
│ └── node-red_1.0
└── workspaces
    ├── node-red-controller
    │ ├── flows_cred.json
    │ ├── flows.json
    │ ├── lib
    │ ├── node_modules
    │ ├── package.json
    │ ├── package-lock.json
    │ └── settings.js
    ├── node-red-dashboard
    │ ├── flows_cred.json
    │ ├── flows.json
    │ ├── lib
    │ ├── node_modules
    │ ├── package.json
    │ ├── package-lock.json
    │ ├── settings.js
    │ └── static
    ├── node-red-telegram
    │ ├── flows_cred.json
    │ ├── flows.json
    │ ├── lib
    │ ├── node_modules
    │ ├── package.json
    │ ├── package-lock.json
    │ └── settings.js
    └── node-red-test
        ├── flows_cred.json
        ├── flows.json
        ├── lib
        ├── package.json
        └── settings.js

```

Everything is managed with a PM2 ecosystem file.

After all it's not very different from your approach.

---

_[View the full topic](https://discourse.nodered.org/t/multiple-node-red-instances/18002)._