Skip to main content

Install Host Agent

Run one of the following commands in your terminal:

For Linux/macOS:

Loading...

For Windows (PowerShell):

Loading...

Adjust options as needed. Add the output to the hosts section of your config on the Coordinator Host:

/this/is/a/demo.toml

Hosts Table

Host Status Leases Actions

Install Client

Run one of the following commands in your terminal:

For Linux/macOS:

Loading...

For Windows (PowerShell):

Loading...

Optionally specify a custom base client ID as the second argument (otherwise random). The full client ID will include your hostname. Tip: Use separate clients for different use cases.

Then, add the output to the clients section of your config on the Coordinator Host:

/this/is/a/demo.toml

Clients Table

Client ID Leases Last Used Actions

🖥️ Platform Support

Component Linux macOS Windows
Web GUI ✅ (any modern browser) ✅ (any modern browser) ✅ (any modern browser)
Coordinator ✅ Binary
✅ Docker
✅ Binary
❌ Docker
✅ Linux VM
(bridged networking)
❌ Binary
❌ Docker
❌ WSL
✅ Linux VM
(bridged networking)
Host Agent ✅ Binary ✅ Binary ✅ Self-extracting
(manual service setup required)
Client
(Script)
✅ Shell
✅ Docker
✅ Shell
✅ Docker
✅ PowerShell
✅ Docker
✅ WSL (Shell)
Direct Control
(Script)
✅ Shell ✅ Shell ✅ PowerShell

Architecture Documentation

ShutHost's architecture is built around three core components: the Coordinator, Host Agents, and optional Clients for programmatic control.

Core Components & Interactions

Host-Agent-Coordinator Interaction Diagram

Lease System & Multi-Client Access

Client-Coordinator-Host Lease System Diagram

When leases matter: When you have clients defined in your configuration or multiple entities (WebUI + scripts) accessing hosts, the lease system prevents conflicts and ensures hosts stay online while in use.

Deployment Options

Deployment Options Diagram

Direct Control vs. Coordinator

Direct Control vs Coordinator Comparison Diagram