Introducing EnvSync
Why we built another secrets manager: most teams don't need zero-knowledge encryption and a six-figure compliance package, they need their .env files out of Slack. Here's the shape of what we shipped.
Notes on building EnvSync — security decisions, product tradeoffs, and the occasional post-mortem.
Why we built another secrets manager: most teams don't need zero-knowledge encryption and a six-figure compliance package, they need their .env files out of Slack. Here's the shape of what we shipped.
A per-org data key wrapped by a master key sounds complicated until you draw it out. Here's why we picked this design over encrypting every secret directly with one shared key.
Most permission systems either give you three roles and no flexibility, or a rules engine nobody wants to configure. We landed on sane defaults plus an editable matrix — here's why.
Our CLI ships with no npm dependencies at all — just Node's built-ins. That's a smaller supply-chain surface for a tool that holds decrypted secrets in memory. Worth the extra code.