MonitorX is a lightweight process manager with a built-in cluster mode. Share a port across N workers with zero code changes — plus live logs, auto-restart, and state that survives a daemon restart.
npm i -g @yamanzyan/monitorx
Start the daemon, spin up a fork, scale a cluster, list everything, and tail logs — all from a single CLI. This is a real session, looping.
module.exports = { processes: [ { name: 'server', script: 'node process1/src/server.js', }, { name: 'server2', script: 'node process2/src/server.js', instances: 2, // → cluster of 2 } ] }
Drop a monitorx.config.js in your project root and every process boots with the right name, script, and worker count.
The identifier shown in monitorx ls, logs, and every command.
The shell command to run — e.g. node src/app.js.
Any value > 1 enables cluster mode — N workers share one port, round-robin.
monitorx start
Fork → boot → listen → online. MonitorX assigns the PID, tracks CPU and memory live, and restarts it automatically if it crashes.
Eight verbs, target anything by name or by ID. Run monitorx help <cmd> for details.
start-i -nStart a script, a config file, or a stopped process. Add -i 4 for a cluster.
stopStop a running process or every worker in a cluster — by name or ID.
restartGracefully restart a process or a whole named cluster.
deleteStop and remove processes from the registry entirely.
lsList every process with PID, mode, status, uptime, CPU and memory.
logsStream live output from all processes or a single worker by ID.
monitorx-daemonThe background daemon that manages your apps. Keep it running.
helpShow all commands, or detailed help for a single command.
State persistsRunning processes are saved to ~/.monitorx/ and relaunch automatically when the daemon restarts.
Free and open source. One global install gives you the CLI and the daemon.
npm i -g @yamanzyan/monitorx