Tools: I Got Tired of PM2. So I Built a Process Manager in Go — Single Binary, Any Language - 2025 Update
The Problem
What APM Is
What Makes It Different
Who It's For
What It Looks Like
Where to Get It If you've ever set up a server running a mix of Node.js, Python, and Go services, you know the pain. PM2 is great — until you realise it requires Node.js on every machine just to manage processes that have nothing to do with Node.
That was my breaking point. I had a Linux server running a Python worker, and a couple of Node.js services. PM2 worked fine for the Node stuff, but managing everything through it meant dragging in a Node runtime as a hard dependency just to supervise processes that didn't need it at all.I looked at alternatives. Supervisord is Python-dependent. systemd works but it's not exactly developer-friendly for per-project process management. Everything else was either too basic or too complex.So I built APM. APM is a production-grade process manager for Linux, written in Go and distributed as a 2.5MB static binary. No runtime. No dependencies. No config files required to get started.Drop it on any Linux box and you're running: APM is built for developers and DevOps teams who: The web GUI gives you a live view of all running processes, with per-process CPU and memory graphs, log streaming, and controls to start, stop, and restart. The CLI monitor mirrors this in your terminal for SSH sessions. Website + docs: processmanager.devManual: processmanager.dev/manual.html APM is at v1.3.0 and production-ready. I'm actively developing it and genuinely interested in feedback — especially from anyone running it on unusual distros or mixed-language setups.
What's your current setup for managing Linux processes? I'd love to know what pain points you're hitting that APM might help with. Templates let you quickly answer FAQs or store snippets for re-use. Hide child comments as well For further actions, you may consider blocking this person and/or reporting abuse
