SECURITY / PROJECT ACCESS
SSH access requires an isolated gateway.
No SSH host, gateway, or container is configured. BRIQONA does not expose VPS root access or report a successful connection.
Infrastructure required
SSH is unavailable until the workload environment provides per-project isolation, non-root accounts, public-key verification, short-lived access, session auditing, rate limits, and revocation.
Project-only access
Any future session must reach only the user's authorized application environment; it must not expose host credentials, the Docker socket, or other customer files.
Operator verification required
A secured gateway and worker must be deployed and independently tested before connection details or session controls are presented.
Security boundary
- • No unrestricted host shell or root credentials.
- • No shared customer SSH keys or cross-project access.
- • No public SSH port to customer containers without a reviewed isolation architecture.
- • Session access, expiry, and termination must be recorded and revocable.
Deployment readiness: live builds, custom routing and certificates require a separately operated, security-hardened workload server and verified GitHub configuration. These services are not reported as active until they pass live checks.