Windows fleet monitoring that sees every machine, everywhere, before it becomes a problem.

For every monitored machine, WINMON collects CPU utilisation, memory used, disk used (worst drive), disk health, network adapter state, uptime and last boot time, plus a count and detail of recent Windows event-log errors. Nothing is installed on the machines themselves; everything is gathered remotely over WinRM by the on-site collector.

Each machine resolves to one clear status that drives its colour on the dashboard, so a team can tell at a glance which machines need attention and which are healthy.

Thresholds resolve machine-specific, then site/branch, then company-wide, then built-in defaults, most specific wins. An operator can set one global standard, tighten it for a particular site, and override it for a single sensitive machine, all without touching everything else.

When a machine crosses a threshold or recovers, WINMON adds an entry to the in-app notification feed and sends a WhatsApp message to configured recipients. Repeated alerts are throttled, a mass event is merged into one summary message, and a global send queue prevents the sender number from ever being blocked.

Each company can define monitoring hours. Outside those hours the machine is still monitored and the dashboard still updates, but outbound alerts are suppressed, so nobody is woken at 2 a.m. for a store that's closed.

Each collector heartbeats to the cloud. If a collector stops reporting, the platform detects it, surfaces the collector as offline on the dashboard, and alerts, so a site going dark is never mistaken for a quiet, healthy site.

Each customer is a fully isolated Company with its own machines, users, thresholds, recipients, sites, and collectors. Platform administrators can provision a new company in one step, pause or suspend a company as an enforced lock-out, or permanently delete a tenant.

Authorised users can add a machine, edit it in place, pause or resume monitoring, delete it, and group machines by site or branch. Changes take effect on the collector's next cycle, with no site visit required.

Each site's collector is issued a unique high-entropy token that can be rotated or revoked independently. Collector updates are cryptographically signed and verified on-device before being applied, with fail-closed verification and canary-first roll-outs.