Your vault starts with you.

Items are encrypted in your browser before they sync. Your organization sets the policy but does not hold your key.

The EPV unlock screen asking for the vault passphrase
The EPV side panel showing an unlocked vault with sample logins and a secure note

How it works

Encrypted on your device. Only ciphertext travels.

The server stores what it cannot read. Your organization manages access without seeing what is inside.

  1. In your browser

    Sealed before it is stored

    Your passphrase is stretched with Argon2id, and each item is encrypted with AES-GCM before it reaches IndexedDB.

  2. In transit

    Ciphertext only

    Sync sends encrypted items and revision numbers over authenticated HTTPS. Sign-in tokens stay in memory.

  3. On the server

    Stored, never opened

    The API keeps ciphertext and wrapped key envelopes, separated per organization by PostgreSQL row-level security.

One vault for every kind of work secret.

Personal items, shared team vaults and organization policy, all in the extension.

Eight item types

Keep logins next to the secrets that usually end up in chat threads.

  • Logins
  • Secure notes
  • TOTP codes
  • API credentials
  • SSH keys
  • Certificates
  • Identities
  • Custom items
Editing a sample login in EPV, with the password masked

Shared vaults that rekey

Remove a person or group and the owner's device re-encrypts the vault under a new key.

Signed, two-person policy

Rules are Ed25519-signed and need a second administrator's approval before they publish.

Fills only when you choose

Suggestions match the exact secure site. You pick Fill, and EPV never submits the form.

Private breach checks

Only a five-character SHA-1 prefix goes to Have I Been Pwned. The password stays on your device.

A recovery code only you hold

Restore your vault on a new browser with a one-time recovery code. It is shown once and never sent to the server.

Your security team gets the controls, not the contents.

The organization console manages people and policy. Vault items stay encrypted, so running EPV never means reading them.

  • Groups, roles and invitations Invite by email and manage who can reach which vault.
  • SCIM 2.0 provisioning A focused subset for adding and deactivating members.
  • Offboarding that rotates keys Revokes devices and flags shared vaults for rekey.
  • Metadata-only audit log See who did what, never what was stored.
The EPV organization console sign-in screen
The organization console before sign-in. Its workspace opens after OIDC sign-in.

Project status

Where EPV stands today.

EPV is in active development and is not production-ready. It has not yet had an independent cryptographic review or penetration test.

Working in the codebase

  • Local encrypted vaults with user-held recovery
  • Encrypted sync with conflict protection
  • Shared vaults with owner-driven rekey
  • Signed policies with second-person approval
  • Encrypted file storage
  • SCIM subset, offboarding and audit review

Still to qualify

  • Independent cryptographic review and penetration test
  • A production identity provider and its SCIM mapping
  • Autofill on real sites and in more browsers
  • Production deployment, monitoring and backups
  • Chrome Web Store submission

Do not store production credentials in EPV until these checks are complete.