Bad habits
Stop sharing passwords over chat or a spreadsheet
Three concrete reasons
Why a spreadsheet stops being enough
Nobody knows who saw it
A file shared over chat or in a spreadsheet doesn’t say who opened it, when, or whether someone copied it before leaving the company.
One copy, one point of failure
If that spreadsheet leaks — a misdirected email, a stolen laptop — every password is exposed at once, not one at a time.
Changing them afterward is manual work
Once a leak is found, someone has to go server by server changing each password by hand, keeping track of which ones are already done.
SHTERA replaces the spreadsheet with an encrypted vault: each server lives in a folder, with its own password, and access to each folder is granted or removed per person. Nobody sees a folder that isn’t theirs, and taking someone’s access away doesn’t require telling anyone else or rewriting a shared file.
Connecting to a server over SSH, RDP, VNC or Telnet through SHTERA never exposes the real password to the person connecting: it travels encrypted from the browser to SHTERA’s server, and from there to its destination, without ever reaching their screen. There’s nothing to accidentally copy into a chat.
If a password has already circulated and still needs changing, SHTERA can rotate it against the real server: it installs the new one, verifies it, and only then revokes the old one — without a window where neither works.
Every server’s password is encrypted in the browser before it’s saved: not even SHTERA can read it. The full mechanism is explained in Vault security.
Get started
The vault and the tree
of your servers
Free costs nothing: 1 login, 1 connection, 10 servers.