v0.5.1 availableGit for secrets

Your .env,
with a history.

Envoy gives environment files the workflow they were missing: encrypted staging, redacted diffs, atomic commits, and precise team access.

$cargo install envoy-cli

Read the docsXChaCha20-Poly1305 · local-first encryption

~/acme-api

$ envy status

Changes staged for commit

new.env

mod.env.production

$ envy diff --cached

@@ .env.production @@

- DATABASE_URL=<redacted:42>

+ DATABASE_URL=<redacted:58>

$ envy commit -m "rotate production db"

[4b7f8a1] 2 encrypted files committed

keys stay local

commit 4b7f8a1

one passphrase

A keyring, not a key pile.

Every managed file gets an independent key derived locally from one project passphrase.

per-file access

Grant each collaborator access to the exact encrypted blobs they need. Owners stay in control.

git semantics

Stage, diff, commit, push, pull, and remove secrets with the same mental model as Git.

familiar by design

Envoy keeps encryption machinery out of the way and preserves the muscle memory of a normal Git workflow.

01
Initialize the ledger
Create the project, authenticate with GitHub, and choose the one passphrase that protects its local keyring.
$envy init
02
Stage what changed
Add one or many environment files, then inspect a structural diff where values remain redacted.
$envy add .env && envy diff --cached
03
Commit and collaborate
Push encrypted history, invite project members, and narrow individual files to explicit collaborators.
$envy commit -m "configure api" && envy push

live infrastructure

Checking

PostgreSQL—

Deniz Cloud S3—

GitHub OAuth—

recent availabilityNo data