Networking
Jump Hosts
Reach machines behind bastions through one hop or several, each with its own credentials and host key check.
A jump host (bastion) sits between you and a protected machine. SwiftServer connects to the bastion first, then tunnels the real connection through it — through one hop or a whole route of them. Jump hosts are part of Premium.
Set up a route
In the machine editor, enable Use Jump Host:
- Select Jump Host — any saved machine can be a hop.
- Add Hop for multi-hop routes; reorder or remove hops as needed. The visualization shows the full path ending at your Destination.
- Clear Route removes the whole chain.
Because each hop is just a machine, each hop authenticates with its own credentials and passes its own host key check — a compromised first hop still can't silently impersonate the second.
Everything that rides the machine's connection — terminal, SFTP, Docker, port forwarding, monitoring — automatically goes through the route.
Notes
- Dashboard status needs unattended logins, so it is disabled when any hop requires an interactive prompt.
- Mosh bootstraps through the route, but its UDP session connects directly — set the machine's UDP Host to an address reachable without the route.