For developers · Free

Sync your .env files and secrets anywhere. One command.

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.

Start with just an email and a password — no AWS account needed
Every value has a history, so a mistake is one rollback away
The audit log records who viewed or changed what, and when
Install the CLI

The console and the CLI see the same values

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.

The console's Keys screen: the development environment lists API_BASE_URL, DATABASE_URL and SMTP_PASSWORD, with actions for the selected key on the right (reveal value, delete, promote to Common).
Console — manage keys per environment
A terminal running dotvault pull: the hand-written PORT and DEBUG lines stay, three keys are written between the managed markers, and .env is -rw-------.
CLI — dotvault pull writes your .env (hand-written lines stay)

Get started in 3 steps

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

dotvault's Create an account screen with email, password and confirm-password fields and a Create account button.

1Create an account

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

A terminal running dotvault login and dotvault whoami: the login succeeds and shows the personal organization.

2Log in with the CLI

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

A terminal running dotvault pull, writing three keys into .env.

3Pull

Run dotvault pull in your project folder and your .env is ready.

What you can do

Everything you need to hand out secrets, in one service. Every image below is the real product.

ENVIRONMENTS

One project for every environment — and see the differences

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 →
The Compare environments drawer: production vs development, with DATABASE_URL and SMTP_PASSWORD only in development and a Copy to production button on each.
HISTORY

Overwrote a value? Roll it back

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.

Read the guide →
A terminal running dotvault rollback and dotvault versions: DATABASE_URL is restored to version 1 and the history lists v1, v2 and v3.
FILES

Ship .npmrc and kubeconfig as whole files

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.

Read the guide →
A terminal running dotvault scan: it finds a service token, a GitHub token and an AWS key in ci.yml, deploy.sh and s3.js, and exits with code 1.
GLOBAL KEYS

One place for values every project uses

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 →
The Global Keys screen: SENTRY_DSN has a Common value and a production override, with Update value, Delete override and Delete key buttons.
CI / CD

Give CI one short-lived token — not your password

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.

Read the guide →
The Create service token dialog: name ci-deploy, role Read only (viewer), project demo-app, expiry 90 days.
AI AGENTS

A scoped token for your AI agent

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 →
The Create service token dialog: name claude-agent, role Read/write, project demo-agent-app, expiry 30 days, limited to production.
TEAM

Invite people, scope what they see, shut a leaver out

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 →
A project's Access tab: members and a team hold owner, writer or reader roles with environment scopes, each with Change and Revoke buttons.
AUDIT LOG

Know who did what, and when

Every reveal, change, token creation and revocation is recorded. Filter by action, actor, target and date.

Read the guide →
The Audit Log: rows for project archive and delete and for service token creation and revocation, with time, actor, action and target.
ROTATION

Rotate a leaked key without downtime

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.

Read the guide →
A terminal running dotvault rotate PAYMENT_API_KEY --reason leak: the rotation starts, --abort is refused because it is a leak rotation, and the status shows STAGED.

Built for these moments

Solo developers

Run dotvault init, login, and pull to keep .env in sync across every machine you code on.

Development teams

Onboarding a new teammate is login + pull — no more sending .env files over Slack.

CI/CD pipelines

Store a service token as DOTVAULT_TOKEN in your CI secrets, then dotvault pull --env production for production secrets.

Organizations running multiple products

Shared credentials like a Cloudflare token live in the global key pool — only the projects that need them bind in.

Teams syncing more than .env

.npmrc, kubeconfig, certificates — dotvault push brings them into the same sync flow.

Pricing

dotvault is free to use. The Usage screen in the console always shows your current usage and limits.

Personal

Just you
Free
  • Unlimited projects
  • Unlimited keys
  • Up to 10 environments per project
  • 14 days of audit log

Company (free plan)

Your team
Free
  • Up to 10 members
  • Up to 25 projects · 1 team
  • Unlimited keys · up to 10 environments per project
  • 1,000 pulls per day · 14 days of audit log
The Usage screen on the free plan: USERS 2/10, TEAMS 1/1, PROJECTS 3/25, KEYS 2/unlimited and SYNCS today 0/1000.
Usage screen — 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.

Frequently asked questions

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.

Step-by-step guides

A series that walks through dotvault with real screens and commands.

Stop pasting .env. Start pulling it.

Start free
Language日本語English