APM — Process Manager for Linux

APM v2 introduces built-in inter-worker IPC, allowing processes managed by APM to communicate with each other directly through the APM daemon. This means workers written in different languages — Node.js, Python, Go, Rust, PHP, Bash, or anything else running on Linux — can exchange messages without needing Redis, RabbitMQ, extra sockets, temporary files, custom ports, or another service sitting in the middle. The goal is simple: if APM already supervises your processes, proxies them, restarts them, watches them, and shows their live status, it should also be able to help them talk to each other. With IPC, a Node.js web worker can hand a task to a Python script, a Go service can notify a Rust worker, or multiple app instances can coordinate without every component needing its own communication layer. APM stays true to its original idea: one small static Linux binary, no external dependencies, and no requirement to change your stack. You can keep using the languages and tools you already like — APM just gives them a common communication path. This update makes APM more than a process manager. It becomes a lightweight runtime layer for mixed-language Linux applications, especially useful for backend services, APIs, automation, monitoring tools, and small self-hosted systems where adding a full message broker feels too heavy. Still simple. Still language-agnostic. Still one binary. Now with workers that can chat.