MistTerm in 3 minutes

Download MistTerm, connect a server, run a built-in example command, then optionally create a free team for certificates and audit. MistDocs is the runbook companion.

Download free Create a free account → Open MistDocs (app) Three time-saving ways to use MistTerm Community

3-minute quick start

Experience a MistTerm differentiator first, then turn on team features if you need them.

  1. Install MistTerm from the download page (fresh installs include example commands and a one-time guide).
  2. Add an SSH server and connect; run a built-in example command (disk/memory) from the library.
  3. Optional: create a free team for certificates and command records; try AI multi-host “check disk on all servers” (no API key).
  4. Optional: write the first runbook in MistDocs, or use port forwarding in the UI / mist fwd.
Command audit covers snippets, history, AI, and batch runs — not hand-typed PTY input yet. Still use roles for production access.

What it looks like

Real screenshots of the three products. The servers and data come from a demo setup.

MistTerm (terminal)

Left: the server list in the MistTerm desktop app. Right: mist ls in a terminal lists the same 5 servers, and mist exec connects to one of them.
Left: the server list in the desktop app. Right: the mist command-line tool uses the same list.
MistTerm desktop app: all 5 demo servers connected in the list on the left, a terminal session on staging-web in the middle, and the AI assistant on the right checking memory on every server and listing the results per server
The AI assistant checks memory on 5 servers at once. Results are listed per server, and high ones are marked red.
MistTerm saved-commands panel with four commands (memory, disk usage, uptime, listening ports); the two just used show how many times they ran
Save common commands and run one with a click. It also counts how often each one is used.
MistTerm's SFTP panel: files on your computer at the top, files in the logs folder on the server staging-web at the bottom
Browse the server's files inside the app. No separate tool needed to upload or download.

MistDocs (team docs)

Document library
Open a runbook from its folder and see who wrote it and which tags it has.
See who's editing
When two people have a document open, you can see the other cursor and how many people are online.
Versions
See each saved version and who saved it.
Sheet
Use formulas in a sheet to calculate amounts and totals.

More MistDocs screenshots →

Console (team admin)

These are the signed-in admin pages. The console is where you see your teams and saved commands. The admin panel shows the totals and the server list.

Admin panel with counts for users, teams, saved commands, and servers, plus shortcuts including login certificates
The admin panel opens on this page: how many users, teams, saved commands, and servers there are, and shortcuts on the right, including login certificates.
Server list in the admin panel, including demo hosts 演示-bastion, 演示-staging-db, and 演示-staging-web
The server page lists each machine's name, address, and status. The demo machines are 演示:bastion, 演示:staging-db, and 演示:staging-web.
Open Console →

Install MistTerm

MistTerm is the desktop terminal for Windows, macOS, and Linux. Download the latest release, then sign in with your MistLab account.

Current client release: MistTerm v1.2.10 · download page.

Download the latest release: https://mistlab.dev/download.html

Add your first server

  1. Open the server manager and choose Add server.
  2. Enter the hostname, port, and SSH username.
  3. Log in with an existing SSH key, or have your team issue a short-lived login certificate.
  4. On first connection, check the server fingerprint (it confirms you reached the right machine).

MistTerm CLI (mist)

If you prefer typing commands, use the mist command-line tool that comes with MistTerm. It shares saved servers, jump hosts (servers you log in through), and credentials with the desktop app, so you don't sign in again.

# Connect to a saved session or host mist ssh prod-web-01 # Run command across a server group with parallel execution mist exec --group prod --parallel 4 "uptime" # Port forwarding: Local, Remote, or Dynamic SOCKS5 proxy mist fwd bastion -L 13306:internal-db:3306 -D 1080 # SFTP remote directory listing and file transfer mist rls prod-web-01:/var/log/nginx/ mist put ./dist/app.tar.gz prod-web-01:/opt/app/ # Run team snippet templates with variables mist frag run deploy-service prod-web-01 -v env=prod -v ver=v1.2.0 # Import ~/.ssh/config hosts into MistTerm mist import-ssh-config --dry-run
Full mist command-line guide →

Set up your team: roles, shared commands, and runbooks

Manage member access and ops docs in one place, the console at mistlab.dev.

Console team page showing Acme Ops Demo with an ADMIN badge and manage-members button
The console's team page. This account is in the admin and myteam teams. Each card has a button to manage members.
Console saved-commands page for Acme Ops Demo, listing Rotate application logs and Tail service logs
The console's saved-commands page. Team commands are grouped by category. You can search, edit one, or turn it into a document.
  • Assign admin, editor, or viewer roles to each member.
  • Save frequently used commands to the team library after someone has checked them.
  • Write deployment and incident runbooks in MistDocs.
  • Share a document externally with a time-limited or password-protected link.
Open setup guide →Sign in to Help Center

Review command records

Each command record shows the command, who ran it, the server, and the time. Risky commands get a tag, and that is all the tag does. By default commands are only recorded and nothing is blocked; blocking and confirm-before-run come only after a team admin turns on those rules (Team plan). To suggest a safe alternative when a command is blocked, first save your approved commands to the library.

Command audit is there to catch slips and remind new teammates. It won't stop someone who sets out to get around it; to guard against people, use the server agent together with account permissions. MistTerm checks commands sent from saved commands, command history, the AI ops assistant and batch runs; commands typed straight into the terminal aren't checked yet. On servers, only commands root runs directly with ssh host "command" are checked and recorded; commands typed after logging in over ssh are neither checked nor recorded, and if the team server can't be reached the command runs unchecked. What it can and can't do

  1. Open Audit from the console navigation.
  2. Choose a team and time range.
  3. Filter logs by action or search for a command.
  4. Check the risk tag on the record. A "confirm" rule shows a dialog in MistTerm so the person running the command confirms it themselves; there is no flow yet that sends a command to someone else for approval before it runs.
Open audit dashboard →

Three time-saving ways to use MistTerm

One host list for the GUI and the mist CLI, a confirmed read-only pass across machines, and real command snippets. Commands are only recorded by default; blocking is opt-in.

Read story Series index

What's next

Once the basics work: set up SSH certificate signing (temporary certificates instead of long-lived keys), write a deployment runbook, and use a webhook to notify your systems about important command records.

View source on GitHub →