What AegisOne is (and what it is not)

AegisOne is an endpoint operations platform. A small compiled agent runs on each machine you manage, maintains an outbound connection to the platform, and reports inventory, health and patch position. From the console you can inspect those endpoints, patch them, open a shell on them, apply remediation rules, and produce the reporting and compliance evidence that the work generates.

Around that technical core sits a service-operations layer: clients, sites, departments, contracts, licences and reconciliation. This exists because the people running endpoint estates are usually accountable for the commercial position too — what was promised, what is being delivered, and the difference between the two.

Five terms carry most of the meaning in the console, and they are worth learning before anything else.

An endpoint is a machine with the agent installed. An asset is the inventory record for a thing you manage, which may be an endpoint but may also be a monitor, a phone, or a switch with no agent on it. A client is the organisation the estate belongs to; internal IT teams typically model themselves as a single client. A site is a physical or logical location under a client. A department cuts across sites and is used for ownership and chargeback.

Discovered devices are a sixth category and are held deliberately apart. Network discovery finds things on a segment that have no agent — printers, appliances, unmanaged switches. These land in a separate register precisely so that "devices we manage" and "devices we can see" never get conflated in a count you might put in front of a customer.

It is equally worth being clear about what is not in the product today. There is no threshold alerting or escalation engine: AegisOne records health history continuously, but nothing evaluates that history against rules and pages someone. There are no synthetic or outside-in service checks. There is no user-authored script library and no scheduled automation builder — remediation rules cover a fixed action set, not arbitrary code. There is no software or package deployment. And operator login is email, password and TOTP; there is no SAML or OIDC federation.

If any of those are load-bearing for your operation, plan around them rather than around a roadmap date.