Documentation
getmyenv docs
Runtime configuration for developers. Start in your project folder with npx getmyenv. No account needed. Daily path: npx getmyenv run -- npm run dev. Each project has variables and contexts. Manage them in the dashboard or the CLI. There is no public management REST API.
How it works
1
A context holds the values
context
2
run decrypts them on your machine
getmyenv run
3
Your app reads them as usual
process.env
Primary commands: run, context, set, import, export, guest. Import a .env once. Every value is encrypted. Your code still reads environment variables.
Start here
- Run the CLI
No global install. Every command runs through
npx getmyenv. Requires Node 24 or newer. - CLI reference
start, run, status, context, set, unset, ls, import, export, push, guest, claim, backup, restore, lock, unlink.
- First project
Run
npx getmyenvin your folder. Start without an account or sign in, import your .env, then run.
Also see
- Vault: a key per context, the OS keychain in the CLI, and what happens if you forget the Vault password.
- Contexts: names, slugs, Open and Read-only.
- Languages: Node, Python, Ruby, Rust, Go, PHP. No SDK.
- Security: what we store, tokens, and how contexts limit access.
- llms.txt: short product summary for agents. Full version.