dotvault encrypts your .env files, .npmrc, kubeconfig and other secrets, and hands them to the people, CI jobs and AI agents you allow — with a single dotvault pull. No more pasting .env into chat or a wiki.
Values you enter in the browser reach your laptop, CI and AI agents through dotvault pull. Lines you wrote by hand stay; only the managed block is rewritten.


Create an account, log in with the CLI, and pull. New teammates follow the same steps on day one.

Sign up at app.dotvault.io with an email and a password.

Install with npm i -g @earthlink/dotvault, then dotvault login.

Run dotvault pull in your project folder and your .env is ready.
Everything you need to hand out secrets, in one service. Every image below is the real product.
Keep development, staging and production in one project. Compare two environments side by side and copy a missing key in one click. Put values shared by every environment in Common, so you fix them in one place.
Read the guide →
Every key keeps its version history. dotvault versions shows who changed it and when; dotvault rollback --to 1 restores an earlier value — and the rollback itself is kept as a new version.

Files that are not key=value pairs go up as-is with dotvault push. Before you commit, dotvault scan finds secrets that slipped into your code — offline.

Keep a Sentry DSN or a Cloudflare token in Global Keys. Only the projects that bind a key receive it, and you can override it per environment.
Read the guide →
Create a read-only service token scoped to one project that expires in 90 days, and put it in GitHub Actions as DOTVAULT_TOKEN. Revoke it and it stops working immediately.

Instead of pasting .env into Claude Code or another agent, hand it one token limited to a project and an environment. Everything it reads is in the audit log, and you can revoke it any time.
Read the guide →
Invite by email and choose an org role (org_admin, member, guest) and a project role (owner, admin, writer, reader), scoped to the environments you pick. Guests only see the projects you grant. Remove someone and their tokens and grants go with them.
Read the guide →
Every reveal, change, token creation and revocation is recorded. Filter by action, actor, target and date.
Read the guide →
dotvault rotate delivers the new value, confirms every consumer has it, and only then revokes the old one. A leak rotation cannot be aborted, so the leaked value never comes back.

Run dotvault init, login, and pull to keep .env in sync across every machine you code on.
Onboarding a new teammate is login + pull — no more sending .env files over Slack.
Store a service token as DOTVAULT_TOKEN in your CI secrets, then dotvault pull --env production for production secrets.
Shared credentials like a Cloudflare token live in the global key pool — only the projects that need them bind in.
.npmrc, kubeconfig, certificates — dotvault push brings them into the same sync flow.
dotvault is free to use. The Usage screen in the console always shows your current usage and limits.

Stop pasting .env files into Slack. Secrets shouldn't be copied around — they should be pulled by whoever's authorized. That's dotvault.
Yes. dotvault is published as a free tool for developers. Personal (just you) has unlimited projects and keys. The Company free plan covers 10 members, 25 projects, unlimited keys and 1,000 pulls a day. Both allow up to 10 environments per project and keep 14 days of audit log.
A series that walks through dotvault with real screens and commands.
dotvault pull in five minutesStop pasting .env. Start pulling it.
Start freeCheck out other products from EarthLink Network.