About getmyenv
Last updated: September 20, 2026
Managing secrets as files was the problem
Environment variables are fine. Storing them as files is not. A .env on disk is plaintext. It ends up in git history, chat logs, screenshots, and shared folders. Sharing means copying the file. There is no expire, no revoke inside the file itself, and no environment scopes - one blob for every machine that can read it.
What getmyenv keeps
The native environment interface. Your application still reads environment variables. Same code. No SDK.
What getmyenv adds
- Client-side encryption (browser for Simple, machine for Advanced). We store ciphertext only. Never your Vault password.
- Projects and environments so secrets are scoped.
- Revoke and expire in getmyenv - we stop providing the secret.
- Machine access requests with short-lived grants.
- Webhooks that POST names and metadata - never secret values.
Does not
- See or store your Vault password.
- Store plaintext secret values.
- Require an SDK in your application.
- Revoke credentials at third-party providers when you revoke in getmyenv.
- Control what your process does after secrets are loaded into the environment.
Read more
Open pilot
getmyenv is an open pilot. Early adopters get a lifetime free account with up to 5 projects. No paid plans are live yet.