WeTTY
Self-HostedWeb-based terminal emulator for browser access to your shell
Overview
WeTTY is a lightweight, open-source web terminal emulator that connects your local or remote shell to a browser interface. It supports secure SSH access, HTTPS encryption, and integrates with auth systems like OAuth2/LDAP. Deployable via Docker (one-command setup) or npm, it works across modern browsers and preserves core terminal functionality (colors, shortcuts). Ideal for remote teams needing shared shell access or users wanting browser-based terminal access without native clients.
Self-Hosting Resources
Below is a reference structure for docker-compose.yml.
⚠️ Do NOT run blindly. Replace placeholders with official values.
version: '3'
services:
wetty:
image: <OFFICIAL_IMAGE_NAME>:latest
container_name: wetty
ports:
- "8080:<APP_INTERNAL_PORT>"
volumes:
- ./data:/app/data
restart: unless-stopped Key Features
- Web-based terminal access from any modern browser
- Secure SSH connections with HTTPS encryption support
- Easy deployment via Docker or npm packages
- Authentication integration (OAuth2, LDAP, and basic auth)
Frequently Asked Questions
? Is WeTTY hard to install?
WeTTY is easy to set up for basic use—you can deploy it with a single Docker command or install via npm. Advanced setups (like HTTPS or OAuth2 integration) require basic server configuration knowledge but are well-documented.
? Is WeTTY a good alternative to native terminal clients?
WeTTY shines for remote access scenarios (e.g., accessing a server from a browser without a native client). For local use, native clients may offer more advanced features, but WeTTY is a great choice for web-based terminal needs.
? Is WeTTY completely free?
Yes! WeTTY is licensed under the MIT License, so it’s completely free to use, modify, and self-host. There are no hidden costs or restrictions on its usage.
Top Alternatives
People Also Ask about WeTTY
Tool Info
Pros
- ⊕ Self-hosted for full privacy and control over data
- ⊕ No recurring subscription fees (100% open source)
- ⊕ Cross-browser compatibility (Chrome, Firefox, Safari)
- ⊕ Lightweight and low resource consumption
Cons
- ⊖ Requires a server to host the application
- ⊖ Technical setup needed for advanced auth configurations
- ⊖ Relies on stable network connection for uninterrupted use
- ⊖ Lacks some advanced features of native terminal clients (e.g., split panes)