The short review: NetLock RMM is good software for what it sets out to be. It is an independently developed open source project from Germany, released under AGPL-3.0 with an active v2.6.x release cadence and a growing GitHub community. It is genuinely open source, the Community Edition is free up to 25 devices, and self-hosting is first-class. The platform does a lot right: multi-tenancy with granular role-based permissions, remote shell and screen control, antivirus and firewall monitoring, security baseline enforcement, whitelabel, SSO and MFA, and a clean Docker or Kubernetes deployment. For EU teams prioritizing data sovereignty, the German origin and air-gapped support are real differentiators. None of that is in dispute here.
The difference is not feature-count; it is what the product is. NetLock, like every traditional RMM, is a dashboard: it surfaces alerts, and a human operates the console to triage and resolve them. Breeze is built the other way around. The workers are the product. They read an alert, investigate across the affected devices, apply the fix, and write up what they found and did, and a 4-tier risk engine decides what runs autonomously versus what waits for a technician to approve. You set those tiers. Low-risk routine work clears itself; anything sensitive stops for review.
That changes who does the work. With NetLock you are still the operator, scaling by hiring more technicians. With Breeze the workers scale with you. Breeze is also the first RMM to ship an MCP server, so you can drive the platform from Claude Desktop, Cursor, or ChatGPT, querying fleet state and triggering actions from the tools your team already uses. The Breeze Community core is AGPL-3.0, free to self-host with unlimited devices and technicians. Commercial extensions under ee/ (Wisp and Breeze AI for Office) have separate terms. Managed cloud is in public beta. Both projects share the open source values; they differ on whether you operate the fleet or something operates it for you.