Roadmap

Where envdotweb is headed. Up next: a VS Code extension to upload your .env straight from the editor.

In progress

4

VS Code extension

Next up

Upload the .env you have open straight to an environment, pull secrets into your workspace, and reveal or edit values inline — without leaving the editor. Same client-side encryption, right in VS Code.

envdot CLI

login, pull, push, run and diff from your terminal and CI. Decryption happens locally with a token-scoped key.

Scoped CLI tokens

Create project- and environment-scoped tokens, shown once and hashed at rest, with revocation and last-used tracking.

Polar billing & customer portal

Per-seat subscriptions with an annual option, self-serve upgrades and a billing portal. Plan limits are already enforced across the app.

Planned

3

Production change notifications

Opt-in email alerts when a secret changes in production, with per-user preferences.

Integrations & webhooks

Sync to Vercel, Netlify, GitHub Actions and Docker, plus outbound webhooks on secret changes.

Git-style branching for environments

Branch an environment, make changes in isolation, and merge — with a review step before values hit production.

Shipped

5

Zero-knowledge encryption

Browser-side AES-256-GCM with RSA-OAEP envelope sharing across a team.

Encrypted projects, environments & history

Masked secrets with reveal/copy/edit, import/export, version history and environment diffing.

Figma-style team sharing

Invite by email or link, roles, and per-project envelope key grants.

GitHub repo import

Turn any repository into an encrypted project in one click.

One-time secret sharing

Free, no-signup /share tool with links that self-destruct after one view.