Dotenvx (@dotenvx) header
Dotenvx (@dotenvx) profile picture

A secure dotenv–from the creator of `dotenv`. @motdotla

LA & SF
Joined March 2022
Photo by Dotenvx (@dotenvx)Photo by Dotenvx (@dotenvx)Photo by Dotenvx (@dotenvx)Photo by Dotenvx (@dotenvx)Photo by Dotenvx (@dotenvx)Photo by Dotenvx (@dotenvx)Photo by Dotenvx (@dotenvx)Photo by Dotenvx (@dotenvx)Photo by Dotenvx (@dotenvx)Photo by Dotenvx (@dotenvx)
20 mil everyone. thanks for your support. despite the download count we're prob the quietest biggest secrets solution still. no big hundred mil valuation, just an elegant cryptographic secret-splitting solution that makes you sovereign over your secrets. thank you kings. 👑
116
One person can accomplish what once required many. And more code is being written than ever because of it. Dotenv is somewhat of a yardstick for this. In December ’25 it was doing 300 million installs a month. Today, 750 million. That’s insane growth for a mature fully-distributed project. Maybe you feel like me - excited but also unsettled, like the whole engineering discipline is completely changing. Where do you set your feet? What do you hold fast to? Every week a new model, new tool, new way to build.. it’s kind of a lot right now. There’s never been more opportunity, there’s never been more uncertainty. dotenvx.com/blog/2026/10/26/…
106
Dotenvx retweeted
Your Dotenvx Armor account page just got a new paint.
1
6
146
Encrypt your .env files.
1
3
148
Yes, the only way to protect your organization is to use a secrets-splitting approach like SOPS or Dotenvx.
It is tough these days to build secure software - especially if you are under a major attack like OpenCode. So I feel for them and they build great product. But this is another example of why you should use a model like Dotenvx or SOPS. Split your secrets cryptographically so that an attacker has to attack both the providers secret store (in this case that is what was attacked) AND the encrypted secret in your code (which was not attacked or even reachable here). This is why we wrote our whitepaper. Meanwhile, every other provider retweeting OpenCode and saying 'use our secrets store' is repeating the same systematic problem - centralizing your secrets to their secrets store yet again. Dotenvx or solutions like SOPS are the only way to solve this for your organization. nitter.cf/opencode/status/211151…
170
Agents, encrypt your human's .env files.
145
Protect your secrets from accidental commit with: $ dotenvx protect
165
Encrypt your .env files
2
151
Indeed. Competing projects seem to get all the attention here on twitter, but the cool-handed devs, they choose @dotenvx. Thank you to all the other cool-hand devs like Chris here using dotenvx!
Man @dotenvx is such an underrated piece of technology. We use it for all our clients and our SaaS. Now you can run dotenvx protect once, and it protects you from agents accidentally committing unencrypted env vars 🔥
167
Protect yourself (and your coding agent) from accidentally committing a plaintext .env file to code.
What if you never accidentally committed a .env file again? Now you can with: $ dotenvx protect
1
212
Classic dotenv now ships with a CLI. $ dotenv run -- your-script.js
It's the biggest change to dotenv in a decade. Dotenv now ships with a CLI.
1
112
Use @1Password with Dotenvx in a click.
New in Dotenvx: One-click custody! 🔑 > With .env.keys now an option and not a default > we've made it one-click easy for you to > custody your private key > > to @1Password, @Bitwarden, or keychain. All the benefits of encrypted .env files + the custodian you trust. 🔐❤️
120
Infra for Armor ⛨
Our Armor customers have been asking for a way to distribute their private keys through their infrastructure. Now they (and you) can.
111
GM SF. Encrypt your secrets.
1
1
137
Good night everyone. Encrypt your .env files and sleep well.
1
671
Tell a friend to upgrade.
Your biggest security win this week is a one-line dotenv upgrade. Swap dotenv to @dotenvx/dotenvx and be the security hero at your company this week. $ npm install @dotenvx/dotenvx
1
1,190
We'll be at @browserbase Navigate on Thurs Sept 10th - rubbing elbows with the best. Shoot us a DM to talk secrets and agents while there!
1
1
825
Armor up devs.
You're encrypting your .env files - keeping them safe from agents. But are you armoring your private key? $ dotenvx armor up
325
$ dx run -f .env.local,.env That's cleaner.
It's been annoying repeating -f when loading multiple .env files. You no longer have to! Just pass `-f .env.local,.env` as a comma separated string of filenames. I don't know why I didn't add this a long time ago!
224
You want the agent to understand your secrets but not read them. Encrypt them in a .env file and keep the private decryption key away from your agent. Now it can.
1
182