Terminals — Old but Handy Remote Connection Manager for Windows
What it is
Terminals is an open-source client for Windows that’s been floating around IT circles for years. It was never meant to be flashy — the goal was simply to keep all those RDP, VNC, SSH, and Telnet sessions under one roof. A lot of admins still keep it in their toolbox, not because it’s new or shiny, but because it gets the job done without licenses, fees, or overcomplication. Development has slowed down, but the program itself still works fine on modern Windows.
How it works
Connections are saved as profiles in a local database. Each one can store usernames, passwords (if you want), and display settings. The big convenience is tabbed sessions — instead of twenty RDP windows cluttering the desktop, everything runs inside a single window with tabs. Out of the box, Terminals speaks RDP, VNC, SSH, Telnet, Rlogin, and even ICA for Citrix. For passwords, it can hook into Windows Credential Manager, which is usually safer than leaving them in the app itself.
Technical profile
| Area | Details |
| Purpose | Multi-protocol remote client |
| Platforms | Windows only |
| Protocols | RDP, VNC, SSH, Telnet, Rlogin, ICA |
| Features | Tabs, grouping, credential storage, search |
| Authentication | Username/password, SSH keys |
| Security | Uses Windows Credential Manager; database encryption available |
| Licensing | GPL, free |
| Deployment | Portable or installer |
Why admins keep it around
It’s free and doesn’t nag about licensing. Tabs make life easier when bouncing between dozens of servers. Simple interface — no steep learning curve. Portable version can be carried on a USB stick. Still runs fine on Windows 10/11 despite no big updates.
Usage scenarios
– A sysadmin juggling Windows servers via RDP while occasionally hopping into network switches with SSH or Telnet.
– Small IT teams keeping lab machines organized in one client.
– Freelancers or consultants carrying Terminals on-site for quick access.
– Shops that want something light instead of paying for Remote Desktop Manager.
Security notes
Since the project isn’t actively maintained, best practice is to use it inside trusted networks. If credentials are stored, rely on Windows Credential Manager, not the app’s own storage. For environments with strict compliance, it’s better to move to something still supported.
Limitations
No real development in years, so don’t expect bug fixes. Windows only, no cross-platform version. Interface feels dated next to modern tools. Missing enterprise features like shared vaults or central role-based control.
Comparison snapshot
| Tool | Strengths | Best fit |
| Terminals | Free, tabs, simple | Labs, consultants, small IT shops |
| mRemoteNG | Lightweight, open source | Windows admins needing a fresher fork |
| RDM Free | More structured, extra features | SMBs that want organization |
| Remmina | Linux-native | Mixed Linux-heavy environments |
| Royal TS Free | Modern UI, cross-platform | Teams testing before upgrading |
Minimal checklist
– Download Terminals (installer or portable).
– Add connection profiles for servers and devices.
– Configure credential storage via Windows Credential Manager.
– Group sessions for clarity.
– Use mainly in lab or internal networks.