Private vaults
Keep personal information separate. An administrator is not meant to gain automatic cryptographic access to every private vault.
127Vaults is being built for people who want practical control over their password infrastructure, while keeping private vaults across devices.
Each authorized device is designed to keep an encrypted local copy of vaults it can access. The server coordinates encrypted changes between devices. When the server is temporarily unavailable, already synchronized vault contents should remain available on the device.
Vault data is designed to be encrypted on the client before it reaches the server. The server is not intended to hold plaintext passwords or the secrets required to decrypt a vault.
Keep personal information separate. An administrator is not meant to gain automatic cryptographic access to every private vault.
Keep separate vaults for work, personal use, or other collections without granting other users access.
Every client device is registered and has its own cryptographic identity. The server knows authorized device identities, not their private keys.
127Vaults aims to support user management and private vault use without the complexity of a traditional enterprise password manager. Recovery is intended to be explicit and user designated, rather than blanket administrator access to private vaults.
The same core product is intended for Personal Self-Hosted, Commercial Self-Hosted, and 127Vaults Cloud.
Read the security approachList vaults and items, and check the client status from the CLI.
Switch commands to see the CLI response format.
$ 127vaults vault list
[
{ "name": "Personal", "code": "V-91E900D1C9" },
{ "name": "Work", "code": "V-95840506C7" }
]Compare self-hosting and managed Cloud before choosing a plan.