AGSelected work
Case study 03

Developer tooling · 2026

Envy

Your secrets, out of the repo and still exactly where you need them.

Envy macOS app icon
BUILT BYAGmacOS + Linux
Product surfaceIllustrated from the working application

api

~/code/orbit/apps/api · inherits orbit

Active in this folder
NameValue
DATABASE_URLpostgres://••••••••@db:5432/orbit
REDIS_URLredis://••••••••
STRIPE_SECRET_KEYsk_test_•••••••••••• secret
API_PORT4001 worktree
OPENAI_API_KEY•••••••••••• AI keys
LOG_LEVELdebug orbit
Health✓ 14 variables valid✓ 0 .env files on disk✓ pre-commit hook installed
YEAR

2026

ROLE

Creator · Native app & CLI

STATUS

macOS + Linux

SOURCEView repository ↗

01 / Context

The challenge

.env files are plaintext secrets sitting in every checkout, worktree, and backup. They get committed by accident, shared over chat, and drift between the apps of a monorepo.

The response

Envy keeps every value in one encrypted vault and lets the folder you are in decide which variables a command gets, so the usual cd and pnpm dev workflow keeps working with nothing on disk.

02 / What it does

Built around the
real work.

  1. 01

    Per-project environments injected into npm, pnpm, Python, Cargo, Docker and more

  2. 02

    Git-aware worktrees, branch variables, and a pre-commit secret guard

  3. 03

    Touch ID-protected production values, validation rules, and rotation reminders

  4. 04

    Reviewed sync with Vercel, GitHub Actions, Cloudflare, AWS, Railway, and more

03 / Built with

SwiftSwiftUImacOS KeychainLinux CLI

04 / Read more

I deleted every .env file on my laptopWhy I built Envy, a macOS app and CLI that keeps secrets in the Keychain and hands them to your commands based on the folder you're in.
Next case study · 04ModelPort