Termius Alternative for Mac: How to Move Your SSH Setup
If you are looking for a Termius alternative on your Mac, the fastest route is not to rebuild every saved server by hand. macOS already ships OpenSSH, and most of what Termius keeps in its vault can be written into ~/.ssh/config in an afternoon. Do that once and you can move to any Mac SSH client — or stay in Terminal — without losing your host list, keys, or tunnels.
This page is about the move itself: what to write down, the file to create, how to check it, what you pay afterwards, and the cases where leaving Termius is the wrong call. If you are still weighing the two products rather than migrating, read the Termius and DartShell comparison instead.
Why people start looking for a Termius alternative on Mac
The reasons are usually practical rather than ideological.
- An account sits in front of the host list. Termius syncs through an account and a cloud vault. That is convenient across devices, but it also means your saved sessions depend on a login state you do not control. If you only ever connect from one Mac, you are paying for plumbing you do not use.
- SSH is rarely the whole job. A normal maintenance day can include a Windows box over RDP, a VNC session, a database query, a file transfer, and a tunnel. Termius is deliberately SSH-first, so the rest lives in other apps.
- The subscription does not end. Pro renews every month or year. For a tool you open every working day, that recurring line is easy to notice after a couple of years.
None of this makes Termius a weak client. It means a Mac that does more than pure SSH may want a different shape of tool.
What to write down before you cancel anything
Termius stores hosts, keys, snippets, and forwarding rules in its own vault rather than in a plain text file. Before changing clients, take an inventory of the connections you actually use — most people find that a handful of hosts matter and the rest are stale.
| Termius field | Where it goes on the Mac |
|---|---|
| Host label | Host alias in ~/.ssh/config |
| Hostname, port, username | HostName, Port, User |
| Private key | IdentityFile pointing at the key file on disk |
| Jump host / bastion | ProxyJump |
| Saved local or remote forwarding | LocalForward / RemoteForward / DynamicForward |
| Snippets and saved commands | A shell alias or a script in your dotfiles |
Keep Termius installed and your subscription active until the last verification below passes. There is no reason to lose access to a production box while testing a new client.
Step 1: Put your hosts in ~/.ssh/config
OpenSSH reads this file on every connection, so it becomes the portable source of truth. A realistic example with a bastion and a database tunnel looks like this:
Host bastion
HostName bastion.example.com
User ops
Port 22
IdentityFile ~/.ssh/id_ed25519
Host api-prod
HostName 10.0.1.24
User deploy
Port 22
IdentityFile ~/.ssh/id_ed25519
ProxyJump bastion
Host staging-db
HostName 10.0.2.18
User deploy
IdentityFile ~/.ssh/id_ed25519
LocalForward 5433 127.0.0.1:5432
Save it and lock down the permissions:
chmod 600 ~/.ssh/config
Two rules matter here. Reference the key file by path — never paste a private key into the config — and give every host a short alias you can remember. If you are moving keys between Macs at the same time, the steps in managing SSH private keys on Mac cover permissions and passphrases. Forwarding rules are the item most often forgotten; local port forwarding on Mac shows how to check that the tunnel really comes up.
Step 2: Verify the config before switching clients
OpenSSH can print the effective configuration for an alias, which lets you catch typos without connecting:
ssh -G api-prod | grep -E '^(hostname|user|port|proxyjump|identityfile) '
Then run a real connection with a short timeout:
ssh -o ConnectTimeout=8 api-prod 'uname -a'
For the tunnel host, confirm that the forwarding rule was parsed:
ssh -G staging-db | grep -i localforward
Test at least one host that uses a jump chain and one that uses a key. If either fails, fix it in the config file first — every Mac SSH client will read the same values.
Step 3: Choose where the host list lives
You now have three workable options, and the config file is useful in all of them.
- Terminal or iTerm2. Type
ssh api-prod. Free, already installed, and the config is easy to keep in a dotfiles repository. The trade-off is that the host library is a text file, with no GUI for RDP, VNC, or file transfer. - DartShell. Import the SSH config directly: open the import option, pick
~/.ssh/config, review the parsed hosts, then assign groups and tags. It also keeps RDP, VNC, SFTP, serial, and database connections in the same host list, so a machine that needs more than SSH stays one record. The full SSH config import walkthrough covers the preview step, and sharing SSH config through iCloud Drive explains how to sync the configuration across Macs without a separate account. - Keep both for a while. Point the new client at the same config, run your five most-used hosts in both, and compare. This is the lowest-risk way to move.
After importing, spot-check jump hosts, key authentication, and one tunnel in the new client. Only then cancel Pro and remove the old app.
What you pay after switching: subscription and one-time licence
Prices below are from the Termius pricing page and the DartShell App Store listing in November 2026; checkout is the authority, and regional prices vary. The multi-year column is simple arithmetic on the annual-billing rate, not a quoted multi-year plan.
| Termius | DartShell | |
|---|---|---|
| Free tier | Starter: local vault, SSH, SFTP, port forwarding on one device | SSH and basic SFTP, up to 3 servers |
| Paid plan | Pro, $10/month with annual billing | Pro, one-time $9.99 (limited offer; list $17.99) |
| First year | $120 | $9.99 |
| Three years | $360 | $9.99 |
| Five years | $600 | $9.99 |
| If you stop paying | Pro features, cloud vault, and cross-device sync turn off | The licence keeps working |
Team is $20 per seat per month and Business is $30 per seat per month, so the gap is wider for shared vaults. Two caveats keep this table honest: if you are on Starter, there is no bill to escape, and switching purely for price saves nothing. The numbers only matter once you are paying for Pro, and the Termius subscription is buying cross-device sync and team features that a macOS-only app does not provide.
When you should stay with Termius
Switching is not automatically an upgrade. Keep Termius if any of these describe your week:
- You answer alerts from an iPhone or Android device, or work from Windows and Linux as well as macOS. DartShell is macOS only, with no mobile or Windows build.
- Your team shares a vault of hosts and credentials, or you need shared session logs and access control.
- You rely on synced snippets and command history across several machines.
- Your work is entirely SSH and SFTP and the free Starter tier already covers it. Migrating costs an afternoon and saves zero dollars.
- You are in the middle of an incident or a deadline. Move the config when nothing is on fire.
A fair summary: Termius is the better fit when the value is a single account across many devices and people. A Mac-only replacement is the better fit when the value is a local host list, a one-time licence, and fewer apps open at once. For a broader look at where iTerm2, SecureCRT, Termius, and DartShell each fit, see how to choose an SSH client on Mac.
Frequently asked questions
Can I export my Termius hosts directly?
Termius keeps hosts in its own vault and does not offer a general SSH config export of the whole list. The reliable route is to write the hosts you still use into ~/.ssh/config once — aliases, ports, users, key paths, and jump chains — and use that file as the source of truth going forward.
Do my private keys move with the config?
No, and they should not. The config stores only the path to the key file, such as ~/.ssh/id_ed25519. Copy keys separately with their existing permissions (chmod 600), and never paste a key body into a config file, a cloud note, or a form field.
Will I lose my port forwarding rules when I leave?
Only if you leave them behind. Forwarding rules usually live in session properties rather than in the SSH config, so add LocalForward, RemoteForward, or DynamicForward lines explicitly before you cancel anything, then confirm with ssh -G <alias> | grep -i forward.
Is there a free Termius alternative on Mac?
Yes. macOS includes OpenSSH, so Terminal plus ~/.ssh/config costs nothing and handles hosts, keys, jump hosts, and tunnels. iTerm2 adds a better terminal on top. A GUI client earns its place when you want a searchable host library, reusable credentials, and remote desktop or database connections in the same workspace.
Related guides
- Termius and DartShell compared — the head-to-head if you are still comparing rather than moving.
- Import SSH server connections on Mac — the full import and preview walkthrough.
- How to choose an SSH client on Mac — where iTerm2, SecureCRT, Termius, and DartShell each fit.
Related reading
More on the same problem, in the order most people need it.
- PuTTY for Mac: Set Up SSH in DartShell
Configure SSH on a Mac with DartShell, load an OpenSSH private key, save the connection, and verify the remote host.
- SecureCRT for Mac: Is There a Better Alternative in 2026?
What you actually lose by leaving SecureCRT, how many apps four everyday jobs take, and how long a migration takes to…
- How to Choose an SSH Client on Mac: iTerm2, Termius, SecureCRT
Check what actually separates Mac SSH clients — finding hosts, reusing credentials, jump hosts — and how iTerm2…
DartShell
Want a smoother remote ops workflow on macOS?
DartShell brings SSH, RDP, VNC, SFTP, and serial access together in one native macOS app, so you can reduce tool switching and repetitive setup.
Download DartShell