Getting a machine onto your fleet is deliberately trivial: one installer and one short code, and zero port forwarding. Here is the whole flow.
1. Mint an enrollment code
In the console, create an enrollment code for the machine you want to add. The console hands you a single-use, short-lived code alongside the exact install one-liner to run on the target machine.
2. Run the installer on the machine
On the target machine, install GoodLink from
get.goodlink.cloud — a .deb one-liner on Linux,
an MSI on Windows, or a .pkg on macOS. On its first run the agent asks for the
enrollment code, which it reads from standard input rather than the command
line, so the code never lands in your shell history.
Enrollment generates a device keypair on the machine, registers the device, and stores its private key locally with owner-only permissions. From that point on the agent authenticates every connection with a short-lived, per-connection token signed by that key — there are no standing passwords anywhere.
3. The machine comes online
Once enrolled, the agent dials outbound only to the GoodLink gateway and holds a single control connection open, reconnecting forever if the network blips. That means zero inbound ports, no port forwarding, and no VPN to set up — the controlled machine never has to be exposed to the public internet.
Every 60 seconds the agent reports health telemetry — engine status, disk, display session, clock skew — so the console can tell you why a machine is unhappy instead of only that it is “offline.”
What you get
With the machine online you can open a full remote-desktop session from a browser or a phone, move files over a dedicated verified sideband, and — if a machine is linked to out-of-band recovery hardware — reach it even when its software is gone. See How GoodLink works for the two-plane picture, or jump straight to the features.