Every developer has copied a .env file between machines over Slack, email or a USB stick. It works until it doesn't: a key goes missing, a value is stale, or the file lands in a Git history it should never have touched.

nvault treats environment configuration as what it is — sensitive data that changes often and needs to move with you. It is a secure, developer-native vault: store your config files once, keep a full version history, and restore any project's environment on a new machine in one command.

Principles

• Security first. Encryption happens in your browser. The server stores ciphertext and wrapped keys, never plaintext and never your passphrase.
• Fidelity. Files are preserved byte-for-byte. nvault does not parse and rewrite your configuration.
• The CLI is a product, not an afterthought. WSL, SSH and headless workflows are first-class.
• Boring where it counts. Standard algorithms, explicit destructive actions, and no third-party scripts on the page.

Status

nvault is in early access. The web application — authentication, projects, upload and download, versioning and restore — is available today. The terminal CLI and process secret injection (nvault run) are next on the roadmap.