· Infrastructure · 5 min read

Multi-environment secrets without dotenv drift

By Ethan Cole, Co-Founder & CTO

Staging and production issues often trace back to the same mistake: a copied .env file that drifted, or a release step that leaked credentials across boundaries.

Once a team moves past a single production box, environment drift becomes an everyday risk. A feature works in dev, fails in staging because a variable name changed in February, and blocks a release while engineers compare notes over chat.

The temptation is to share one oversized configuration file or copy values loosely between environments. That fixes the short-term friction and creates a much worse security boundary.

In Nimbus, dev, staging, and production keep strictly isolated runtime copies and secret stores. Promoting a service from staging to production carries the container image reference and topology settings forward, never the underlying secret values.

After a secret is saved, the control plane shows only that the key is configured and when it changed — never the plaintext value back in the browser. Dev workloads cannot read production credentials, even by accident.

Configuration shape should stay consistent across every environment while credential access stays tightly scoped to the environment that owns it.

All notes