Share .env files. Never the secrets.
Envbyte syncs, versions and rolls back your team's environment files. The file is encrypted on your laptop before it leaves, only the teammates you invite can open it, and the server can't read a single value.
$ curl -fsSL https://envbyte.trackedge.in/install.sh | shInstalls to ~/.envbyte/bin and checks the download's SHA-256 first.
Apple silicon and Intel. Windows installer
Your team sees# payments-api, productionDATABASE_URL=postgres://app:Hx7pQ2vL@db.internal/paySTRIPE_API_KEY=demo_51NfK2bL9xQ7mZ4cR8vYwSESSION_SECRET=7c1e9f04b2d86a35e1f0c4REDIS_URL=redis://:a8Kd2mQ@cache.internal:6379MAILER_TOKEN=mt_8f2c1e9d04b7a653CHECKOUT_V2=true
Encrypted before it leaves. Readable only by your team.
Encrypted on your laptop
envbyte pushencrypts the whole file before it leaves your machine, variable names included.Stored as noise
The server keeps your files in a form it can't read, so a leaked database gives an attacker nothing.
Opened only by your team
Only the people you invite can open the file, each on their own machine, so nothing gets pasted into chat.
From first invite to last day
Invitations that can't be forwarded
Only Priya's own account can accept it. Forward the email to anyone else and it gives them nothing.
envbyte add priya@company.comHistory and rollback
Every push is a version. Roll the server, or only your local copy, back to any earlier one.
envbyte logs --remoteenvbyte rollback --address <commit>Roles and an audit log
Owner, admin, member and viewer. The log shows who pushed, pulled, invited and rotated, per project.
envbyte role <user-id> viewerenvbyte auditMade for CI
Give your pipeline an identity of its own, and revoke it exactly like a teammate.
ENVBYTE_IDENTITY_KEY=… envbyte pullOffboarding in two commands
Rotating re-encrypts every file, so anything a departing member kept can't open what comes next.
envbyte remove <user-id>envbyte rotate
Up and running in a minute
No keys to copy and no passwords to share. Your teammate signs in, accepts the invitation and pulls.
- 1
Create your account
envbyte register - 2
Start a project in your app's folder
envbyte create payments-api - 3
Encrypt and upload your .env
envbyte push -m "first version" - 4
Invite a teammate
envbyte add priya@company.com - 5
They join and pull it down
envbyte init && envbyte pull
$ envbyte create payments-api✓ Created payments-api$ envbyte push -m "add stripe keys" encrypting .env on this machine✓ Pushed version 3. The server can't read it$ envbyte add priya@company.com✓ Invited priya@company.com# meanwhile, on Priya's laptop$ envbyte init && envbyte pull✓ Decrypted .env · 14 variables$
Prefer your own server?
The hosted service works out of the box. If your company would rather run everything itself, the API ships as a small container with its own Postgres, and the CLI points at it with one variable.
Read the self-hosting guide# on your server
git clone https://github.com/NYLONXD/EnvByte_CLI
cd EnvByte_CLI && cp .env.example .env
docker compose up -d
# on every laptop
export ENVBYTE_SERVER=https://envbyte.your-company.comStop pasting secrets into chat.
Free and open source, under MIT or Apache-2.0.