A browser-based control plane for every deployment, secured behind SSH.

Every relay server runs a web admin panel that lets you manage services, users, and terminals without leaving the browser. It is never publicly exposed — access is always gated through an SSH tunnel.

SSH-gated

the panel is only reachable through an SSH tunnel to the relay server

Automatic

started by PM2 during relay initialization — no extra configuration required

tunnel

bash

ssh -N -L 3772:localhost:80 -i .turboci/.ssh/id_rsa root@<relay-server-ip>

Access

How to reach the admin panel

After a successful turboci up, the CLI prints the relay server IP and the exact tunnel command to use.

Establish the SSH tunnel

tunnel

bash

ssh -N -L 3772:localhost:80 -i .turboci/.ssh/id_rsa root@<relay-server-ip>

The -N flag keeps the connection open without executing a remote command. Leave this running in a separate terminal tab.

Open the panel

browser

bash

http://localhost:3772

Navigate to this URL in any browser while the SSH tunnel is active.

Capabilities

What the admin panel provides

Service management

View the status of every service and server in the deployment, trigger restarts, and inspect logs directly from the browser.

User management

Create and manage external users who can access the admin panel. External users authenticate through the panel rather than SSH.

Terminal access

Open a browser-based terminal into any server in the deployment, powered by ttyd and proxied through NGINX.

Technical details

How the panel is wired up on the relay server

The admin panel process is managed by PM2 and starts automatically during relay initialization.

Web UI

Port 3772

Served at / via NGINX on the relay server.

WebSocket

Port 3773

Real-time communication at /ws for live status and logs.

Terminal (ttyd)

Dynamic ports

Browser terminals proxied at /ttyd/<port> for each server.

The panel database is encrypted at rest using a randomly generated 32-character password and 16-character salt, both unique per deployment. No credentials are shared across deployments.

Next step

Self-healing that runs alongside the panel

The relay server also runs an auto-healing daemon that continuously monitors every service and recovers failing servers automatically.

Continue to auto-healing