I Built ShellSSH: A Different Take on SSH Clients Like Termius, Termux and PuTTY
SSH itself doesn't need reinventing. The workflow around SSH might. For years, my typical server workflow looked something like this: Find server credentials ↓ Open SSH client ↓ Connect ↓ Need a file? ↓ Open SFTP client ↓ Need another server? ↓ Find another profile ↓ Something looks wrong? ↓ Connect and start checking None of these steps is particularly difficult. The friction comes from…
SSH protocols aren't fundamentally revolutionary, but the surrounding workflow can be improved. For years, my workflow included finding server credentials, opening an SSH client, connecting, using an SFTP client for files, locating another profile when needed, and troubleshooting issues by reconnecting. This repetitive process across multiple servers led to the creation of ShellSSH.
What is ShellSSH? ShellSSH is an SSH and server-management application that works on Windows and Android platforms. Rather than treating the terminal as the entire product, ShellSSH positions it as just one part of a server workspace. Its current features include: SSH terminal sessions, SFTP file management, SSH key management, saved servers, and server status/monitoring.
Compared to established tools like Termius, ShellSSH differs in its narrower focus on server-centric workflow, while Termius offers broader cross-platform capabilities with advanced collaboration features. Termux, another comparable product, provides a Linux-style terminal for Android, but ShellSSH offers a dedicated graphical interface for remote server management.
PuTTY, a long-standing Windows SSH client, contrasts with ShellSSH's server-centric approach. MobaXterm, an extensive Windows remote-computing tool, focuses more on a broader range of remote administration functionalities beyond SSH and SFTP. ShellSSH acknowledges that different users have varying requirements, from developers to network engineers and Linux power users.
The application aims to address key questions before connecting: Which servers are available? Which one is currently being worked on? Is it online and behaving properly? Can files be accessed? Which identity should be used? Can the same process be performed from a different device? By answering these questions, ShellSSH positions the terminal as a component of a broader workflow, rather than the entire process itself.
ShellSSH's development is ongoing, and user feedback is highly valued, particularly from those who frequently manage Linux servers.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
