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.
Every feature on every planFrom £20 a month. No charge per technician.
Getting startedFrom signup to your first enrolled device in minutes. Clients, agents and sample data.
Monitoring and alertsAlert profiles, health scores, predictive disk warnings, web checks, network discovery and the fleet war room.
Patch managementWindows Update and winget third-party patching on per-client schedules.
Service deskTickets, email-to-ticket threading, SLAs, canned responses, CSAT and time tracking to billing.
Helio AIInvestigations, auto-healing playbooks, the AI service desk and Ask Helio.
ReportingScheduled health reports, the day-one baseline audit and proving progress against it, QBRs, and the internal reports you run for yourself.
Client portalBranded portals on your own domain, client-facing AI intake and QBRs.
IntegrationsMicrosoft 365, Defender for Business, backup detection and remote access.
Public APIScoped API keys and a documented REST API over your clients, devices, tickets and alerts.
Security modelTenant isolation, admin two-factor authentication, passkeys and the encrypted credential vault.
Antivirus and allow listsWhat to allow so the agent and remote access install cleanly: the publisher, folders, services and addresses.
Security advisoriesWhich clients a published security alert touches: what Helios reads, what each status means, and the alert.
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.
