Security

How values are stored, read, and logged.

Encrypted on its own. Opened by one token for one environment. Read into a log that names keys and never values.

Encrypted one value at a time.

Nine rules cover how a value is stored, who can read it, and what the log keeps. Open any one to see how it works.

Encryption per value

Each value gets its own AES-256-GCM ciphertext.

One data key per project

Values in a project are encrypted under that project's own data key.

Context binding

A ciphertext only decrypts in its own project, environment, and variable name.

Key rotation

Rotate the root key without touching a single value.

Scoped tokens that expire

A token opens one project and one environment, then expires.

Tokens stored as digests

The raw token is shown once, when you create it.

Withheld values

Mark a value withheld for an agent and it is left out of that agent's environment.

Audit records name keys, not values

Every read records who read, the project, environment, key names, source, and time.

Encrypted local cache

The CLI keeps the last resolution encrypted on disk for five minutes.

One-time shares

Send a value to someone without an account. The link closes on first read, or at a deadline you set.

Two-factor for everyone

Require an authenticator app for the whole organization. A member without one cannot get in.

Stop pasting .env files.

One command. The right values for whoever runs it.