vero.

VAULT ENCRYPTION · SSH IDENTITY · ACCOUNT PROTECTION

Encryption begins
on your device.

Saved hosts, authentication data, known SSH fingerprints, keychains, tags, and terminal preferences are encrypted in your vault. The sync service receives an encrypted envelope—not plaintext hosts or private keys.

A SIMPLE PROMISE

Your private world stays private.

Follow the path your information takes. Choose a step to see what happens—and what stays in your hands.

Your saved connections stay yours.

Hosts, keys, and preferences are gathered into a private vault on your device.

Your device
Optional sync
Your vault stays on your device
Step 1 of 3: Your vault
Step 1 of 3

THE SECURITY MODEL

One password signs in.
Another unlocks your vault.

The vault is encrypted on-device

Your vault is protected on your device with strong, modern encryption before anything can be synced. A fresh encryption setup protects each saved version.

Account and vault passwords are different

Your sign-in and vault password do different jobs. Only the vault password unlocks your data, and it never goes to the sync service. You can use Vero without an account.

SSH host keys are checked

Vero remembers each server’s identity. If it changes unexpectedly, you’ll see a clear warning before connecting.

Credentials use platform protection

When you choose to sync, sign-in credentials use your device’s secure storage and are refreshed safely in the background.

Found a security issue?

Contact the security team