The honest comparison
| What matters | PortPane (a launcher) | All-in-one clients |
|---|---|---|
| What it is | A launcher that opens the clients you already use | Clients with a built-in terminal, VNC viewer and RDP |
| Remote desktop built in | No — opens macOS Screen Sharing, Terminal, your RDP app | Yes — bundled viewers and terminals |
| Bonjour discovery | Yes — finds Macs, PCs and servers advertising Screen Sharing, SSH or RDP | Some (e.g. Remoter); most need manual entries |
| Imports ~/.ssh/config | Yes — aliases, keys, ProxyJump and port forwards keep working | Partial or manual in most |
| Menu-bar quick connect | Yes — your five most recent machines, one click away | Rarely |
| Local-first, no account | Yes — no account, no agent, no stored passwords | Varies; several require an account or a subscription for the full feature set |
| Learning curve | Use what you know — the same clients you already use | A new client to learn for every protocol |
| Pricing | Pre-launch — join the waitlist | Free tiers plus paid subscriptions (Termius is about $10/month billed annually) |
When PortPane is the right fit
- You already work in Terminal, macOS Screen Sharing and your RDP app, and want one place that lists every machine.
- You manage a mix of Macs, Windows PCs, Linux servers and a Raspberry Pi, and want discovery and quick connect without adding another protocol stack.
- You live in your
~/.ssh/configand want aliases, keys and ProxyJump to keep working exactly as they do today. - You prefer local-first software — no account, no agent on your machines, no stored passwords.
When an all-in-one client is the better fit
- You want a single window with tabs that contains the terminal, VNC and RDP sessions themselves.
- You need features the built-in clients do not offer, such as multi-tab terminals, session logging, shared accounts or a serial console.
- You are willing to move your SSH keys and host list into a new client to get everything in one place.
Why the launcher approach works
PortPane does not re-implement remote desktop. It builds on the clients Apple and Microsoft already ship: Screen Sharing and Terminal on macOS, and the Remote Desktop app you choose. That means no new protocol code, no new security surface, and your existing keys and aliases keep working. PortPane’s job is the part those tools do not do well: keeping your whole fleet — every machine, space, and the right connection for each one — in one pane.
Common questions
Is PortPane a remote desktop client?
No. PortPane is a launcher. It opens macOS Screen Sharing for VNC, a compatible installed client for RDP, and Terminal for SSH. Those clients handle the actual remote sessions.
Do I need to learn a new terminal or VNC viewer with PortPane?
No. PortPane launches the apps already on your Mac. Your SSH config, keys, ProxyJump and port forwards keep working exactly as they do today.
When should I use an all-in-one client instead of PortPane?
If you want one app that bundles its own terminal, VNC viewer and RDP client, an all-in-one client like Termius, SSHive, Remoter or Royal TSX is a good fit. PortPane is for people who already have a workflow and want every machine in one menu bar.