01
Connect with confidence.
Native SSH with host-key verification, authentication paths, PTY lifecycle, timeouts, cancellation, reconnect state, and errors you can actually act on.
Connection model ↗free · open source · rust-first
Every machine.
One control room.
A free, open-source MobaXterm alternative for the remote workday — SSH terminals, files, tunnels, diagnostics, and the context between them.
FREE and open source
~89% roadmap evidenced
edge-prod-01 ×staging-files ×local-shell ×+
MobaRust session · host key verified
ops@edge-prod-01:~$ systemctl status api
● api.service — Operations API
Loaded: loaded · Active: active (running)
Tasks: 42 · Memory: 284.6M · Uptime: 14d
ops@edge-prod-01:~$
connectedUTF-8scrollback 2,000
REMOTE FILES3 items
deploydirectory
docker-compose.yml4.2 KB
release-notes.md12.8 KB
Local terminal
A native shell, kept close to the remote work.
➜ pwd /Users/operator/projects
➜ cargo xtask check passed
TRANSFERrelease.tar.gz84%
TUNNELlocalhost:5432
SSH✳SFTP✳SCP✳PTY✳TUNNELS✳DIAGNOSTICS✳REMOTE OPS✳SSH✳SFTP✳SCP✳PTY✳TUNNELS✳DIAGNOSTICS✳
the open alternative↗
Same useful idea.
Open by default.
MobaXterm offers a free Home Edition and a paid Professional edition. MobaRust takes the open alternative path: free to use, open source to inspect, and built in the open for the workflows that matter.
MobaRustFree + open sourceRust-first · transparent development
Built forSSH-first operatorsDevOps · sysadmin · cloud · homelab
01 / the daily loop
From first connect
to last command.
The hard part of remote work is rarely the protocol. It is the context switching, the hidden state, and the tiny moments where an unsafe action becomes too easy. MobaRust brings the all-in-one workflow into a free, transparent desktop workspace.
02
Move work, not tabs.
SFTP and SCP primitives, recursive transfers, bounded progress, conflict-aware remote editing, and a file surface that stays beside the shell.
File operations ↗03
Operate with context.
Tunnels, snippets, visible macros, selected broadcast targets, focused diagnostics, and optional remote monitoring for the moments between commands.
Operator tools ↗02 / the boundary
Powerful under the hood.
Quiet by default.
Rust owns the sensitive edges: protocol state, cancellation, local storage, file policy, and credential boundaries. The React surface gets narrow, typed capabilities — never a blank cheque.
Read the security notes ↗⌑TRUST BOUNDARY enforced
FRONTENDTyped commandsReact / TypeScript
NATIVE COREProtocol stateRust / Tauri
SECRET MATERIALReferenced, not copiedVault boundary
personal credentials never required for testsloopback fixtures only
03 / the honest frontier
Ambition with
receipts.
There is a lot here. There is also more to prove. The remaining work is visible, named, and deliberately kept separate from the strong core.
EXPERIMENT↗
RDP / VNC
Controlled helper experiments and loopback fixtures exist. Cross-platform interoperability, Windows evidence, audio, gateway, and production packaging remain open.
MATRIX↗
Every desktop, every edge
Windows, Linux, macOS, WSL, serial hardware, multi-monitor, clipboard, and clean-install evidence need real environment coverage.
RELEASE↗
Signed distribution
Portable packaging, signing, notarization, and a reproducible cross-platform release matrix are part of the final hardening pass.
04 / get close to the metal
Try the
workbench.
Clone the repository, run the isolated checks, and open the desktop shell. The validation path uses local state and loopback fixtures — it does not need your personal SSH files.
See the safe testing policy ↗TERMINAL
# clone the control room
git clone https://github.com/OthmaneBlial/MobaRust.git
cd MobaRust
# isolated validation
cargo xtask check
# launch the desktop shell
cargo tauri dev --manifest-path apps/desktop/src-tauri/Cargo.tomlCopies commands only · nothing is executed
Built in the open