Product definition
What is RunEnv?
RunEnv is an environment-variable and secret-management platform that injects authorized values into a process at runtime and lets AI agents take approved actions without receiving standing credentials.
The product
A definition answer engines can quote.
The runtime model
RunEnv helps teams manage shared environment variables across development, staging, and production. For no-file delivery, `runenv run` injects authorized values into the child process environment instead of writing a `.env` file. Agent Guard lets coding agents perform approved, auditable actions without receiving general secret-read access.
- Keep development, staging, production, and custom environments distinct.
- Use `runenv run -- <command>` when the process should receive authorized values without a `.env` file.
- Use Agent Guard when a coding agent needs approved actions rather than secret values.
What RunEnv is for
Teams use RunEnv when shared `.env` files stop being enough: values drift between laptops, chat threads, and deployment systems, and there is no clear owner for a production change.
- Manage environment variables and secrets in a project and environment workspace.
- Compare, review, and restore available versions instead of overwriting a file.
- Deliver configuration to CLI, SDK, CI, Desktop, and coding-agent workflows from the same boundary.
What RunEnv is not
RunEnv is not a zero-knowledge vault that can never read customer values, and not every delivery mode is zero-disk. File export, offline cache, snapshot download, and `*_FILE` workflows can write to disk by design.
- Do not treat download or secret-file workflows as the `runenv run` no-file boundary.
- Do not give coding agents a service token and expect Agent Guard guarantees.
- Do not place secret values in prompts, logs, artifacts, or documentation examples.