There is no login. Your key is who you are.
An encrypted key file, whose private half only opens on your own computer, is what unlocks Vigia. It is made the first time you open the app — a name, a password, nothing else — and sealed under that password: not checked against anything, but what the key is encrypted under, so the file is noise to anyone who copies it or takes the computer. Touch ID or Windows Hello stands behind it. Nothing is sent anywhere to be checked, so there is no account to phish and no cloud to go down.
The door, in order.
Nothing typed but the password, and nothing sent anywhere to be checked: the key opening is the check.
The password
Twelve characters at least — three or four words you will remember are easier to type and harder to guess than one clever word. It opens the key, and the key opening is the check: no server, no activation, nothing typed but the password. Five wrong answers and the account stops answering for fifteen minutes.
Touch ID or Windows Hello
Asked once the key has opened, never before. A Mac with no sensor, or a laptop with its lid closed, falls back to the password; a Windows computer with Hello not set up does the same — and the screen always says which. Setup → Accessing Vigia can leave the sensor out: the password alone opens Vigia, and is asked again before the actions that are hard to undo.
The map
Vigia opens on your servers. Being in is the authentication: no Touch ID or Windows Hello per action. Root on a box is your saved password through sudo, sealed under your key.
Made here, sealed here, and nowhere else.
The account, everything it keeps and the one way back in all live on this computer, under your key.
The encrypted backup, kept off this computer.
One page in Setup that says how the backup stands, its buttons on the same line — and one file, kept off this computer, that is the whole account.
Setup → Encrypted Backup → Turn On… asks two things: a passphrase of your own, and a folder that leaves this computer — a USB drive, a NAS share, a folder Dropbox, iCloud Drive or OneDrive keeps in sync. Vigia's own folder is refused: a copy that dies with the disk insures against nothing. From then on everything Vigia keeps is sealed with AES-256 under that passphrase — the servers and groups, snippets, flows, diagrams, the audit ledger, the licenses, the saved logins with the SSH key files they open with, the certificates and repositories, the database mirrors, the mail server, the startup board and the buckets — and rewritten within a minute of any change, beside the account here and in that folder. Command history stays on this computer.
A name, a password, and you are in
No account to create anywhere else. Ten servers free on this computer, forever.