Getting started

Eanvi encrypts and versions environment variables so teams stop sharing .env files over chat. This guide walks through the full first-run loop — dashboard setup, then CLI sync.

Prerequisites

• A modern browser
• Node.js 20+ if you will use the CLI
• Access to email for account verification

---

1. Create an account

1. Open the app and go to Register.
2. Enter your name, email, and password (or continue with a supported OAuth provider).
3. Verify your email if prompted.
4. Sign in. You land on the dashboard.

You can also start from the marketing site: Get Started Free → /register.

---

2. Create an organization

Secrets belong to an organization. New accounts typically get a personal org; you can create another anytime.

1. Open the workspace switcher in the top bar.
2. Choose Create organization.
3. Give it a name and slug (for example acme / acme).
4. Confirm. The new org becomes your active workspace.

Members, billing, API keys, and audit logs are scoped to this organization.

---

3. Create a project

1. Go to Projects.
2. Click New project.
3. Enter a display name and slug (for example my-app).
4. Save.

A project groups related environments (development, staging, production, and custom ones you add later).

---

4. Add an environment

1. Open the project.
2. Create or select an environment — start with development.
3. Optionally add staging and production when you are ready.

Each environment has its own secret set. Changing DATABASE_URL in development never overwrites production.

---

5. Add your first secret

1. Open the environment’s Secrets view.
2. Click Add secret.
3. Enter a key (for example DATABASE_URL) and value.
4. Optionally add a description and tags.
5. Save.

The value is encrypted with AES-256-GCM before it is stored. List views show metadata and masked values — not plaintext. Revealing a value is an explicit, audited action.

Tip: Prefer importing an existing .env (Import / Export) when you already have many keys.

---

6. Install the CLI

npm install -g @eanvi/cli
eanvi --version

See CLI installation for details.

---

7. Pull secrets locally

Authenticate, bind the project, then download decrypted secrets to a local file:

eanvi login
eanvi init --project my-app --environment development
eanvi pull

Running eanvi login with no flags opens an interactive prompt with login options (browser, email & password, or API key). For non-interactive use (CI or scripts), pass a key directly:

eanvi login --api-key eanvi_sk_...

eanvi pull writes to .env by default (or the path in .eanvi/config.json). Keep .env gitignored — Eanvi is the source of truth; the file is a local checkout.

Verify connectivity anytime:

eanvi doctor
eanvi list

---

What to read next