Skip to content
EANVI

Docs

Managing secrets

Create, update, reveal, version, import, and export encrypted secrets.

Managing secrets

Each secret is a named key with an encrypted value, optional description and tags, and a version history. Plaintext never appears in list APIs or the database.

Create a secret

  1. Open a project environment.
  2. Choose Add secret.
  3. Enter KEY (uppercase snake case recommended) and the value.
  4. Add tags (for example database, stripe) to filter later.
  5. Save.

Eanvi encrypts the value with AES-256-GCM before persistence. See Encryption.

Update a secret

Editing a value creates a new version. Metadata changes are recorded in audit logs. You can restore a prior version from the history view.

Reveal

List views show masked values. To see plaintext:

  1. Use Reveal on a single secret, or
  2. Run eanvi list --reveal / eanvi pull / export with explicit intent.

Reveals are rate-limited and audited. Prefer pull/export for bulk local use instead of revealing many keys in the UI.

Import and export

Import

Upload or paste .env, JSON, or YAML:

  1. Environment → Import.
  2. Preview conflicts (create / update / skip).
  3. Confirm.

CLI:

eanvi import .env.production --environment production --dry-run
eanvi import .env.production --environment production

Export

eanvi export --format env --output .env.backup
eanvi export --format json
eanvi export --format yaml --tags database,cache

Exports decrypt values for the authenticated principal with permission — treat output like a password file.

Version history

Open a secret → History to:

  • Browse versions
  • Reveal a historical value
  • Compare two versions
  • Restore a prior version (creates a new current version)

Bulk actions

  • Bulk copy — copy selected keys in dotenv format
  • Bulk delete — remove multiple secrets with confirmation
  • Duplicate — clone a secret to another key or environment (where supported)

CLI day-to-day

eanvi pull                 # remote → local .env
eanvi push --dry-run       # preview local → remote
eanvi push                 # apply
eanvi diff                 # compare
eanvi sync --yes           # bidirectional merge

Next steps