Terminals

Open a container or database shell

Instance operators can open shells from service and database pages, the CLI or client.terminals in the SDK. Local and node-placed Docker services get a real TTY with resize. For Compose, open a managed container. Panel-host database client mode supports psql, mysql/mariadb and Redis-compatible clients; node databases support a shell only, where you can run the client yourself.

ninedeploy terminal service 12
ninedeploy terminal db 3
ninedeploy terminals list
ninedeploy terminals kill <session-id>

Host terminals and remote nodes

Node terminals require agent v0.15.0 or newer and sealed transport. Update the agent from the Servers bootstrap flow. Terminal frames use an encrypted, authenticated channel; older agents get an explicit upgrade refusal. Workspace admins and fine-grained API tokens cannot open terminals.

History and privacy

Short-lived single-use tickets, idle limits, maximum duration and user/panel caps govern sessions. History records the user, target, client IP, duration, byte counts and end reason, with start/end audits. Typed commands and terminal output are never stored. Operators can terminate active sessions.