New: per-secret sharing

Your .env files,
versioned and encrypted.

StoreEnv turns any Git repo into an encrypted, shareable home for its environment files. Push once. Pull anywhere. Share exactly what you mean to.

$ npm i -g storeenv

"Bro, send me the .env" should never be a message anyone has to type again.

~/cakeshop
$ storeenv push -m "Added Razorpay keys"
Project acme/cakeshop (branch main)
Scanning 3 env files
backend backend/.env default +2 ~1
backend backend/.env.production production +2
frontend frontend/.env default no changes
Encrypting 19 secrets locally... done
default v 9f2c81a "Added Razorpay keys"
production v 3b7e0d4 "Added Razorpay keys"
$ storeenv pull # on a teammate's laptop
+ backend/.env 12 keys
+ backend/.env.production 14 keys
+ frontend/.env 5 keys
Restored 3 files.

How it works

The repository is the configuration. Git remote becomes the project, folders become services, file suffixes become environments.

You already knowIn StoreEnv
RepositoryProject, linked to the Git repository
FolderService (frontend/, backend/, root)
BranchEnvironment (default, production, ...)
CommitVersion (author, message, changed keys)
git push / pull / clonestoreenv push / pull / init <url>

Built for secrets you can't afford to leak

Stop pasting secrets into chat.

$ npm i -g storeenv Get started