Production terminal workspace
Termix brings SSH, SFTP, port forwarding and serial access into one disciplined desktop client.
Termix is built for operators and developers who need direct host access, reusable command flows, encrypted storage and multiple profile backends without turning day-to-day terminal work into a SaaS dependency.
Latest stable desktop build is being resolved automatically.
100% free in production
Apache 2.0
Local / Firebase / QMM
$ ssh prod-edge
termix: connected with saved key
termix: forward 5432 -> db.internal:5432
termix: SFTP mounted at /var/www/app
ready for deploy tasks
Jump into repeated production targets without rebuilding the connection every time.
Move, rename, edit and inspect remote files in the same workspace.
Keep database and internal service tunnels visible instead of hidden in shell history.
Pinned stable build
Termix covers remote servers, local sessions and device-level serial connections in one UI.
Designed as a full client, not a thin marketing layer around a restricted feature set.
Operational scope
From direct SSH sessions to file transfer and tunnel management.
Termix is not just a terminal tab. The product already includes dedicated modules for remote files, forwarding, snippets, key material and host management.
Profile architecture
Local JSON, Firebase and QMM-backed account models.
The application already supports multiple profile types, profile switching and optional sync workflows instead of locking every user into one storage model.
Trust model
Encrypted secrets, known-host verification and an audited dependency path.
Saved credentials are encrypted, host fingerprints are persisted, and the release workflow includes dependency tracking and security audit steps before builds are published.
Core capabilities
Each major workflow in Termix deserves its own place in the product story.
The application already covers a broad operational surface. The site now highlights the major workflows separately instead of compressing them into generic claims.
Remote file work without leaving the client.
Termix ships with a dedicated SFTP manager for browsing, reading, writing, renaming, copying and creating files and folders. That means remote maintenance stays inside the same workspace as the shell session.
Port forwarding with explicit state and conflict checks.
Local-to-remote and remote-to-local tunnels can be stored, started, stopped and validated from a dedicated module instead of disappearing into shell history.
Serial / COM access alongside regular shell work.
COM and tty ports can be discovered directly from the app, opened with a selected baud rate and managed next to SSH and local terminal sessions.
SSH, local shell and known-host handling in one place.
Saved hosts, native local terminal sessions and known-host verification are part of the same application model, which makes repeated operational work more consistent.
Reusable command snippets with host-aware execution.
Operational commands can be stored manually or imported from JSON URLs, then executed against a selected VDS or SSH target from the snippet workflow itself.
Encrypted storage for passwords, API keys and profile secrets.
Saved credentials are encrypted, portable keys are supported and known-host fingerprints are persisted so the client carries its own trust and storage model instead of leaving that responsibility to ad hoc files.
Multiple account systems for local, cloud-backed and self-hosted workflows.
Profiles can be created as local JSON, Firebase-backed or QMM-backed accounts. The app can switch between them, sync profile data when required and keep the storage model aligned with the environment.
Open-source codebase with dependency and audit controls.
Apache 2.0 licensing, automated dependency updates and audit checks in the build pipeline support a cleaner maintenance story than a closed binary with opaque release practices.
Account models
Three storage models, depending on how you want to operate.
Termix does not force every user into the same profile architecture. Local-only, Firebase-backed and QMM-backed accounts are all first-class options.
Fast, local and direct.
Profiles, hosts, snippets, tags and settings can stay as local JSON data for users who want simple, self-contained storage on the device.
Cloud-backed profile sync.
Firebase-backed profiles are available for teams or users who want synchronized profile data without changing the rest of the desktop workflow.
Self-hosted host sync with encrypted secrets.
QMM-backed accounts support encrypted API key storage and optional self-signed certificate handling for environments that prefer self-hosted infrastructure.
Desktop builds
Stable builds for Windows, Linux and macOS.
The latest desktop installers are resolved automatically, and the matching operating system gets priority on the current device.