Sshwifty
Self-HostedOpen-source web-based SSH/Telnet client for browser-native remote access
Overview
Sshwifty is an open-source web-based SSH and Telnet client that lets users access remote servers directly from their browser—no local client installation needed. Key features include multi-session management, SCP/SFTP file transfer, customizable terminal themes, and proxy integration. It can be self-hosted via Docker (or Docker Compose) with minimal setup, making it ideal for privacy-focused remote access without relying on third-party services. The lightweight Go backend ensures fast performance, while the responsive UI works across desktop and mobile browsers.
Self-Hosting Resources
Below is a reference structure for docker-compose.yml.
⚠️ Do NOT run blindly. Replace placeholders with official values.
version: '3'
services:
sshwifty:
image: <OFFICIAL_IMAGE_NAME>:latest
container_name: sshwifty
ports:
- "8080:<APP_INTERNAL_PORT>"
volumes:
- ./data:/app/data
restart: unless-stopped Key Features
- Browser-native SSH & Telnet sessions
- SCP/SFTP file transfer support
- Multi-tab session management
- Customizable terminal appearance
Frequently Asked Questions
? Is Sshwifty hard to install?
No—Sshwifty can be deployed quickly using Docker or Docker Compose. The official repo provides a simple docker run command or compose file, requiring minimal configuration (like setting ports and persistent data volumes).
? Is it a good alternative to desktop SSH clients like PuTTY?
For browser-based access, yes—it eliminates local client setup. However, it may lack advanced features (e.g., serial port support) found in full desktop clients, so it’s better suited for quick sessions or web-preferring users.
? Is it completely free?
Yes—Sshwifty is open source under the MIT License, meaning it’s free to use, modify, and self-host without any licensing fees or hidden costs.
Top Alternatives
People Also Ask about Sshwifty
Tool Info
Pros
- ⊕ Privacy-focused (self-hosted, no third-party relays)
- ⊕ No local client installation required
Cons
- ⊖ Requires self-hosted server deployment
- ⊖ Lacks some advanced features of desktop SSH clients