A real SSH server, your own DevPlace login

This workspace is also reachable as a genuine SSH host, not just a browser tab. Point any real SSH client at it, sign in with your DevPlace username and password, and you land in the exact same persistent tmux session your browser would show you. Nothing about the container changes depending on how you reach it.

ssh -p 222 your-devplace-username@this-host

Everything a real SSH connection does

• Shell. Plain ssh with no command attaches you to your own main tmux session, live, shared with the browser.
• Remote commands. ssh host 'some command' runs it inside your container and streams the real output back, stdout and stderr kept separate, exactly like any other SSH host.
• SFTP. Any SFTP client (sftp, scp -s, a GUI file manager's SFTP mode) talks to the real OpenSSH sftp-server running inside your own container: full permissions, symlinks, and resumable transfers, not a partial reimplementation.
• Local port forwarding. ssh -L 8080:<your-container-name>:80 you@host reaches a server you started inside your own container from your laptop. Your container's own name for this purpose is printed the moment your shell session starts.

Forwarding only ever reaches your own container, never anyone else's, and a remote listening port (ssh -R) is not offered. Sign-in attempts are rate-limited, both per address and per username, so this gateway can never become a way to hammer DevPlace's own login system.

Reaches you however your network reaches the internet

Port 222 answers on IPv4 and IPv6 alike, dual-stack, so a client on an IPv6-only or IPv6-preferring network connects exactly as fast as one on plain IPv4; there is no fallback delay to wait out either way. The server also offers two host key algorithms, Ed25519 and RSA, specifically because a narrowly-built client (ChromeOS's own Secure Shell app, tested directly) could not complete key exchange against an Ed25519-only host. Whichever your client already trusts or prefers, it will find a match.

Real, measured throughput on this host: SFTP transfers run at roughly 170 MB/s in both directions, and a plain ssh host 'cmd' round trip costs about 48 ms. See the architecture page for the exact numbers and how they were measured.