termique vs mRemoteNG
Maintained cross-platform SSH manager vs legacy Windows tool
The short version.
- Free and open source
- RDP, VNC and SSH in one tabbed window
- Already approved on many corporate images
- Passwords in an XML file, plaintext by default
- Windows only
- Slow, infrequent releases
- Credentials encrypted on your device, always
- macOS, Windows and Linux, synced
- Regular releases with a public changelog
On mRemoteNG out of habit rather than need? termique is a real upgrade in security and platform support.
Every row, side by side.
Where the two part ways.
01Credentials
- termique
- AES-GCM, key derived on your device.
- mRemoteNG
- XML on disk, plaintext unless you opt in.
Read the detail
Credentials in XML vs E2EE vault. mRemoteNG stores connection configurations, including passwords, in an XML file. By default this file is not encrypted - your credentials are readable plaintext on disk. An optional encryption passphrase can be set, but it is not enforced, is easy to forget to configure on new installations, and the protection does not extend to syncing or sharing the file. Termique encrypts your credentials with AES-GCM using a key derived on-device from your master password via PBKDF2. The server stores only ciphertext it holds no key for. The file on disk contains nothing readable without your master password. This is not a marginal improvement - it is a fundamentally different security model.
02Platforms
- termique
- macOS, Windows and Linux, with sharing.
- mRemoteNG
- Windows only.
Read the detail
Windows-only vs cross-platform. mRemoteNG runs on Windows only. Developers and teams working across macOS, Windows, and Linux cannot share a workflow around it. The connection configuration XML file does not travel between platforms. Termique runs natively on all three platforms via a Tauri runtime, and host configurations sync automatically across machines via encrypted cloud sync. A macOS developer and a Windows developer on the same team see the same host library, the same groups, and can share hosts with each other via Termique's built-in share-invite feature. There is no per-platform workaround, no exported files, and no manual reconciliation.
03Maintenance
- termique
- Regular releases.
- mRemoteNG
- Long gaps between versions.
Read the detail
Legacy maintenance cadence vs active development. mRemoteNG has a long history, and many organizations use it because it was adopted years ago and continues to work for basic connection management. Release cadence has slowed significantly. The project has long gaps between versions and an open issue backlog that grows faster than it is resolved. Security patches, modern SSH cipher support, and new features arrive slowly if at all. Termique ships regular releases across all platforms with a public changelog, active bug tracking, and a feature roadmap driven by user feedback. For teams that need their SSH tooling to keep pace with infrastructure changes and security requirements, the maintenance posture matters.
On every device you use.
mRemoteNG is Windows-only and integrates with Windows RDP, which is a real advantage if you manage desktops as well as servers.
Not available. A mixed team ends up maintaining two different host lists, which is exactly the state that leads to stale credentials sitting in someone's notes.
Moving over from mRemoteNG.
- 01Export from confCons.xml
mRemoteNG stores everything in confCons.xml under %APPDATA%\mRemoteNG. Use File > Export to write a CSV of your connection tree - readable, and it shows exactly which credentials were stored where.
- 02Separate the SSH hosts
Filter the export down to the SSH entries. RDP and VNC connections stay with mRemoteNG or move to a dedicated remote-desktop tool.
- 03Import into Termique
Recreate the SSH hosts, mirroring your folder tree as groups. Re-enter passwords once - they are AES-GCM encrypted on-device rather than sitting in a config file.
Does Termique support RDP or VNC?
No. Termique is SSH and SFTP. If you need RDP in the same window, keep mRemoteNG or use a dedicated remote-desktop client.
How does credential storage differ?
mRemoteNG encrypts confCons.xml with a password that defaults to a well-known value, so an unmodified file is effectively readable by anyone who takes it. Termique derives a key from your master password with PBKDF2 on-device and encrypts each credential with AES-GCM.
Is mRemoteNG still maintained?
Development has been intermittent, with long gaps between releases. It still works. Whether that is acceptable for a tool holding your production credentials is a judgement call.
Can I import confCons.xml directly?
Not as a file. Export to CSV from mRemoteNG first, then add the SSH hosts in Termique.
Does Termique run on macOS and Linux?
Yes. mRemoteNG is Windows-only, which is usually the reason a mixed team looks for an alternative.