Frequently asked questions

No. You run it in your own Docker environment and use it from a browser. You control network exposure, updates and backups.

The Free plan allows one active user and up to five enabled hosts, without a time limit. It includes SSH, SFTP, RDP, VNC, Docker Manager and optional AI with your own compatible API.

No. Console Hub connects through existing SSH, SFTP, RDP or VNC services. Those services must be enabled and reachable from the Console Hub server.

Console Hub is designed for desktop browsers with a keyboard and mouse. Use a desktop for terminal, file, and remote desktop work.

No. Installation and management are separate. Add a saved Linux host with an SSH profile and the required permissions, then open its Docker workspace.

No. Docker management uses the saved Linux host’s SSH connection. The remote account must have the required Docker access.

No. The SSH terminal operates on the host. A container exec terminal runs inside the selected container and depends on the executables and permissions available in that image.

Browser access to Console Hub and backend access to a remote host are different network paths. Check the target service, route, firewall, credentials and host permissions.

No. Reusable connection credentials are encrypted in your installation and used by the backend to establish remote connections.

No. Audit logs record actions and results, not terminal input, output, or session recordings.

No. You are responsible for backups and recovery. Protect the database and Vault volumes together and test recovery using a compatible image.

Managed private-LAN HTTP is supported. Use HTTPS when your network exposure or policy requires it. Browser passkeys require a secure context such as HTTPS or localhost.

No AI provider is included by default. An administrator configures a compatible endpoint and key. Submitted text is processed by that provider; review its policies before sending sensitive content.