Compare
Termuna vs Termius.
Termius is a very good SSH client with a synced vault. Termuna is a terminal whose sessions do not end. If you are choosing between them, the decision is usually one of three things, and two of them are about what happens the day you leave.
The short answer
Stay with Termius if you mainly need a polished client for many hosts on many devices and you are fine reconnecting each time. Switch to Termuna if you want the session itself to survive: the build you started at your desk still running when you open your phone, the same scrollback, the same cursor position, and a local terminal that works with no account at all.
1. An account to type
Termius asks you to sign in or create an account on first launch; you can log out afterwards and use it locally, with the vault staying on that device. Termuna's terminal is free forever and never asks: the daemon, the panes and the vault on your disk all work with no network. An account only exists once you want a session to reach a second device.
2. A session, not a connection
Termius opens a connection per device: close the laptop and the remote process is gone unless you were running tmux on the server yourself. Its sync keeps hosts, keys and snippets in step across your devices; the shell is not part of it. Termuna keeps a local daemon that owns the shells, mirrors them end to end encrypted, and hands the same live session to the web or the phone (how that works).
3. What you can take with you
Termuna hands back the whole account as one JSON archive with every encrypted blob verbatim, on every plan, and the format is public at /docs/export. Termius documents import and not export; the community wrote its own exporters. We would rather you could leave easily, and we built it that way.
| What you need | Termuna | Termius |
|---|---|---|
| Use the terminal with no account | Yes, forever | Sign in on first launch, then you can log out and stay local |
| Session survives a closed lid | Yes, the daemon owns the shells, and a dropped SSH link redials into the same pane (the rule), once for every pane on that host: panes and the file lane share one SSH connection, so a new split opens at once and a 2FA host asks once, not once per pane (how) | No, a session is one connection |
| Same live session on the phone | Yes, same scrollback, same cursor | A phone app, but a new connection per device |
| Can the vendor read your scrollback | No, the relay holds ciphertext only | Sessions are not mirrored; the vault sync is end to end encrypted |
| Leaving with your data | One JSON archive, documented, every plan | Import is documented, export is not |
| Price | Terminal free forever. Cloud continuity from $6 a month | Free Starter with a local vault; Pro from $10 a month for sync |
| Termius facts checked on 6 September 2026 against the pages linked above. Prices are the vendor's own on that date and change without telling us. The full five-way matrix is on /compare. | ||
Pick Termius if
- You manage dozens of hosts from an iPad or a phone as often as from a laptop, and its host organiser, with groups, tags and shared identities, is the thing you actually use every day. Our phone app is for continuing a session, not for running a fleet from a couch.
- You want SFTP, port forwarding, Mosh, Telnet and serial from one vendor with years of polish, and you do not need the session to outlive the window. Termuna speaks SSH and SFTP; it does not speak Mosh, Telnet or serial.
- Your team already lives in Termius shared vaults with single sign on and one bill, and the switching cost is a hundred hosts times every colleague.
- You are on a platform we do not ship a native app for yet. Our phone story today is the web dashboard in a browser; the native Android and iOS apps are still coming.
Coming over
Termius has no documented export, so the first step is getting your
hosts into the one neutral place every SSH tool reads,
~/.ssh/config: with a community exporter such as
termius-to-sshconfig,
or by hand for a short list. Then, in Termuna, press Ctrl+K,
type ssh config and choose Link ~/.ssh/config.
Every plain Host block (HostName, User, Port, IdentityFile,
ProxyJump) becomes a host in your encrypted vault, wildcards are
skipped and named, and the link is kept: re-read it after an edit and
the two live side by side while you decide. Nothing leaves your
machine unless you turn on connection sync.
Details on SSH and SFTP.