hirogate 0.1.0

Hiro — WebSocket relay gateway server

hirogate

Hiro Gateway — WebSocket relay server.

Accepts connections from Hiro desktop servers and online apps, performs challenge/response authentication, and relays messages between authenticated devices identified by device_id.

Dev setup

hirogate is part of the hiroserver uv workspace. No separate tool install is needed — it runs directly from the workspace venv via uv run.

After cloning or pulling updated code, run from the repo root:

./dev-sync.sh

Or manually:

cd hiroserver
uv sync

Quick Start

# Create a named gateway instance (mandatory values at creation)
uv run hirogate instance create home --port 8765 --desktop-pubkey "<base64-public-key>" --set-default

# Start the instance later using only its name/default
uv run hirogate start --instance home
# or simply:
uv run hirogate

Instance model

Each gateway runs as a named instance with persistent config:

• name (instance identity)
• host and port (bind address)
• desktop_public_key trust root
• log_dir (optional override)

Instance commands:

hirogate instance list
hirogate instance show home
hirogate instance set-default home
hirogate instance remove home --purge

How it works

1. Every new socket receives an auth challenge nonce.
2. A desktop client authenticates using its master key (auth_mode=desktop) against the desktop trust root configured at startup (--desktop-pubkey).
3. A device client authenticates with desktop attestation + nonce signature (auth_mode=device).
4. Once authenticated, messages are relayed by device_id.

Message Format

{
  "target_device_id": "uuid-of-the-target-device",
  "payload": { ... }
}

If target_device_id is omitted, the message is broadcast to all connected devices.