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.

An encrypted key kept on the computer behind a password, Touch ID or Windows Hello behind it, and the map that opens. your key, on this computer Sealed under your password and under this machine, nowhere else. Password, then the second step Touch ID or Windows Hello, once Your map opens web-1up db-1primary db-23 updates One backup file, kept elsewhere. Restores the whole account anywhere. No login. No cloud. The key only decrypts on this computer. Nothing is sent anywhere to be checked.
/ SIGNING IN

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.

/ ON THIS COMPUTER

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.

Made hereA name and a password, typed into Vigia, and the key is written on the spot: an Ed25519 pair in a folder of its own under Vigia's data folder, its private half sealed under the password and this machine's fingerprint. No form on lockflare.com, no email, no card. LockFlare never hears that the account exists.
SealedEverything Vigia keeps is sealed. Saved logins, certificates and their keys, repository secrets, the mail server, API keys and your licenses live on your computer under your key's own signature. The file is useless to anyone who copies it.
One accountThe door opens the one account this computer keeps, with its password, and nothing else. Two people are two computers — or one backup file, restored on each.
LockLock, without leaving: Lock Vigia, in the bar at the top, blurs the console past reading and asks for the second factor to come back. The shells stay open, the jobs carry on, and nothing behind the blur can be typed into. Nothing dismisses it but the factor.
/ FOR THE DAYS SOMETHING GOES WRONG

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.

VersionsEarlier versions are kept in the folder too: one an hour for a day, then one a day for 30 days. Restore… puts any of them back as a full restore of the whole account, and how things stand now is kept as a version first.
Any computerRestore an account from a backup file, at the door of any computer, brings it all back under a new password: same key, same servers, same logins, same slots. The passphrase cannot be recovered — not by LockFlare, not by anyone.
A second computerRestore the backup file there and it is the same account — or open a fresh one, since every installation has its own ten free slots. Vigia is free on every computer and nobody counts people.
The worst dayComputer gone, no backup file. The map and the saved logins are gone with it — LockFlare has never held a copy, and that is the point. The license and every slot key you bought come back from lockflare.com/license, sent to the address of the account after a six-digit code mailed there. Vigia sends nothing; the visit is the browser's.
New passwordChanging the password: Setup → Accessing Vigia → Change Password…, the current one asked first. The key is resealed under the new one on the spot; nothing else changes and nothing leaves the computer.
Never sentWhat LockFlare could not give back: nothing operational, because nothing operational was ever sent — not a server, not a login, not a certificate. If you buy slots, LockFlare holds your email and the keys issued to it, and that is the whole of it.

A name, a password, and you are in

No account to create anywhere else. Ten servers free on this computer, forever.

Download Vigia