Termix — Self-Hosted, Open-Source
Clientless web-based server management platform with SSH terminal, tunneling, and file editing capabilities.
License: Apache-2.0. Website: https://docs.termix.site/. Source: https://github.com/LukeGus/Termix.
Features
- SSH Terminal Access - Full-featured terminal with split-screen support (up to 4 panels) with a browser-like tab system. Includes support for customizing the terminal including common terminal themes, fonts, and other components.
- Remote Desktop Access - RDP, VNC, and Telnet support over the browser with complete customization and split screening
- SSH Tunnel Management - Create and manage SSH tunnels with automatic reconnection and health monitoring and support for -l or -r connections
- Remote File Manager - Manage files directly on remote servers with support for viewing and editing code, images, audio, and video. Upload, download, rename, delete, and move files seamlessly with sudo support.
- SSH Host Manager - Save, organize, and manage your SSH connections with tags and folders, and easily save reusable login info while being able to automate the deployment of SSH keys
- Server Stats - View CPU, memory, and disk usage along with network, uptime, system information, firewall, port monitor, on most Linux based servers
- Dashboard - View server information at a glance on your dashboard
- RBAC - Create roles and share hosts across users/roles
- User Authentication - Secure user management with admin controls and OIDC (with access control) and 2FA (TOTP) support. View active user sessions across all platforms and revoke permissions. Link your OIDC/Local accounts together.
- Database Encryption - Backend stored as encrypted SQLite database files. View docs for more.
Installation
services:
termix:
image: ghcr.io/lukegus/termix:latest
container_name: termix
restart: unless-stopped
ports:
- "8080:8080"
volumes:
- termix-data:/app/data
environment:
PORT: "8080"
depends_on:
- guacd
networks:
- termix-net
guacd:
image: guacamole/guacd:1.6.0
container_name: guacd
restart: unless-stopped
ports:
- "4822:4822"
networks:
- termix-net
volumes:
termix-data:
driver: local
networks:
termix-net:
driver: bridge
Why self-host Termix
Self-hosting gives you three things SaaS can’t: data ownership (the files live on disks you control), cost predictability (a one-time setup vs. recurring per-seat fees that grow with your household or team), and longevity (open-source means the app keeps working even if the maintainers move on, since you can pin a working version). The trade-off is that you take on the operational work of running a server, applying updates, and handling backups.
What hardware do you need
Most self-hosted apps run comfortably on modest hardware — a Raspberry Pi 4, a mini PC, a NAS with Docker support, or a small VPS is usually enough for personal or family use. CPU and RAM requirements scale with how many simultaneous users or how much data you push through Termix. Storage requirements depend on the kind of data you keep; check the README for guidance on data retention.
Last verified: 2026-04-28