forever

I'd suggest taking a look at the 'forever' module by indexzero for deployment. It has a bunch of node-specific neat features and keeps your process persistent... https://github.com/indexzero/forever

Logo and company name seems very similar to http://www.nodejitsu.com It's also curious NodeFu seem to be using some of Nodejitsu's open-source offerings to make this work. ( https://github.com/nodejitsu/node-http-proxy and https://github.com/indexzero/forever ). Are NodeFu and Nodejitsu the same company?

@intranation Just to toss out a scenario: Lets say under high traffic your application hits an edge case and starts to crash very frequently. Suppose you want to receive an email, SMS, or IM when something like this happens as a devops person. Would you consider that a valid concern of process monitoring? Planned features to Forever include this from the command line, but if you use it from node directly one could implement that feature now: https://github.com/indexzero/forever

That's a strange usage for "proprietary" since it's all free and open source (MIT). Either way, the nodejs child_process module is really just a light weight wrapper to execvp(): http://linux.die.net/man/3/execvp I haven't dug through the source for tools like monit, daemontools, but I'm sure near the metal they're using POSIX or similar system APIs. EDIT: There's really no reason Forever has to be node specific, I actually say that in the article: "Honestly, it's a one line fix here (https://github.com/indexzero/forever/blob/master/lib/forever...), but I'm not sure if users want to put 'node' in-front of every command." I'll file your comment as a +1 for that feature ;)