Your .env files,
always recoverable.
Back up, encrypt, and share environment variables across dev, staging, and production. Sign in with GitHub — no CLI, no config, no paid tier.
AES-256-GCM at rest · GitHub OAuth · MIT licensed
The problem
A .env file is one accident away from being a long evening.
Wiped your laptop.
Stripe key, gone. Postgres URL, gone. An evening of recovery — if you can find them all.
Onboarded a teammate.
A Slack DM with the .env attached. Now it lives in their cloud backups forever.
Rotated an API key.
Staging picked it up. Production didn’t. You’re debugging it at 11pm on a Friday.
How it works
Four steps from sign-in to a shared .env.
A workflow that fits how you already ship. No CLI required.
Sign in with GitHub
One-click OAuth. No passwords. No email verification. No setup screens.
Create a project
Dev, staging, and production out of the box. Add custom environments anytime.
Paste your .env
Drop in a whole file. Each value is encrypted before it touches the database.
Share with your team
Invite teammates by GitHub handle. Editor or viewer roles per project.
Features
Built for the way you ship configs.
Encrypted by default. Free for everyone. Open source under MIT.
Per-environment variables
Separate sets for dev, staging, and production. Switch via tabs. Custom envs anytime.
GitHub-based team access
Invite by GitHub username. Assign editor or viewer roles per project.
Project-scoped storage
Each app keeps its own keys. Nothing leaks between repos or environments.
One-click export
Copy a single value or download the full .env. Pastes straight into your shell.
AES-256-GCM at rest
Every value is encrypted before it hits the database. Authenticated encryption catches tampering.
Role-based access
Owner, editor, and viewer roles. Granular control at the project level.
FAQ
Frequently asked questions.
Can't find what you're looking for? Open an issue on GitHub.
Stop losing keys.
Sign in with GitHub. Paste your .env. Your team has it in under a minute.