For your own machines
A handful of machines, no sysadmin team, and no desire to manage SSH config drift across every laptop you own. WingGate gives a single person one control plane for every box they run.
The machines this is for
If most of your infrastructure fits on one hand, this page is about you:
VPS instances
One or two rented servers running your services. Reach them from any browser without copying keys to every device you touch.
Home server
A machine behind NAT or a dynamic IP. The connector dials out, so it stays reachable with no port forwarding and no public inbound exposure.
Personal dev machine
The workstation or spare laptop you occasionally need when you are away from it. Open a Web Terminal from a phone or a borrowed computer.
Lab and experiment boxes
Machines that get rebuilt often. Host key probing and explicit confirmation make rebuilds visible instead of silently trusting whatever answers.
A typical afternoon
From a fresh account to reaching your first machine, the whole loop is:
- Register and finish MFA enrollment. One account, one organization — no team setup required to start.
- Install a connector on (or next to) the machine. It connects outbound to WingGate over mTLS; nothing inbound to open on the box itself.
- Register the asset and attach a Connection Profile. Address plus SSH credentials, stored separately from your login credentials.
- Confirm the host key, then connect from the browser. Web Terminal is the default path; your own SSH client works too once you register a public key.
Why it fits a one-person setup
- Cheap to start. A single organization is enough — no project structures, grants or member management to configure before the first connection.
- Nothing listens inbound. Home boxes behind NAT and VPSes alike stay closed to the internet; the connector only dials out.
- No local SSH config to lose. New laptop, phone, borrowed machine — the Web Terminal is identical everywhere, so device churn stops mattering.
- SSH when you prefer it. Register your public key and keep using your own client; WingGate never holds your private key. Both entrances share the same audit trail.
- Host key confirmation scales down. Probing and pinning is a one-minute habit even for a single user, and it is what catches a silently replaced machine.