Most SSH tools solve the connection problem.
I wanted to solve the workflow around the connection.
When I manage servers, the work rarely stops at "open a terminal." I usually need to connect over SSH, move files with SFTP, check whether the server is under pressure, open or edit remote files, recover failed transfers, and sometimes set up port forwarding. Those actions often live in separate tools or separate windows, which makes simple server work feel more scattered than it needs to be.
That is why I started building TermDock.
TermDock is an open-source, local-first SSH + SFTP desktop workspace for developers and operators. It is built with Electron, React, TypeScript, xterm.js, and ssh2, and it currently focuses on macOS and Windows.
The goal is not to become the biggest terminal app. There are already mature tools in that space. The goal is to make everyday server operations safer and more recoverable for individual developers, small teams, and people who frequently manage remote machines.
What TermDock Does
TermDock brings the common server workflow into one desktop app:
- Multi-tab SSH terminal
- Session management
- SFTP file browser
- Upload and download queues
- Retry Center for failed transfers
- Server health panel
- Local, Remote, and Dynamic SOCKS5 port forwarding
- Dangerous-command guardrails
- Diagnostics and bug report export
- English and Simplified Chinese interface
The app is local-first. It does not require a cloud account to manage servers. Session data and diagnostics are stored locally, and diagnostic bundles are generated locally so users can review them before sharing.
Why "Safer" SSH?
The most interesting part of TermDock is not simply that it connects to servers. The more useful idea is that server work should have guardrails.
For example, TermDock has dangerous-command protection. Risky terminal writes can be intercepted before they reach the server, including commands coming from keyboard input, paste, command history, snippets, quick profiles, and startup commands.
This is not meant to replace good operational discipline. It is meant to catch the kind of mistake that happens when you are tired, moving quickly, or working across multiple environments.
The same thinking applies to file transfer recovery. If a batch upload or download fails, TermDock keeps failed transfer history in the Retry Center so the work can be reviewed and retried instead of disappearing into a terminal scrollback or a one-off dialog.
Why Combine SSH and SFTP?
SSH and SFTP are often part of the same job.
You connect to a server, inspect a file, upload a build artifact, download logs, edit a config, check disk usage, restart something, then maybe set up a port forward. Splitting that across multiple tools is workable, but it adds friction.
TermDock treats SSH and SFTP as one workspace:
- The terminal remains the main stage.
- SFTP behaves like a file explorer rail.
- Server health and command history live in an inspector rail.
- Transfers live in a bottom panel.
The UI direction is closer to a compact code editor workbench than a card-heavy operations dashboard.
Built-In Server Health
TermDock includes a server health panel so you can inspect basic runtime state without leaving the SSH workspace.
It can show CPU, memory, disk, network, load, uptime, processes, and failed services. The intent is not to replace a full monitoring platform. It is a lightweight context view for the server you are already working on.
For many small-team or personal projects, that context is enough to answer immediate questions:
- Is the server under CPU pressure?
- Is memory tight?
- Is disk usage high?
- Are there failed services?
- Which processes are using the most resources?
Port Forwarding Without Rewriting Commands Every Time
TermDock also includes a port forwarding manager for:
- Local forwards
- Remote forwards
- Dynamic SOCKS5 forwards
The idea is to reduce repeated manual ssh -L, ssh -R, and ssh -D setup when you use the same forwarding patterns often. Saved presets and runtime status make it easier to see what is active.
What Is Still Early
TermDock is still early, and I want to be transparent about that.
Current limitations include:
- No in-app auto-update yet
- Persistence is still JSON-based while a SQLite migration is planned
- Public-trust signing and notarization evidence is still being improved
- The project is currently focused on macOS and Windows
Because this is an SSH/SFTP app, trust matters. I added a security document to explain local storage, credential handling, diagnostic exports, and current limits. I would rather be explicit about what is finished and what is not.
What I Am Looking For
I am looking for early feedback from people who regularly manage servers.
I would especially like to know:
- What SSH/SFTP client do you use today?
- Which part of the workflow still feels annoying?
- Would dangerous-command guardrails be useful or get in your way?
- Do you prefer SSH and SFTP in one workspace, or separate tools?
- What would make you trust a new SSH desktop app?
- Which platform/package format matters most to you?
The project is open source, and the releases are available on GitHub:
https://github.com/gongteng0215/TermDock
If you try it, please open an issue with your platform, TermDock version, downloaded asset, and sanitized reproduction details. Please do not post real hosts, usernames, private keys, passwords, tokens, or full logs publicly.
Closing
TermDock is not trying to be "another SSH client."
The direction is a safer, local-first server operations workspace for developers and small teams: connect to the server, move files, inspect health, manage port forwards, avoid risky mistakes, and recover when transfers fail.
If that workflow matches your day-to-day server work, I would love to hear what feels useful and what still feels missing.
Top comments (0)