Current release

This page describes the state of the platform as documented on 19 July 2026. The capability registry behind this site records the production evidence for every claim made here; anything not present in that registry as available is not in the product.

Shipped and generally available: the cross-platform endpoint agent for Windows, Linux, macOS arm64 and macOS amd64, with token-based enrolment, scripted install and a signed macOS installer package. Asset intelligence covering hardware, software and warranty inventory with a per-asset timeline. Client, site and department structure. Endpoint health and internet-reachability history. Network discovery with a separate discovered-device register. Remote terminal over an authorised WebSocket session. An integrated service desk with recurring-issue detection and promotion to problem records. Patch scan, install and uninstall with retained per-endpoint patch inventory. Remediation rules over a fixed action set. Compliance frameworks, scoring, findings and evidence export. A vulnerability and risk register. The credential vault. TOTP multi-factor authentication with audit logging and invite-based operator onboarding. Contract, licence and consumable management with revenue-leakage reconciliation. Customer risk and success scoring. A client portal. AI-assisted root-cause analysis, summarisation, QBR generation and executive narrative. Executive reporting with PDF, Excel and PowerPoint export. Global search across entities.

In beta: remote screen access. Capture is implemented on Windows, macOS and Linux and available for evaluation. Multi-monitor handling and the end-user consent flow are not complete, which is why it carries a beta label rather than a shipped one.

Not built, and not scheduled here: threshold alerting, escalation and notification; synthetic and outside-in service checks; the script library and automation builder; software and package deployment; SAML and OIDC single sign-on; and predictive failure or capacity analytics. These appear on the public roadmap with their real status and should not be planned against as though they exist.

When a capability moves between statuses, the change is made in the registry that drives this site, and the evidence line recording why is updated at the same time. That is the mechanism that keeps documentation and marketing copy from drifting away from the product, and it is the reason this page can be specific about what is missing.