Stop Slacking .env files. Start syncing them.
P2P encrypted .env sync. No server. No cloud. Just your team on the same LAN.
$ npm install -g p2p-envsync$ envsync create myroom .env$ envsync sync myroom
The .env problem every team has
- Developers share secrets over Slack, email, and sticky notes.
- New team members wait hours for the right .env.
- One wrong value means hours of debugging.
- Secrets are scattered across DMs with no audit trail.
How it works
- 🔐
1. Create a room
envsync create myroom .envEncrypts and stores your .env in a local vault.
- 🔑
2. Share the key
one-time, out-of-bandGive teammates the room key once, over a channel you trust.
- 🔄
3. Sync
envsync sync myroomPeers discover each other on the LAN and exchange an encrypted diff.
Features
Zero server
P2P over LAN, no cloud dependency.
End-to-end encrypted
AES-256-GCM. Keys never leave your machines.
Offline-first
Works without internet and syncs when peers appear.
Diff-based sync
Only changed values transfer, with full history.
GitHub backup
Optional encrypted backup to a private repo.
Menu bar app
Native tray app for macOS (envsync-tray).
Install
CLI
$ npm install -g p2p-envsync
Tray app
$ npm install -g p2p-envsync-tray
VS Code extension: available on the marketplace.
P2P EnvSync vs alternatives
| Feature | P2P EnvSync | Doppler | 1Password | .env in Slack |
|---|---|---|---|---|
| No server needed | Yes | No | No | N/A |
| Free & open source | Yes | Freemium | No | N/A |
| Works offline | Yes | No | Partial | No |
| E2E encrypted | Yes | Yes | Yes | No |
| Audit trail | Yes | Yes | Yes | No |
| P2P / no cloud | Yes | No | No | N/A |
FAQ
Is it safe to sync .env files over the network?
Yes. Every value is encrypted with AES-256-GCM using the room key before it leaves your machine, and the key itself is never transmitted over the network. Peers without the key see only ciphertext.
What happens if I'm not on the same network as my team?
P2P EnvSync is LAN-first, so remote peers won't discover each other automatically. Your vault keeps working offline, and you can use the optional encrypted GitHub backup to exchange changes across networks.
How is this different from HashiCorp Vault?
Vault is a central secrets server you must deploy, unseal, and operate. P2P EnvSync has no server at all: teammates sync directly, which suits small teams that just need to share .env files safely.
Can I use this with Docker / CI/CD?
Yes for local Docker workflows: sync your .env, then point docker compose at it. For CI/CD, keep using your CI provider's secret store; P2P EnvSync targets developer machines.
What encryption does P2P EnvSync use?
AES-256-GCM authenticated encryption. Values are encrypted at rest in the local vault and in transit during sync.