Dotenv and Dotenvx theme buttons

About

A small file. A lasting commitment to keeping secrets safe.

DOTENVX LLC keeps secrets safe without making software harder to ship. We're the company behind Dotenv, Dotenvx, and the next chapter of .env.

We started with a problem every developer recognizes: an app needs credentials, but those credentials don't belong in its source code. Dotenv gave them a home in a small, readable file. No dashboard to learn. No service to depend on. Just a file and the code you were already writing.

That simplicity mattered. But the secrets on one developer's laptop also had to reach teammates, build servers, and production. Keeping the file out of Git meant finding another way to move it around. We wanted secrets to follow the same path as the software they configure, without exposing their values.

That's why we built Dotenvx. Encryption lets the file travel with your code while its private key stays separate. The familiar .env becomes something you can version, review, and share through Git.

Now we're asking the next question: how can an agent work on your app without being handed its secrets? Envfile carries our approach forward, making the rules for secrets explicit so software can enforce them.

Secrets separate from code

We created Dotenv to separate secrets from code. One small file made configuration safe.

Dotenv →

Secrets encrypted alongside code

We created Dotenvx to make that same file safe to commit and share through Git. Secrets stay encrypted alongside your code and decrypt in memory at runtime.

Dotenvx →

Secrets separate from agents

We're building Envfile to keep secrets out of agents' reach. Your app gets secrets; your agents get rules.

Envfile →

We keep coming back to that small file. Developers understand it. Projects can carry it. Our job is to make it safer as the way we build software changes.