VNC
In-app noVNC framebuffer with optional SSH-tunnel routing. Headless Linux, IoT panels, lab gear — pixel-for-pixel without the second tool. New connection kind alongside SSH / RDP / Telnet on every tier.
VNC is a first-class connection kind on every tier — the new vnc type sits alongside ssh, rdp, telnet, serial, ssm, browser, and local in the saved-connection list and uses the same auth model, the same audit trail, and the same tab strip.
Why it’s here
The browsers, RDP clients, and Termius-class tools don’t speak VNC. The infrastructure that does — headless Linux servers, IoT panels, KVMs on lab gear, embedded device displays — has had to live in a separate tool. ShellYard ships an in-app noVNC framebuffer so the screen lives in the same window as the SSH session that got you in.
Auth
VNC connections support:
- No auth — for fully open framebuffers (lab gear, isolated IoT).
- VNC password — the legacy DES-based VNC auth, with the password resolved from the active Space’s vault.
- VeNCrypt / TLS — modern encrypted handshake where the server supports it.
Credentials resolve from the vault on connect, the same way SSH and RDP credentials do. The cleartext password never lives on the connection row.
SSH-tunnel routing
Pick any active SSH session as the route. The VNC handshake and framebuffer stream flow out the SSH session’s network instead of your local one — the same pattern as the HTTP client’s tunneling. Useful for VNC servers behind a jump host or on a customer network that isn’t reachable from your machine.
Performance
- Bandwidth-aware encodings (Tight, ZRLE, Hextile) negotiated based on the round-trip ping
- Adjustable framerate cap to keep CPU sane on cellular / Wi-Fi
- Local cursor rendering so pointer motion stays responsive even on a slow link
Tier behavior
VNC is available on every tier including Free. The connection lives in your Personal Space on Free, syncs cross-machine on Pro, and can be shared into a Shared Space on Team and Enterprise.