ShellMate is a modern SSH workspace with native terminal sessions, permission-aware team access, server-managed encrypted credentials, and auditable connection controls.
ShellMate started from a frustration I ran into almost every day. Connecting to servers via SSH was easy — everything around it wasn't.
Credentials were in password managers, notes were scattered across documents, access details lived in chat messages, and onboarding teammates was often a manual process. Finding the right server sometimes took longer than connecting to it.
So I built ShellMate, a desktop SSH workspace for developers, sysadmins, and DevOps teams. It brings hosts, credentials, terminal sessions, permissions, team collaboration, and access management into one place.
A quick note on security: I previously described the credential vault as "zero-knowledge." That wasn't accurate. ShellMate currently uses server-managed encryption and short-lived, session-bound access grants. The server remains part of the trust boundary, so it is not yet a true zero-knowledge or end-to-end encrypted system.
What ShellMate offers today:
🔐 Encrypted credential storage with session-bound access ⚡ Fast desktop SSH experience 🛡️ Permission-aware host access and short-lived grants 👥 Team workspaces, host groups, and RBAC 🖥️ Organized host and infrastructure management 📋 Activity logs and security events 🔑 SSH certificate support for enrolled hosts
I'm actively working toward a stronger end-to-end encrypted architecture while keeping the experience simple and fast.
I'd love your feedback:
👉 What's the biggest pain point in your current SSH workflow? 👉 What security controls would you expect from a tool like this? 👉 What would make you switch from your current solution?
Thanks for checking out ShellMate and supporting indie makers!
Are there any compliance stuff that proves that shellmte is safe? EG. Soc2, Hippa
ShellMate's import/onboarding story is the piece I'd test first, especially if it can pull an existing ~/.ssh/config into a cleaner vault without breaking aliases. For teams, the zero-knowledge vault and workspace model make sense, but the practical tradeoff is migration friction. Do you preserve ProxyJump, per-host identity files, and agent-forwarding settings when importing existing SSH config?
nice product!
does it work with completely air gapped environments with no internet access like isolated DBs?
The zero-knowledge vault for SSH credentials is architecturally sound. Most SSH managers store secrets in a way that the vendor could access them, so client-side encryption is the right call. We've dealt with credential sprawl ourselves: private keys shared over Slack is a scary common default. How does cross-device sync work under zero-knowledge constraints? Is the vault key derived from a passphrase with the encrypted blob synced, or something different?
SSH credential sprawl is genuinely painful when managing multiple environments across a team. The team-based access model makes sense: keeping prod keys isolated from staging is something everyone knows they should do but it's rarely implemented cleanly. How does key rotation work? Do you push updates to all hosts automatically, or does each server need a manual sync?
Clean take on an SSH client, and the zero-knowledge encrypted vault is reassuring for credentials. I like that sync is built in. For a solo dev not on a team, does the vault still sync across my own Macs without setting up any workspace stuff?
About ShellMate on Product Hunt
“Manage SSH servers, credentials, and teams in one place”
ShellMate launched on Product Hunt on June 12th, 2026 and earned 117 upvotes and 14 comments, placing #8 on the daily leaderboard. ShellMate is a modern SSH workspace with native terminal sessions, permission-aware team access, server-managed encrypted credentials, and auditable connection controls.
ShellMate was featured in Productivity (655.7k followers), Privacy (11.2k followers) and Developer Tools (515.5k followers) on Product Hunt. Together, these topics include over 227.5k products, making this a competitive space to launch in.
Who hunted ShellMate?
ShellMate was hunted by Arab. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how ShellMate stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Arab
Hey Product Hunt! 👋
ShellMate started from a frustration I ran into almost every day. Connecting to servers via SSH was easy — everything around it wasn't.
Credentials were in password managers, notes were scattered across documents, access details lived in chat messages, and onboarding teammates was often a manual process. Finding the right server sometimes took longer than connecting to it.
So I built ShellMate, a desktop SSH workspace for developers, sysadmins, and DevOps teams. It brings hosts, credentials, terminal sessions, permissions, team collaboration, and access management into one place.
A quick note on security: I previously described the credential vault as "zero-knowledge." That wasn't accurate. ShellMate currently uses server-managed encryption and short-lived, session-bound access grants. The server remains part of the trust boundary, so it is not yet a true zero-knowledge or end-to-end encrypted system.
What ShellMate offers today:
🔐 Encrypted credential storage with session-bound access
⚡ Fast desktop SSH experience
🛡️ Permission-aware host access and short-lived grants
👥 Team workspaces, host groups, and RBAC
🖥️ Organized host and infrastructure management
📋 Activity logs and security events
🔑 SSH certificate support for enrolled hosts
I'm actively working toward a stronger end-to-end encrypted architecture while keeping the experience simple and fast.
I'd love your feedback:
👉 What's the biggest pain point in your current SSH workflow?
👉 What security controls would you expect from a tool like this?
👉 What would make you switch from your current solution?
Thanks for checking out ShellMate and supporting indie makers!