Monitor Windows with an agent that reports to one console.

Server 2016 and later, Windows 10 and 11. Runs as a service, installs with one PowerShell line, watches services, the event log and patch state. BE AI investigates when something fails; a person approves the fix.

install

One line, from the company's install page.

Run in elevated PowerShell. It fetches the signed binary, verifies the checksum, installs the service and connects. Run it again any time; it never overwrites the machine's identity.

irm https://hub.[yourdomain]/install/inst_…/windows.ps1 | iex

Outbound 443 to the hub only. No inbound rule, no VPN, no SNMP community.

what the agent watches on WindowsServicesAuto-start services that are not running, restart proposed by BE AI, approved by you.Event logError and warning entries from the System log, read on demand with a cap.Patch healthPending reboot, failed updates, last successful update, uptime.Mapped drives and printersPer-user checks for the drive letter and the printer that the front desk cannot work without.Disk, memory, CPUEvery fixed volume; ISOs and recovery partitions are ignored.UsersWho is logged in, from the session API, so a check can wait for a user.Remote controlWatch or take control from the console in one click, over the agent's outbound connection. Serves Remote Desktop sessions and unattended servers, sign-in screen included. questions

Before you put it on Windows.

Does it run as SYSTEM?

As a Windows service, yes. Commands you approve run in that context; per-user checks read the user's session and registry hive.

How is it removed?

One command uninstalls the service and deletes the folder. The machine's history stays on the hub until you forget it.

Does remote control need an open port or a VPN?

No. The session travels over the agent's existing outbound connection. Nothing is reachable from the network, no port is opened, and Windows Firewall does not prompt.

Ten machines, 14 days, no card. Uninstall the agent and you are out.

Start a free trial See pricing