termique vs SSH Config file
Visual SSH manager vs manual config files
The short version.
- Works with every SSH tool: ssh, scp, rsync, Ansible, git
- Scriptable, diffable and version-controllable
- No vendor, no account
- Passwords and passphrases are not stored
- No UI; one bad edit breaks everyone
- No sync between machines
- A visual host manager anyone can edit safely
- Credentials encrypted end-to-end
- Imports your existing ~/.ssh/config
Keep the file if a dozen hosts live in your head. Once a team shares them, termique is easier and safer.
Every row, side by side.
Where the two part ways.
01Editing
- termique
- A visual manager anyone can use safely.
- SSH Config file
- A shared text file nobody wants to touch.
Read the detail
The config file nobody dares to touch. Every team has a shared SSH config that's grown organically for years. Nobody knows what half the entries do, and editing it means risking breaking everyone's workflow. Termique replaces it with a visual manager anyone can use safely.
02Credentials
- termique
- Encrypted vault, one-click connect.
- SSH Config file
- In your clipboard or your head.
Read the detail
Credentials in plaintext vs encrypted vault. SSH config stores hostnames and keys - but passwords and passphrases still live in your clipboard or head. Termique encrypts your credentials end-to-end with AES-GCM, syncs them to the cloud, and connects in one click. No plaintext, no clipboard exposure.
03Setup
- termique
- Add a host, click connect.
- SSH Config file
- Syntax, chmod and silent failures.
Read the detail
From zero to session without a manual. Setting up SSH config requires knowing the syntax, managing key permissions with chmod, and troubleshooting silently failing entries. Termique is a UI - add a host, click connect, done.
On every device you use.
~/.ssh/config is already there and already works. Termique reads it on first launch and leaves it in place as your source of truth.
OpenSSH ships with Windows 10 and 11, so %USERPROFILE%\.ssh\config works too, though far fewer people keep one. Termique gives Windows the host list the file never really provided there.
Moving over from SSH Config file.
- 01Nothing to migrate
Termique reads ~/.ssh/config on first launch. Your Host blocks, HostName, Port, User and IdentityFile entries all come across.
- 02Keep the file
Termique does not take the file over. Keep editing it by hand for scripting and Ansible; use Termique when you want search, grouping and a credential vault.
- 03Add what the file cannot hold
Passwords are the one thing ~/.ssh/config cannot store, which is why they end up in a password manager and the clipboard. Add them in Termique once, AES-GCM encrypted on-device.
Will Termique overwrite my ~/.ssh/config?
No. It reads the file to import hosts and leaves it as your source of truth. You can keep editing it directly.
Why use an app if the config file works?
Three things a text file cannot do: store credentials safely, sync encrypted across machines, and give you a searchable list when the file has grown to two hundred entries.
Does Termique support ProxyJump and bastion hosts?
Jump-host configuration defined in ~/.ssh/config is respected on import. Complex multi-hop chains are still easier to express in the file itself.
Can I keep using ssh and scp on the command line?
Yes. Termique does not change how the system ssh client behaves, and it uses standard OpenSSH keys.
Is Termique free?
Yes to download, with unlimited hosts, unlimited sessions and SFTP on the free tier.