pm2 > forever

pm2 > forever

pm2 > forever

Basically it took me less than five minutes to configure pm2 while foreverjs took ... forever ( > 30 mins )

The reason behind it: pm2 allows you to name your process the moment you are starting it. So, you can handle it by just
calling it and does not create several instances without reason. 

Proof:
forever start --uid "server" server.js   -----   pm2 start server.js -n server
## This creates a new instance                   ##This recognizes the old instance and does not create another

pids can be messy to handle in a non-local enviroment. With pm2 you can interact with your named process without
caring about the pid.

I found forever unreliable for my apps, limited and it has issues on system reboots.

My pick is pm2