Apr 18, 2026

Share your environments securely using envault.

secure sharing next.js never lose to your competition encrypted sharing secure communication vibe check

Envault is a zero-knowledge secret-sharing app for environment variables: you paste your .env values, they are encrypted locally in your browser with modern cryptography, and you share a one-time link plus passphrase separately. The server only stores encrypted envelopes, never plaintext secrets or passphrases, so recipients can decrypt securely on their side while preserving end-to-end confidentiality.

Envault is designed for one thing: sharing sensitive environment variables safely, without ever exposing plaintext secrets to the server.
You encrypt in your browser, share a one-time link, and the recipient decrypts locally with the passphrase.

  1. Prepare your secrets
    Gather the .env values you want to share, such as API keys, tokens, and service credentials.

  2. Encrypt locally
    Open Envault, paste your variables, and generate or enter a strong passphrase.
    Encryption happens entirely in your browser before anything is stored.

  3. Create the envelope
    Seal the payload to generate:

    • a one-time share link
    • an envelope ID
    • your passphrase (kept separate from the link)
  4. Share safely
    Send the share link through one channel (for example, chat) and the passphrase through another (for example, voice or password manager note).
    Never send both in the same message.

  5. Recipient retrieves the envelope
    The recipient opens the link, enters the passphrase, and decrypts locally in their browser.

  6. Copy and use the output
    After successful decryption, the real .env content appears and can be copied as:

    • standard .env text
    • JSON format
  7. One-time protection
    Once retrieved, the link is consumed and cannot be opened again.
    This reduces accidental re-access and limits exposure.

Best Practices

  1. Use a long, unique passphrase every time.
  2. Share link and passphrase via separate channels.
  3. Keep TTL short when possible.
  4. Ask recipients to store secrets in a secure vault after decryption.
  5. Rotate secrets after high-risk sharing events.

4

Give a star to encourage!Discussion
Start a new conversation!
Login to join the discussion

More Builds by Srijan Baniyal

bwai-apl-delhi react yolo v8 ipl next.js