Every server you have, from one desktop app.
Terminal, security, databases, clusters, deployments and an AI sysadmin — over the SSH logins you already have. Nothing installed on any box. 10 servers free, forever.
Three rules, kept everywhere.
They are why Vigia can be trusted with root on a production box.
The picture is one server reached the only way Vigia reaches anything — and the work that outlives the window.
Everything over SSH, nothing installed.
Vigia connects with the login you already use. A reading is a command; a change is a script run as root through sudo. There is no daemon, no listening port, no agent to keep patched. What must run while Vigia is closed is a file Vigia writes on the box — a cron line, a systemd unit — never a Vigia process.
Long work runs on the box, not in the app.
An install, a restore, a cluster build starts detached on the server and survives Vigia closing. The screen shows the job's own steps with Stop; jobs that must not be left halfway keep a lightbox up. A job across several boxes reads the whole board first and shows what is in the way, with the fix, before anything writes.
Being logged in is the authentication.
No Touch ID or Windows Hello per action. Root is your saved password through sudo, sealed under your key and asked once if missing. The destructive ceremonies — uninstall, wipe — ask Touch ID or Windows Hello twice, the second time from inside Vigia so no screen can skip it.
What Vigia writes on your server
The whole list. Everything else is a command that reads and leaves nothing behind.
On every server
What every box on the map gets in Vigia, whatever it runs — over the same login, nothing installed for any of it.
Everything a server runs, from one hub.
Each package is installed from its own repository as one job you can watch, secured on the way in, and then administered on a screen of its own that appears in the rail the moment the daemon runs.
Beside it, Web on one box: nginx in, the Websites tool in the rail, and a site that is a thing — folder, owner, certificate, traffic, logs — not a config file.
Web
nginx or Apache. Sites as things: folder, owner, PHP pool, certificate, redirect, protection, traffic, files, logs. Let's Encrypt or your own certificates.
Postfix that earns a reputation: DKIM, SPF, DMARC with the records to copy and the reports read for you; Dovecot mailboxes, rspamd, jails.
Containers
Docker from docker.com with compose. Stacks, images, volumes, networks, the full run form, recreate, ready templates, and the ufw fix nobody remembers.
Virtualization
KVM guests from cloud images or ISOs, snapshots, consoles, a port published to the outside, readiness checked before a byte downloads.
Databases
MariaDB, PostgreSQL, MongoDB: explorer, users, backups, performance, security, settings, replication, sharding, cluster backups, Mirror, reports.
Cache
Redis or Valkey bound and passworded from the first minute, a keys explorer, ACL users, TLS, and Sentinel sets built by dropping servers.
VPN
A WireGuard mesh built by dropping servers in: nine boxes wired and every tunnel proved in 43 seconds. Then the ports shut to the internet from one tab, the MTU measured, a key rotated in one press.
Load balancer
HAProxy with fronts drawn from a database pair or set, repointed by the same job that moves the primary; pools of web boxes behind one address.
FTP
For the one client that insists — and SFTP already works, said first. vsftpd or ProFTPD, who may log in and where each lands, TLS, the passive range, and the firewall warning that saves the afternoon.
Pick the servers once.
Actions, Snippets, Flows, Ask Themis and Overview — the servers at a glance — all work on the same pick.
The picture is Overview on a pick of seven: one row each, a dot per check, and the one red dot that matters opened to say why.
Actions, flows and the NOCOverview, for five hundred servers.
Every picked server read at once, one row each and a dot per check — security, health, disks, backups, databases, updates, access, knocking, exposure, certificates, drift — with no tab opened for any of them. Built for five hundred servers; a click on a yellow or red dot says why.
Actions, on every box at once.
Execute one line everywhere, exactly as typed; Find out asks a curated question and groups the answers; Install puts the plumbing on the boxes that lack it; Set up runs the same change through the same door on every box.
Deployments, the first one alone.
A folder from your computer onto every server of a group — an app, a website, configuration, scripts, certificates — from a recipe you keep. Every box asked first, the first goes alone, only changed files travel, and any run is undone on the servers in one press.
Flows, drawn once.
Steps drawn once on a canvas — actions and yes/no conditions — and run on one server or on many: all at once, ten or five at a time, or one after the other, a row per server and a column per step, pausing where it needs you.
The NOC, drawn by the boxes.
Your servers as boxes and the ports they talk on, drawn by the boxes themselves: Discover reads each firewall and the live connections. Every wire is a claim, and Run Diagram proves it from the box the traffic starts at: reach, listen, allow. What is broken turns red and says why.
Your whole team, and no user table
Vigia has no users, no roles and no permissions screen — on purpose. Your servers already have those: sshd decides who gets in, sudo decides who is root, and that is the only access control there is. Vigia is the console in front of it, on every computer your team works from.
Beside it, three computers on one license: two fleets, one of them on two computers, and nothing in between but the servers themselves.
Read it at the feature level
Every screen documented: what it reads, what it writes, what it refuses to do.