Seeded demo · auth off · no application database · GitLab SoT / GitHub twin · not an ATO

Browser console

One-click web SSH terminal (Xterm.js ⇄ Socket.io ⇄ ssh2) with a Harvester KubeVirt VNC fallback.

Console statusDemo — no gateway attached

Demo mode — no console gateway is attached from this front door.

The 1-click SSH bridge only goes live when the dashboard runs in-enclave with CONSOLE_GATEWAY_URL set. Here it renders a local emulator so you can see the terminal experience — it is not connected to any host and is not an ATO.

Web SSH consoleDEMO

This is a self-contained terminal emulator. Start the demo session to interact with a simulated prompt — useful for confirming the console layout and keyboard handling without a live backend.

Local demo — the terminal below is an in-browser emulator, not a real SSH session.

How the bridge works

The gateway service (DevSecOps/console-gateway) runs a Node.js ssh2 client behind a Socket.io WebSocket and streams the interactive shell to this Xterm.js terminal. When the direct SSH socket is unavailable or misconfigured, it links to the Harvester / KubeVirt native web console (VNC) instead. The dashboard goes live only when it runs in-enclave with CONSOLE_GATEWAY_URL set; from the connected front door it stays in demo mode by design.

Deployment guardrails (SC-7)

  1. Deploy the gateway inside the authorized boundary beside Harvester. It must never be bridged from the connected GitLab / Vercel front door to harvester.alethelabs.dev.
  2. Arm SSH only via the gateway's CONSOLE_ALLOWED_HOSTS allow list — it fails closed with no wildcards.
  3. Finish the Phase 1 provision gate and have the CCB record the console gateway as a component before an AO accepts inbound admin paths.