# Running Node-Red Server as a Service

**URL:** <https://discourse.nodered.org/t/running-node-red-server-as-a-service/20666>\
**Category:** General\
**Created:** [21 January 2020 00:25 UTC](https://discourse.nodered.org/t/running-node-red-server-as-a-service/20666 "2020-01-21T00:25:13Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [21 January 2020 10:04 UTC](https://discourse.nodered.org/t/running-node-red-server-as-a-service/20666/3 "2020-01-21T10:04:39Z")

</div>

some pointers...

> [@Node red multiple instances](https://discourse.nodered.org/t/node-red-multiple-instances/9787/5):
>
> Instead of changing settings file, I use the -p command line option to specify the port. I also use nssm on windows for multiple instances. So each service launches for example... node-red -p 1881 -u c:/nr1881 node-red -p 1882 -u c:/nr1882 And so on. BTW, @knolleary that document you linked to doesn't show the -p option or -t option.

> [@Run on windows as service](https://discourse.nodered.org/t/run-on-windows-as-service/13569):
>
> Hi, I have created a node-red application that works together with an Opto 22 controller to monitor alarms. I installed the app on the computer used on the company where it is going to be working. But sometimes operators close the command prompt where the node-red is running and the app stops. Is there a way to run node red as a windows service?. In that way as the computer is turned on, node red would be instantiated.

For the record - I use NSSM on windows server

---

_[View the full topic](https://discourse.nodered.org/t/running-node-red-server-as-a-service/20666)._