Your first project

Open getmyenv in your browser and sign in with your email. A one-time code arrives in your inbox.

In the dashboard, click New project. Give it a name that matches your codebase. Each project has two environments: Development and Production. The secrets page shows them as separate tabs. Creating a secret in one environment also creates an empty placeholder with the same name in the other.

Simple Protection encrypts secrets in the browser before upload. Fast setup in the dashboard.

Advanced Protection encrypts secrets on your machine with the CLI.

See /docs/protection-modes for the full comparison.

Add secrets one at a time in the dashboard, create name-only placeholders with init (when a linked project is set; login or paste a token if asked), or migrate an existing .env file with the CLI.

cd path/to/your/project
npx getmyenv login
npx getmyenv init
npx getmyenv migrate
npx getmyenv migrate --file .env.production -e production

Placeholders appear in the dashboard so you can fill values later. Migrate searches this folder tree for .env* files (including .env.example / .env.sample after a fresh pull), lists candidates when there are several, then encrypts and uploads ciphertext. Use --file to skip the picker. Use lowercase -e development or -e production. Do not bake production keys into app source.

Use run to inject secrets into your process at startup. Your code still reads process.env.OPENAI_API_KEY.

npx getmyenv run npm start