Reach your Mac home lab from anywhere
Home labs are built to be left alone. The trouble is that the moment you are away, the machine you need is the one you cannot get to.
Nothing exposed to the internet
No port forward to a machine on your home network, which is the part of the usual setup most worth avoiding.
No VPN to maintain
Nothing to install on every client, nothing to reconnect, and no profile to renew. The pairing lives in your account.
Screen and shell together
Most home lab problems are shell-shaped. The ones that are not tend to be a stuck dialog, and for those you want the actual screen.
Works on a phone, on cellular
Built to connect on strict mobile and carrier networks, so being away from Wi-Fi does not mean being locked out.
Where a Mac fits in a home lab
Most home labs are Linux, and then there is one Mac. It is there because something needs macOS: Xcode builds, iOS automation, Apple-only media tooling, Time Machine, or a service that simply runs better on the hardware you already own.
That Mac is usually the odd one out. The tooling you use for the rest of the lab does not quite fit it, and the answer ends up being VNC over a VPN, or nothing at all.
The access problem, stated plainly
Your home router does not accept inbound connections. To reach anything behind it you either forward a port, run a VPN, or use an overlay network. Each is a real answer with a real cost, and the port forward carries the most risk because it puts a service on the public internet.
Many people on CGNAT cannot forward a port at all, which removes the simplest option entirely.
- Port forwarding exposes a service and needs a stable address.
- A VPN is another service to run, update, and troubleshoot.
- CGNAT can make inbound connections impossible regardless.
How Servey reaches it
The Mac runs a host app and registers to your account. Your iPhone or iPad signs in to the same account and sees it. On your home network the connection is direct; from outside, Servey establishes a private encrypted path between your two devices and is built to traverse strict networks, including CGNAT.
There is nothing to configure on the router and nothing listening on a public address.
What it does not cover
Servey reaches Macs running its host app. It will not give you a console on your Linux boxes, your NAS, your switch, or anything else in the rack. It is one tool for one machine, not a replacement for however you manage the rest of the lab.
It is pre-launch, so treat it as something to try alongside your existing setup rather than something to depend on yet.
Frequently asked questions
- Do I need to open a port on my router?
- No. Servey does not use inbound connections to your network, so there is nothing to forward and nothing exposed on a public address.
- Does it work if my ISP uses CGNAT?
- Yes. Servey is built to establish a connection between your own devices even on strict carrier networks where inbound port forwarding is not possible.
- Can it reach my Linux machines too?
- No. Servey connects to Macs running its host app. The rest of your lab needs whatever you already use for it.
- Do I still need a VPN?
- Not for reaching your Mac through Servey. If you use a VPN for other machines on the network, that is unaffected either way.
- Can I use it now?
- Not yet. Servey is pre-launch. This page describes the app's design rather than anyone's experience running it, and the waitlist is open.
Servey puts your Mac in your pocket. Launching soon.