Mac@Xa
What's different

Where Mac@Xa does things differently

Most remote software pushes your screen through the cloud of whoever made it. Mac@Xa skips that part: your two machines shake hands with each other, and the meeting point in between only moves bytes along, holding no key to open them.

While it sleeps

Reach the Mac even while it sleeps

A sleeping Mac drops its connection, and Wake-on-LAN cannot cross your ISP's router — which is where most remote software gives up. The Mac at home schedules its own wake-ups in hardware, opens an eye every few minutes to see if anyone is calling, and goes back to sleep after eight seconds if nobody is. Call while it sleeps and you wait in a queue, told exactly when it will wake — no guessing.

Nothing installed

Works from a borrowed machine, in the browser

The machine at the café, a colleague's Windows laptop, the shared box at the office — places you cannot install software. Open Chrome or Safari, go to the remote page, type the ID and the code, and your Mac's screen is there. Same end-to-end encryption, and closing the tab leaves nothing behind.

No account

No back door

The other tools all ship a vendor console. Whoever takes over that account reaches your Mac. Mac@Xa has no such door to take over.

Blind relay

The meeting point cannot read a thing

It joins the two ends and copies bytes, nothing more. Session keys come from the 6-digit code PLUS a per-session ECDH secret it holds no part of, so all that passes through is random noise.

X25519 + HMAC

The 6-digit code never leaves

Both ends sign a fresh random challenge and compare proofs, and the session key also mixes in an ECDH secret the two machines exchange between themselves. Record the whole session and the code is still safe.

Port 443 only

Gets through hotel and office firewalls

To the network you are sitting on, the session looks exactly like an HTTPS connection. No ports to request, no VPN, no static IP.

LAN first

Same network, direct route

The app tries a direct connection first and only falls back to the server when that fails. You never pick a route; it takes the shortest one available.

30 fps

Encoded by the chip, not the CPU

H.264 runs on Apple silicon itself, so the Mac at home stays cool and the battery in your hand lasts a good deal longer.

Side by side

Where the video travels
Mac@Xa:Straight between your two machines, or a blind relay
Typical remote software:Through the vendor's cloud
Account required
Mac@Xa:No — a 9-digit ID and 6-digit code made on the device
Typical remote software:Mandatory, with email and phone number
Who holds the decryption keys
Mac@Xa:Only your two machines
Typical remote software:The vendor, at least technically
What you must set up
Mac@Xa:Nothing — no VPN, no port forwarding
Typical remote software:Install the vendor app and sign in to an account
Video compression
Mac@Xa:Hardware H.264, 30 fps, adaptive bit rate
Typical remote software:Varies; VNC-based ones lag noticeably over distance
Share a single window
Mac@Xa:Yes, picked from the running apps
Typical remote software:Rarely offered on macOS
Use it from a machine you cannot install on
Mac@Xa:Open the remote page in Chrome or Safari, that's it
Typical remote software:Usually an install; browser builds, where they exist, go via the vendor cloud
Works behind a corporate firewall
Mac@Xa:Yes — port 443 only, indistinguishable from a website
Typical remote software:Usually, since it also travels via the vendor cloud
Footprint on the machine
Mac@Xa:One menu bar icon, no stray windows
Typical remote software:A heavy app plus background services and its own updater

The comparison describes how commercial remote-control software commonly works; individual products differ in the details.

Getting started is quick

Install the app on the Mac at home, give it a role, then type two numbers at the other end — from the app or from a browser, either works. Ten minutes or so, and nothing to disclose about yourself.