How to actually use it.
Everything from creating your first vault to running SEES on your own infrastructure.
No email. Just a Vault ID and a passphrase.
Choose a Vault ID (a name that locates your vault — not a username or identity) and a passphrase. Your browser derives an AES-256 key from the passphrase locally; the passphrase itself is never sent anywhere.
Unlock with your passphrase. Add 2FA if you want a second layer.
Enter your Vault ID and passphrase to unlock. From Vault Settings you can turn on authenticator-app 2FA, which adds a second local check after your passphrase. It is a local unlock step, not account recovery — losing your passphrase still locks you out.
Share a note without handing over your vault key.
Sharing generates a link with its own decryption key stored in the URL fragment, the part of a URL browsers never transmit to a server. You can optionally lock a share with its own password, set an expiry, or revoke it early from Vault Settings.
The full source is public. Run your own instance.
SEES is MIT-licensed and needs no database — just an S3-compatible storage bucket (Storj or otherwise). The README covers required environment variables, local setup, and deployment.
Read the self-hosting guide on GitHub