Browser-Based Access

Helm runs entirely in the browser. Every session launches in a fresh, isolated container powered by KASM. There is no software to install on technician machines — ever.

The Default Way to Use Helm

Browser-based access is not an optional feature. It is the only way technicians interact with Helm. Open a browser, authenticate, and you are in a fully equipped terminal session connected to the endpoint you need to work on.

How It Works

Technician clicks a session link (from the admin portal, a PSA ticket, or a direct URL).
KASM spins up a fresh container with the Helm TUI loaded.
The session connects to the target endpoint via helm-agent.
When the technician disconnects, the container is destroyed. Nothing persists.

Zero Persistence, Compliance Built In

Every session starts clean and ends clean. There are no cached credentials, no leftover files, no session data on the technician’s device. This is compliance by design — not a policy you have to enforce.

Works From Any Device

Desktop, laptop, tablet, or phone — if it has a modern browser, it runs Helm. This means technicians can respond to critical alerts from wherever they are, without needing a managed workstation.

No Onboarding, No Offboarding

Because there is no software on technician machines:

New hires open a browser and start working on day one
Departing staff lose access the moment their account is disabled
No licenses to reclaim, no agents to uninstall, no cleanup

Session Recording (Enterprise)

For organizations that require full audit trails, Enterprise plans support session recording. Every keystroke and screen interaction is captured for compliance review and playback.