Helios documentation

Everything the platform does, written down.

Plain-language documentation for every part of Helios: how it works, how to set it up, and how it behaves once it is running your estate. No feature described here is on a higher tier. Everything is on every plan.

Start hereGetting startedFrom signup to your first enrolled device in minutes. Clients, agents and sample data. OperateMonitoring and alertsAlert profiles, health scores, predictive disk warnings, web checks, network discovery and the fleet war room. OperatePatch managementWindows Update and winget third-party patching on per-client schedules. OperateService deskTickets, email-to-ticket threading, SLAs, canned responses, CSAT and time tracking to billing. AutomateHelio AIInvestigations, auto-healing playbooks, the AI service desk and Ask Helio. ClientsReportingScheduled health reports, the day-one baseline audit and proving progress against it, QBRs, and the internal reports you run for yourself. ClientsClient portalBranded portals on your own domain, client-facing AI intake and QBRs. ConnectIntegrationsMicrosoft 365, Defender for Business, backup detection and remote access. BuildPublic APIScoped API keys and a documented REST API over your clients, devices, tickets and alerts. TrustSecurity modelTenant isolation, mandatory admin 2FA, passkeys and the encrypted credential vault.

How these docs are written

Helios is developed against a real MSP's daily workload, and this documentation is written from that same seat. Where a feature has limits, the limit is stated. Where behaviour is deliberate (for example, which alerts are allowed to create tickets), the reasoning is included, because knowing why is what lets you change the defaults with confidence.

Something missing or unclear? Email support@heliosmsp.io and it will be fixed in the docs, not just answered in the reply.