Ali Niyaz

About

Full-stack engineer focused on developer tooling, environment configuration, and secrets hygiene. Builds envtools to make .env files boring in production.

I started envtools because almost every production outage I've witnessed in ten years of shipping software was caused by .env files — a missing key, a leaked secret, a duplicated value that silently overrode the right one. The goal is simple: make working with environment variables boring. Everything runs in your browser; your .env never leaves your machine.

Areas of focus

• Environment variable hygiene across Node.js, Next.js, Django, Rails, Go
• Secrets management — rotation policy, vault alternatives, team workflows
• CI/CD pipelines and the gap between local and production configuration
• Developer tooling that respects your time and your data

Editorial standards

Every post includes the date it was published and, where updates matter, the date it was last reviewed. Technical claims link to primary sources — GitHub repos, framework docs, Node.js source, CVEs — so you can verify independently. If something here is wrong, I want to know: tell me via the contact page.