Show HN: EnvMark – Git-based .env management with zero infrastructure
envmark.tech
Managing .env files across multiple projects and environments is a mess. Slack DMs, password managers, shared drives – we've all been there.
I built EnvMark to solve this using something we already trust: Git.
The concept is dead simple: - One private Git repo for all your secrets - Each branch = one environment (dev, staging, prod) - Each folder = one project
Pull your .env with a single command:
envmark pull dev
That's it. Git handles versioning, diffs, access control, and audit logs for free. No hosted service, no API, no subscription.
Key features: - Optional AES-256-GCM client-side encryption - Works with GitHub, GitLab, Bitbucket, or self-hosted - Interactive CLI with environment aliases (dev → development branch) - Multi-project support in a single repository
npm install -g @grazulex/envmark
I've been using this across my projects and it's eliminated the "can you send me the .env?" Slack messages entirely.
Curious how others manage environment variables across teams. Do you use Vault, Doppler, or something else?