🖥️

Hermes Remote

Remote shell access to Windows & Linux machines behind NAT or firewalls. No port forwarding, no VPN.

Windows amd64 Windows arm64 Linux amd64 Linux arm64

Windows

Run this in PowerShell as Administrator. Installs as a Windows Service (LocalSystem, auto-start).

# Download & install as Windows Service (amd64 or arm64 auto-detected) . { Invoke-WebRequest "https://hermes-remote.vkand.ru/install-agent.ps1" -OutFile "$env:TEMP\h.ps1"; & "$env:TEMP\h.ps1" }

Linux

Run this in a terminal as root. Installs as a systemd service (auto-start, auto-restart).

# Download & install as systemd service (amd64 or arm64 auto-detected) curl -sSL https://hermes-remote.vkand.ru/install-agent.sh | sudo bash

With custom device ID:

curl -sSL https://hermes-remote.vkand.ru/install-agent.sh | sudo bash -s -- -id my-linux-pc

What happens next

  1. The agent connects to the relay and registers itself — status: pending
  2. You (the admin) approve the device — status changes to online
  3. Run commands, transfer files, manage the machine from Hermes
  4. The agent auto-reconnects on network drops (exponential backoff: 1s → 5 min cap)

Linux service management

sudo systemctl start hermes-remote-agent
sudo systemctl stop hermes-remote-agent
sudo systemctl status hermes-remote-agent
sudo journalctl -u hermes-remote-agent -f

Windows Service management

sc.exe start HermesRemoteAgent
sc.exe stop HermesRemoteAgent
sc.exe query HermesRemoteAgent

Uninstall

Windows

sc.exe stop HermesRemoteAgent sc.exe delete HermesRemoteAgent Remove-Item -Recurse -Force "$env:ProgramFiles\HermesAgent"

Linux

sudo systemctl stop hermes-remote-agent sudo systemctl disable hermes-remote-agent sudo rm /etc/systemd/system/hermes-remote-agent.service sudo systemctl daemon-reload sudo rm -rf /opt/hermes-agent