---
title: "Comment by Mot on \"Dotenv-vault: The New Way to Manage .env\" | Hashnode"
description: "Great Post Shen. Nice breakdown of things. As to your thought here: Disclaimer: I am not sure how will dotenv and Docker work in a serverless environment (Verce"
url: "https://hashnode.com/posts/dotenv-vault-the-new-way-to-manage-env/646ce460f419f3d1c1b5aadc/comment/647a5e521c128bf71962a6b4"
---

[Discussion](https://hashnode.com/posts/dotenv-vault-the-new-way-to-manage-env/646ce460f419f3d1c1b5aadc)

Comment [Dotenv-vault: The New Way to Manage .env](https://hashnode.com/posts/dotenv-vault-the-new-way-to-manage-env/646ce460f419f3d1c1b5aadc)

[Mot](https://hashnode.com/@dotenv)

[Jun 2, 2023](https://hashnode.com/posts/dotenv-vault-the-new-way-to-manage-env/646ce460f419f3d1c1b5aadc/comment/647a5e521c128bf71962a6b4)

Great Post Shen. Nice breakdown of things. As to your thought here:

> Disclaimer: I am not sure how will dotenv and Docker work in a serverless environment (Vercel), maybe it'll retrieve it for every different server?

Checkout the `.env.vault` file. It is not well documented yet, but it is the future here today. Rather than syncing your secrets and scattering them across multiple 3rd parties, you include an encrypted .env.vault with your deploy, and then set a single DOTENV\_KEY on your server/serverless/etc. On boot, your .env.vault file is decrypted just in time and your app runs correctly.

This new approach to security will prevent breaches like the CircleCI breach being effective.

This is an essential difference between dotenv-vault and other SecretOps solutions. It's important to us.

[Hoh Shen Yien](https://hashnode.com/@ShenYien)

[Jun 3, 2023](https://hashnode.com/posts/dotenv-vault-the-new-way-to-manage-env/646ce460f419f3d1c1b5aadc/comment/647a5e521c128bf71962a6b4#reply-647ad57c1c128bf71962ac1c)

Thanks for the explanation, it makes a lot of sense to me now!

Also thanks for the amazing dotenv-vault, I really enjoy using it!
