Built for machines you can’t walk over to.
GoodLink is a remote-desktop control plane with two planes that never mix: a small control plane for presence and commands, and a data plane for session media and file bytes. Everything below is what that buys you — described exactly as it behaves, with the limits stated, not buried.
Stability is the product
A network blip is a hiccup, not a funeral. Reconnect is a state machine, not an apology: if the network drops, the gateway holds the session open on the machine side for a minimum 60-second grace window while the viewer shows a reconnecting countdown instead of an error dialog. When the network returns, the session re-attaches by its own identity and the same desktop resumes with no engine re-login.
Underneath, three supervised binaries and a watchdog keep the agent alive: the control connection reconnects forever with jitter, so Cloud Run recycling and request ceilings are non-events. And when a session can’t be saved, self-repair climbs a ladder automatically rather than giving up.
It goes deeper than the connection. Every long-lived resource — each file descriptor, input buffer, socket, and daemon — is supervised for the failure other tools miss: the wedge where a stuck descriptor or a crashed input buffer silently kills remote input, and the only fix is a restart you can no longer reach. GoodLink detects that locally and heals it itself, because the repair is agent-driven — it never needs the remote input that just died.
- 1
Reconnect the control session
- 2
Restart the screen capture
- 3
Restart the remote-desktop engine
- 4
Reboot the machine (with permission)
- 5
Hand you an out-of-band JetKVM link (layer 0)
Honest diagnosis
The console never just says “offline.” From health-only heartbeat telemetry it tells you why — the difference between a 30-second fix and a wasted drive across town. Degraded machines surface before they fail.
Agent down
The machine itself lost its control connection — a different problem from a sick engine.
Engine listener down
The box is online but the RDP/VNC listener is not answering. Restartable in place.
No display session
No one is logged in at the console, so there is nothing to capture yet.
Network flap
A transient drop — the reconnect state machine is already handling it.
Clock skew
The host clock has drifted far enough to break token validity. Surfaced before it bites.
Disk full
A capacity problem the operator can fix remotely before it takes the machine down.
Zero-config connectivity
Setup is deliberately trivial: one installer and one short code. On the target machine you run a single install command and paste a short enrollment code — read from stdin, never your shell history. The machine registers itself with its own key and from then on dials outbound only.
That means zero inbound ports, no port-forwarding, and no VPN to configure. The controlled machine never has to be exposed to the public internet — sessions reach it through the gateway over an outbound tunnel the agent opened.
One installer
Linux, Windows, or macOS — a single package per OS from get.goodlink.cloud.
One short code
A single-use, short-lived enrollment code registers the device with its own Ed25519 key.
Outbound only
The agent dials out to the gateway. No inbound ports, no firewall holes to open.
Full session control
Once pixels flow, the viewer delivers real control — from a browser or a phone. The limits below are the honest ones: text-only clipboard, a single monitor per session, and no Linux-tier audio in v1.
Session scaling
Fit, fill, 1:1, and custom scaling modes so the remote desktop fits whatever screen you are on.
Two-way clipboard
Copy and paste in both directions, with an honest 256 KB cap. Text-only in v1 — no image or file paste through the clipboard channel.
Keyboard control
An on-screen keyboard, a per-OS shortcut bar, and a real Ctrl-Alt-Del that bypasses browser key capture.
File transfer sideband
Move files both ways over a dedicated channel — offset-addressed for resume, SHA-256 verified, atomic rename on completion. Not screen-scraping.
Works on your phone
Touch and mobile-IME modes make full sessions usable from iPhone Safari — the same bar as the console.
Built for automation and headless ops
GoodLink isn’t only a viewer. The same authenticated, outbound-only tunnel opens your fleet to terminals, scripts, and tools — and reaches machines with no screen at all. These capabilities are rolling out to invite users; where a piece is still landing, we say so.
Key-based headless access
Add your SSH public key to your account and the cloud syncs it to your machines. Then connect the way you already administer servers — full root, no inbound port, no display required — at fleet scale, brokered through the tunnel instead of an exposed sshd.
Root terminals & log streams
Open a root shell, tail journald or a process’s output, or bridge a local socket — all multiplexed over the one tunnel the agent already opened. Every channel is authenticated, authorized, and audited.
Query before you connect
Ask a machine exactly how to drive it — OS, X11 vs Wayland, every display’s scale and geometry, keyboard layout and its limits — before a session even opens, so a controller (or an automation) knows the machine precisely.
A control surface for scripts & AI
A machine-readable control surface with per-scope tokens lets scripts and AI agents work with your fleet — reading capabilities, opening root terminals, coordinating sessions — using each machine’s exact profile for scale-aware, layout-correct input.
Headless machines
No monitor attached? GoodLink can provision a virtual display so a screenless server has a desktop to manage, driven over the same path as any other machine.
Consent on install, not on use
You grant control once — when you install the agent on a machine you own. After that it is frictionless: no per-action prompts, no artificial caps. Security is authentication + authorization + a full audit trail + instant revocation.
Out-of-band recovery (layer 0)
The last rung of the ladder is hardware GoodLink does not ship but fully integrates: each fleet machine can be linked to a JetKVM. When every software rung has failed — a wedged boot, a dead OS, a machine that won’t answer — the console renders a recovery card that deep-links to hardware-level control: power-cycle, BIOS, a screen that works even when the machine’s software is gone. Every power action is audit-logged.
What’s next
Next · specced, not shipped
GoodLink’s own engine
Today GoodLink drives sessions through proven borrowed engines (RDP/VNC via guacd). The roadmap adds GoodLink’s own capture, encode, input, and wire protocol across all three operating systems — designed to slot in behind the same adapter interface, side-by-side with the borrowed engines and reversibly. It is researched to spec depth and is the next phase, not a current feature. We label it as such rather than claim it early.
See it on your own fleet.
GoodLink is currently invite-only. Have an account? Sign in to get started.