A full SSH console before you install a single LockFlare thing.

Every group is a card and every server a row: the dot, the name and state, the address, what it runs, and what it is waiting on — pending updates, a restart. Search narrows the map by name, address or note; Find a server in the bar at the top (⌘P, or Ctrl+Shift+P) opens and connects any one of them from wherever you are. A group has Connect, Check for updates and Update all on its head.

• Colours — five, and none — a thin line on the row and under the tab, and the word in the server's head, so nobody types into the wrong box. Red is what people give production.
• Bastions: a server reached through another one on the map, with the bastion's own saved login. One exposed box lets the rest close port 22 to the world.
• Export: the map, or the part of it you tick, as a JSON file — names, addresses, logins, key paths; never a password or a passphrase.

A real terminal in the window: your credentials, sshd decides, sshd logs. Pages of shells, up to four split on one page, and a shell on this computer beside them. Splitting or resizing a pane never reconnects the shell. Broadcast types one command, or one key like Ctrl-C, into every open shell at once.

• Logins by password, key file — your keys in ~/.ssh offered by name — or the SSH agent. Every login is saved, sealed under your key, because a server nothing unattended can open is a server automation cannot touch. Forget removes it by name.
• Resume: a lid closed or a VPN that fell over does not end the pane. Vigia redials up to twenty times and, on a server kept alive with tmux, lands in the same shell with the command still running.
• Per server: keep alive in tmux, record every session as asciicast (output only, never what is typed), or a plain shell with no history hooks.
• Host keys are never auto-accepted. A multi-line paste arrives as text and waits for Return.

Every command typed into a Vigia shell is filed on your computer per server: the whole line as the shell ran it, its exit status, the folder, when, and how long it took. Searchable across one server or all of them, with Run again to type it back into the open shell. Nothing is guessed from keystrokes — the shell itself reports it — and nothing is written on the box to make it work. A root shell reached with sudo -i is a different shell and is deliberately not filed.

Mark a server and every session to it is recorded as a timestamped asciicast — output only, so a password typed at a prompt is never in the file. Recordings play back inside Vigia at 1×, 2× or 4×, with the terminal resizing exactly as it did at the time.

Local, remote and proxy forwards riding the login Vigia already has, started when the shell is up or on connect. Vigia lists what a tunnel could reach on the box — the database on loopback, the admin panel on 127.0.0.1, a docker port on localhost — and what people usually tunnel to, with their ports. A tunnel bound to the office Wi-Fi can announce itself by Bonjour so a coworker's Vigia sees it under Shared on your network.

The HTTP tunnel is one switch: your browsers leave the internet from the server, its address, its network, its DNS. The one way to see a DNS change that landed everywhere but on that box — and a name can be looked up on the box and on this computer side by side, without opening a browser at all. When a VPN owns your route, Vigia opens a browser window through the tunnel instead.

The server as one pane — beside this computer, other servers and your repositories, up to six side by side — over the same login, nothing installed. Upload and download through your system's own dialogs. Reads fall back to root on their own and say so; changes as root go through your saved password. Right-click a text file and it opens in a code editor beside the pane; saving writes the bytes back with the mode and owner the file had.

Permissions in the order a person asks: what can I do here, who else and what — the classic bits and the ACL as one list — and who owns it. The bucket collects references to files on any server and drops them on another; Vigia relays box to box through your computer.

• Execute: one line, every server, the answers side by side, run exactly as typed. The lines an admin types at a fleet most mornings — uptime, disk, memory, failed services, listening ports, who is on, restart needed — plus your own snippets, each filling the box so what goes out is always in front of you.
• Find out: one of nearly three hundred curated questions, answered as one value per server through its own parser and grouped by answer, biggest group first. Six distinct CPUs is the finding, not thirty-six rows.
• Install: Fail2Ban, ufw, firewalld, CrowdSec, ModSecurity, unattended-upgrades, auditd, AIDE, nginx, Apache, Caddy, PHP-FPM, certbot, ProFTPD, chrony and the rest, on the boxes that lack them.
• Set up: add a user, sudo, keys, lock, delete, a group, a folder grant, open or close a port, the firewall on, Fail2Ban, sshd hardening, a service, automatic updates, timezone, NTP — the same door the server's own tab uses, on every box, a row per server saying what happened.

Steps drawn once on a canvas, run on many: update and upgrade, install packages, create a user, set up SSH for your IP, harden SSH, the firewall, Fail2Ban, kernel hardening, automatic updates, a restart with its way back, a custom script — and conditions that branch: is the package there, is the port listening, does the file exist. Every flow is your own, drawn for the boxes you know.

Run on Servers takes the servers from the pick and asks the flow's questions once, then runs it All at Once, 10 at a Time, 5 at a Time or One at a Time — one server first if you want, the rest starting only if it finishes cleanly, and one failure stopping the rest if you tick it. Each server runs the flow as root on its own session, and the run is a table: a row per server, a column per step, and End. A host key to trust, a sudo password or a failed step — retry, skip, stop — waits on its row, and Watch opens that server's run with the flow lighting up node by node. Quitting Vigia or closing the session while a flow runs asks first.

Your map drawn as boxes with the ports they talk on. A wire says MDB-1 talks to MDB-2 on 27017. That is a claim, and Run Diagram proves it from the box the traffic starts at: did the source open the connection, does something listen on the destination on an address the source dials, does the destination's firewall let the source in. Green, amber or red, with the failing fact in words. Nothing is checked from your computer, which knows nothing about whether two servers can reach each other.

And you do not have to draw it: Discover reads every box's firewall and its live connections and draws the wires itself — 187 of them across ten real servers.