Build around an ordinary support shift
Start with the machines, user accounts and connection methods your team already uses. We map how an operator finds a server, checks its identity, opens a session and returns to the same task later. Saved profiles, groups and tags follow that map.
The specification covers keyboard shortcuts, copy and paste, terminal resizing, split panes, output search and the handling of a dropped connection. Each session keeps its own target and visible status.
Make the destination clear before a command runs
The interface should show the server and signed in account beside the input. First connections need a host key review. A changed fingerprint goes through a separate verification step. We agree how credentials are stored and who can change a saved connection.
Broadcast input needs explicit selection and confirmation. Routine work should default to the active session. An operator must be able to see when input will reach more than one machine.
Choose the deployment and ownership arrangement
We scope a desktop client, browser workspace or internal portal around your operating systems and network. The agreement covers application code, third party licences, hosting, updates and support. A Windows package needs different installation tests from a hosted browser client.
| Demonstration | Expected result |
|---|---|
| Open two hosts | Separate tabs, output and input targets |
| Connection interruption | Visible state and an agreed reconnect procedure |
| Change server identity | A fresh verification decision |
| Close the workspace | Sessions and stored credentials follow the agreed lock policy |
Bring a few representative tasks
Send the operating systems, approximate host count and three jobs that take too many steps today. Include terminal or file tools you want to retain. Use aliases and redacted examples in the initial enquiry.
Before you begin
Can you build a branded SSH client?
Yes. The work can include your visual identity, server directory, workflows and deployment packages. Third party components retain their applicable licences.
Will reconnecting preserve every running process?
That depends on the server session design. We test disconnection and recovery explicitly, including any session manager used on the host.
DSDillon / 26 September 2026
