Termix
Termix is a free, open-source, self-hosted server management platform providing SSH terminals, remote desktop (RDP, VNC, Telnet) access, file transfers, and…
Platform availability
Available on 8 of 10 platforms
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
87/100 Excellent
- Maintained
- 100last commit 8 days ago
- Popular
- 8416,039 GitHub stars
- Easy to install
- 858 install platforms, install notes, Docker image
- Light to run
- 701 GB minimum RAM
- Security check
- 82no serious findings, 3 minor, CI, tests
Availability: platform listings confirmed today, links checked 2 days ago
- GitHub stars
- 16,039
- Open issues
- 37
- Last commit
- 2026-11-13
- Latest release
- v26.11.1
- License
- Apache-2.0
- Activity
- declining
Checked 5 days ago - source: GitHub (Termix-SSH/Termix)
Resources & Compatibility
Minimum requirements: 1 GB RAM, 1 CPU core(s).
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Create Termix's data volume first Create a named Docker volume called termix-data and map it to /app/data when starting the container. This keeps Termix settings and saved data safe instead of losing them when the container is recreated. source
- Set port 8080 and restart policy Use -p 8080:8080 and -e PORT=8080 so the web UI can be reached at http://your-server:8080, and add --restart unless-stopped so Termix starts again after a reboot. If the ports don't match or restart is missing, the container may run but the page won't open or you'll have to start it manually. source
- Start the Linux client without sudo If you installed the Linux executable, launch it with ./termix --no-sandbox instead of using sudo. Running it as root can create permission problems and make the app misbehave for your normal user. source
Fetched 53 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
How do I keep Termix settings and saved data when recreating the Docker container?
Create a named Docker volume called termix-data and map it to /app/data in the container. This keeps Termix settings and saved data safe instead of losing them when the container is recreated.
Which port and restart option should I use for the Termix Docker web UI?
Use -p 8080:8080 and -e PORT=8080 so the web UI is reachable at port 8080, and add --restart unless-stopped. If the ports do not match or the restart flag is missing, the page may not open or the container may not start after a reboot.
Should I expose Termix directly to the internet without a VPN?
The project recommends securely tunneling the connection to Termix through a VPN. It is in the very early stages of development and may have bugs, data loss, and unexplainable issues.
How should I start the Termix Linux client to avoid permission problems?
Launch the installed Linux executable with ./termix --no-sandbox instead of using sudo. Running it as root can create permission problems and make the app misbehave for your normal user.
Answers sourced from docs.termix.site, docs.termix.site, forums.unraid.net
Community
- Reddit (reddit)
- I fell into a Terminix contract trap and got stuck for a year (reddit)
- Just sharing why you probably shouldn't use terminix for ... - Reddit (reddit)
- Termix Terminal Access Manager - Termius Alternative (forum)
- Selfhosted alternative for Termius : r/selfhosted - Reddit (reddit)
Collected 48 days ago - public community threads