Stop losing environment variables. Back up, organize, and recover your configs instantly.
12 variables
How it works
Simple workflow designed for developers who need quick access to their configs.
Authenticate securely using your GitHub account. No password, no setup.
Organize variables by project and environment (dev, staging, prod).
Paste your .env content or add variables one by one. Search and edit anytime.
Copy individual values or export full .env files when setting up new machines.
Features
Built for developers who need reliable, secure access to their project configurations.
Keep keys grouped by project and environment (dev, staging, prod).
Copy values or export .env files instantly with one click.
Quick and secure access from any browser.
Simple web interface - just open, paste, and save.
All environment variables are encrypted before storage and decrypted only when you access them.
Your data stays private with industry-standard encryption and secure authentication.
Security
Your environment variables contain sensitive information like API keys, database credentials, and secrets. ENV Store implements industry-standard security measures to protect your data at every layer. We use the same encryption algorithms trusted by banks, healthcare providers, and government agencies to ensure your configurations remain private and secure.
FAQ
Common questions about ENV Store and how it works.
Sign in with your GitHub account, then create a project for each application. Add your environment variables as KEY=VALUE pairs — either manually, or by uploading an existing .env file. When you need to set up a new environment, export the whole project as a .env file or copy individual values with one click.
All environment variables are encrypted at rest using AES-256-GCM — the same standard trusted by banks and governments. Key derivation uses PBKDF2 with 100,000 iterations and a unique salt per entry, making brute-force attacks computationally infeasible. Data is also transmitted over HTTPS/TLS at all times.
Yes. Paste the contents of any .env file directly into the editor and ENV Store will automatically parse each KEY=VALUE pair. Comments and blank lines are handled gracefully, so you can paste real .env files without cleanup.
Open any project from the dashboard and click Export. You get a standard .env file with all your variables, ready to drop into any project. You can also copy individual values or the entire file to clipboard without downloading.
Yes — completely free and open source. There are no plans, paywalls, or premium tiers. You can also self-host it by cloning the GitHub repository and following the setup guide.
Absolutely. ENV Store is open source (MIT licensed). Clone the repository, set up a MongoDB database, configure GitHub OAuth, add your ENCRYPTION_SECRET, and deploy anywhere — Vercel, Railway, a VPS, or locally. The README has a full setup guide.
AES-256-GCM with PBKDF2-SHA256 key derivation (100,000 iterations, random salt per encryption). GCM mode provides authenticated encryption — it detects any tampering with stored ciphertext before decryption, adding an extra layer of integrity protection.
Currently each account manages its own projects. To share variables with teammates, export a .env file and send it through a secure channel. Team collaboration and shared projects are on the roadmap.
Join developers who trust ENV Store for reliable config management.