// the take
WGCloud is a Java/SpringBoot server-and-agent monitoring stack for fleets of Linux/Windows/Unix hosts — CPU, memory, disk I/O, SMART, network, processes, Docker, DB, plus extras like topology maps, web SSH and SNMP/K8s checks. Aimed at ops teams who want a self-hosted alternative to Zabbix/Nagios without standing up a full observability stack.
The agent/server split is genuinely lightweight — agents push metrics every 2 minutes and the project claims thousands of concurrent hosts, which is plausible given how little the agent does per cycle. Switching from sigar to OSHI for host metrics was the right call; sigar's native binaries are a constant source of platform-specific breakage, OSHI is pure JNA. Platform coverage is unusually wide for a project this size — RISC-V, s390x, ARM, even 麒麟/统信 (domestic Linux distros), which matters if you're running anything beyond x86 Ubuntu/CentOS.
The README itself tells you not to run the open-source version in production and to buy the closed-source build instead, because it's 'more secure, more stable, more actively updated' — that's the vendor admitting this repo is the degraded version, not just a sales pitch. Features like web SSH and batch command execution across agents are a serious attack surface, and there's nothing in the README about how agent-server auth or command dispatch is secured. The DB layer is built around MySQL (via MyBatis XML mappers) with no mention of HA for the server itself, so the monitoring system has its own single point of failure. Documentation, changelog, and the feature list all live on an external site (wgstart.com) rather than in the repo, so you can't audit what's actually implemented without leaving GitHub.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →