Keep secrets on your server, out of your deployment tool
Use case · Updated on 12 October 2026
The problem
A hosted deployment tool is convenient, but it usually wants every variable of every service – including the production database password and the payment provider’s API key. Whoever runs the tool, and anyone who breaks into it, can then read them.
Two ways to keep secrets
In Enver you choose per value: store it encrypted in Enver, or keep it in an env file on your own server, which the agent reads locally so that Enver never receives it.
Stored in Enver, encrypted
- Encrypted with AES-256-GCM and a random IV per value.
- No API response ever contains a secret value – the form only shows that it is set.
- The only way back is Secrets Reveal, a separate permission, and every reveal is written to the audit log.
- Decrypted only to be sent to your agent over the encrypted connection when the service deploys.
Kept on your server, never sent to Enver
- The values live in an env file in
/etc/enver/env-fileson the edge server. - Enver stores only the file’s name. The agent reads the file at every start and passes the values straight to the container.
- Values from the file win over anything set in Enver, so the server’s administrator has the last word.
- They are never shown, exported, revealed or audited by Enver – only a change of the file name is audited.
Set up an env file
sudo nano /etc/enver/env-files/my-app.env
sudo chown root:enver-edge-server /etc/enver/env-files/my-app.env
sudo chmod 640 /etc/enver/env-files/my-app.env
Then open the service in the environment, fill in Env file on the edge server with my-app.env and restart it. The format is the usual NAME=value per line. The agent reads nothing outside the directory: absolute paths, .. and symbolic links leading out of it are refused.
Verify it yourself
You don’t have to take our word for it. The agent can write the TLS session keys of its connections into a file, so Wireshark decrypts everything it exchanged with Enver. The deployment message carries the env file’s name and the variables set in Enver, but no value from the file. The guide walks through the capture step by step. And because the agent is open source, you can also read the code that reads the file and check that a package was built from it.
What it doesn’t protect against
- On Docker the values end up in the container’s environment, so anyone with Docker access on the server can read them with
docker inspect, as with any variable. - On Kubernetes the agent stores them in the service’s Secret in your own cluster.
- Whoever may edit a service in Enver can point it at any file in that directory, so keep there only the files of services running on that server, ideally one subdirectory per environment.
Enver is free for up to 2 environments and 10 services. Try it with a service whose secrets never leave your server.
Questions
Can I mix both ways?
Yes. Many teams keep shared, low-risk values in Enver and only the production credentials in an env file on the server.
What happens if the env file is missing?
The service doesn’t start, and its error names the file – never its contents.
Where is the rest of my configuration stored?
On Enver’s servers in the Czech Republic. The contents of your containers, their volumes and database backups never leave your own servers.