Run Anywhere
dotenvx works the same across every language, framework, and platform – inject your env at runtime with dotenvx run -- your-cmd.
Multiple Environments
Create a .env.production file and use dotenvx run -f .env.production to load it. It's straightforward, yet flexible.
Encryption
Add encryption to your .env files with a single command. Pass the --encrypt flag.
# Database configuration
DB_HOST="encrypted:BDtEtndvzc2sacliQIbLVSxo2ubscj7dDDAklgxFhugoV+jK9XZbajgvc167U/xtB0CwUBBtd0Gt5sVX3RlQYFozZimWnbZ64eTWQoMeNee8TdEgjmRUV3fkPvw+5jTPkMjssMNL02eN9g==""
DB_PORT=5432
DB_USER="encrypted:BDtEtndvzc2sacliQIbLVSxo2ubscj7dDDAklgxFhugoV+jK9XZbajgvc167U/xtB0CwUBBtd0Gt5sVX3RlQYFozZimWnbZ64eTWQoMeNee8TdEgjmRUV3fkPvw+5jTPkMjssMNL02eN9g==""
DB_PASSWORD="encrypted:BDtEtndvzc2sacliQIbLVSxo2ubscj7dDDAklgxFhugoV+jK9XZbajgvc167U/xtB0CwUBBtd0Gt5sVX3RlQYFozZimWnbZ64eTWQoMeNee8TdEgjmRUV3fkPvw+5jTPkMjssMNL02eN9g==""
DB_NAME="encrypted:BDtEtndvzc2sacliQIbLVSxo2ubscj7dDDAklgxFhugoV+jK9XZbajgvc167U/xtB0CwUBBtd0Gt5sVX3RlQYFozZimWnbZ64eTWQoMeNee8TdEgjmRUV3fkPvw+5jTPkMjssMNL02eN9g==""
# API Keys
API_KEY="encrypted:BDtEtndvzc2sacliQIbLVSxo2ubscj7dDDAklgxFhugoV+jK9XZbajgvc167U/xtB0CwUBBtd0Gt5sVX3RlQYFozZimWnbZ64eTWQoMeNee8TdEgjmRUV3fkPvw+5jTPkMjssMNL02eN9g==""
STRIPE_API_KEY="encrypted:BDtEtndvzc2sacliQIbLVSxo2ubscj7dDDAklgxFhugoV+jK9XZbajgvc167U/xtB0CwUBBtd0Gt5sVX3RlQYFozZimWnbZ64eTWQoMeNee8TdEgjmRUV3fkPvw+5jTPkMjssMNL02eN9g==""
# Email Configuration
EMAIL_HOST="encrypted:BDtEtndvzc2sacliQIbLVSxo2ubscj7dDDAklgxFhugoV+jK9XZbajgvc167U/xtB0CwUBBtd0Gt5sVX3RlQYFozZimWnbZ64eTWQoMeNee8TdEgjmRUV3fkPvw+5jTPkMjssMNL02eN9g==""
EMAIL_USER="encrypted:BDtEtndvzc2sacliQIbLVSxo2ubscj7dDDAklgxFhugoV+jK9XZbajgvc167U/xtB0CwUBBtd0Gt5sVX3RlQYFozZimWnbZ64eTWQoMeNee8TdEgjmRUV3fkPvw+5jTPkMjssMNL02eN9g==""
EMAIL_PASSWORD="encrypted:BDtEtndvzc2sacliQIbLVSxo2ubscj7dDDAklgxFhugoV+jK9XZbajgvc167U/xtB0CwUBBtd0Gt5sVX3RlQYFozZimWnbZ64eTWQoMeNee8TdEgjmRUV3fkPvw+5jTPkMjssMNL02eN9g==""
# Logging
LOG_LEVEL=debug
10x. better.
Increased tooling and features to make dotenv 10x better.
Run anywhere
Cross-platform–works everywhere
Multi-environment
Switch environments easily
Encrypted envs
Encrypt your envs for deploy
Variable expansion
Add the value of another variable in your .env
Multiple .env files
Compose multiple .env files flexibly
Multi-line values
Add multi-line secrets like public keys
Debug
Debug server and local envs with built-in debugging
Contextual help
Built-in next steps when something goes wrong
Append .gitignore
Append to .gitignore in one command
Generate .env.example
Generate .env.example in one command
Prebuild
Prevent building .env files into docker images
Precommit
Prevent committing .env files to code
Personal envs
Set personal environment variables
Command substitution
Add the output of a command in your .env
Scan
Scan and protect for secrets
Get/Set
Conveniently get/set single variables
Monorepo
First-class monorepo support
Sharing
betaSecurely share envs across your team
From the creator of dotenv. Trusted by millions of developers worldwide.
Frequently asked questions
-
A DOTENV_PUBLIC_KEY (encryption key) and a DOTENV_PRIVATE_KEY (decryption key) are generated using the same public-key cryptography as Bitcoin. The DOTENV_PRIVATE_KEY is set on your server or cloud hosting provider and your encrypted .env file is committed safely to code.
-
Yes. Secp256k1 asymmetric encryption is used in many cryptographically secure technologies like Bitcoin. It would take on the order of billions of years to crack using current technology - similar to AES-256.
-
In the CircleCI breach the attacker accessed environment variables only. They could not access codebases. To steal your encrypted .env secrets, an attacker needs need both – the private decryption key AND the encrypted .env files.
Can't find the answer you're looking for? Send us an email at [email protected] team. We'd love to hear from you.