AegisOne Platform Datasheet
What the platform does today, what it does not do, and the technical facts you need to evaluate it — including the gaps.
This datasheet states what AegisOne does today. Capabilities that are not built are listed explicitly rather than omitted, because a datasheet that only lists strengths forces you to discover the gaps during a proof of concept, which wastes your time and ours.
The agent
A compiled Go binary with no runtime dependencies. Builds ship for Windows, Linux, macOS on Apple Silicon (arm64) and macOS on Intel (amd64). Installation is via a scripted install on all platforms, with a signed installer package additionally available for macOS supporting managed uninstall.
Enrolment uses a token issued against a specific client and site, with a configurable lifetime, so an agent lands in the correct place in your structure at first contact.
Connectivity is outbound only. The agent establishes and maintains a connection to the platform; the platform never initiates a connection to the endpoint. No inbound firewall rules are required on managed machines, and no VPN is needed to reach them.
Endpoint and asset management
Hardware inventory including manufacturer, model and serial. Installed software inventory with version tracking. Warranty inventory collection. A per-asset event timeline recording assignment and lifecycle changes, which persists across operating-system rebuilds.
Endpoints and assets are organised by client, site and department. Access, reporting and billing all follow that structure.
Monitoring
Rolling endpoint health history and internet reachability history per endpoint, retained as a series rather than a snapshot. Configurable offline threshold. Online and offline state surfaced across the dashboards.
Network discovery scans a range on demand and records responding devices in a register held separately from agent-managed endpoints, so unmanaged and managed device counts are never conflated.
Patching
On-demand patch scan per endpoint. Install and uninstall dispatched from the console or the API. Per-endpoint patch inventory retained, which is what makes historical patch evidence possible. Patch position feeds compliance reporting.
Remote access
Browser-based interactive remote terminal over an authenticated WebSocket channel, authorised by a short-lived ticket and bound to the operator identity, with sessions written to the agent action log. Remote screen access is available as a beta capability; capture is implemented on Windows, macOS and Linux, while multi-monitor handling and the end-user consent flow are not yet complete.
Service desk and automation
Integrated ticketing with threaded comments, linked to clients, sites and assets. Recurring-issue detection across ticket history, with promotion of a recurring issue into a tracked problem record. Remediation rules mapping detected conditions to corrective actions from a fixed action set, with every triggered action logged.
Security and compliance
Control frameworks with per-client scoring, a compliance findings register, on-demand compliance scan per endpoint, and evidence collection and export. A combined register for vulnerabilities, security findings, incidents and business risks. A credential vault with explicit, audited reveal. TOTP multi-factor authentication, login attempt tracking, invite-based operator onboarding, and an audit log across privileged actions.
Service operations
Contract, licence entitlement and consumable inventory per client. Contract-to-delivery reconciliation with a findings register and run history. Per-client risk scoring, an opportunity register and a client-scoped portal.
Reporting and AI
A report catalogue with saved reports, exporting to PDF, Excel and PowerPoint, plus a dedicated executive PDF format. Executive, MSP business-intelligence and RMM dashboards. AI-assisted root-cause analysis on a ticket, ticket and incident summarisation, quarterly business review generation, security and compliance recommendations, executive and board summaries, and knowledge-base search. All AI output is advisory; the platform does not execute actions on the strength of a generated recommendation. Global search spans endpoints, assets, clients, tickets and documentation.
Not built
The following do not exist in the product and should not be planned against: threshold alerting, escalation and notification; synthetic or outside-in service and certificate checks; a user-authored script library, automation builder or scheduler; software and package deployment; SAML or OpenID Connect single sign-on for operator login; and predictive failure or capacity analytics.
Where a gap matters to you, the REST API is usually the practical bridge — most teams needing paging today poll the API from the alerting platform they already operate, which keeps on-call routing and escalation in one place rather than duplicated per tool.