Your database container is probably not at 98 percent memory, whatever docker stats claims, because most of that figure is reclaimable page cache; ContainerFlow subtracts the full cache and shows the memory your containers actually hold. Point it at a Docker socket and it draws the whole estate as a living map: every Compose project discovered automatically, services grouped and colour coded, and the connections between them inferred, app to database, proxy to app, worker to broker. CPU and memory refresh every three seconds, the graph flashes when a container starts, stops, or restarts, and seven days of metric history wait in a local store when you need to know what happened overnight. Click any node and a detail panel opens with live logs you can filter by stream, an inline terminal that runs commands inside the container, and buttons to start, stop, restart, rebuild, recreate, or remove it. The same panel teaches as it works, flagging containers that run with no memory limit, no CPU limit, or no restart policy, while Discord webhooks fire when a container you care about crosses a threshold you set. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. AGPL-3.0 licensed.