Secrets

Take your secrets out of .env files

lpm env and LPM Vault keep a project's secrets outside your repository, in the Keychain on a Mac. Both are free and need no account. Pro adds a cloud copy that is encrypted on your machine.

LPM Vault, a Mac app for your secrets

Free and open source. It stores values in your Keychain, opens with Touch ID or your Mac password, and needs no account.

LPM Vault

Keep secrets out of .env files on a Mac. LPM Vault stores them in your Keychain, keeps a history of every change, and publishes an environment to the platform that runs your app.

A history of every change

LPM Vault records each change to a project's values, whether it came from the app, the LPM CLI or an import. Undo one change, or roll back to an earlier point.

Rules for every key

Declare in lpm.json which keys are required, their formats and their defaults. LPM Vault tests each stored value against the rules and marks the ones that fail.

See what a rule change breaks

Edit a key's rules in a draft. LPM Vault checks each environment's stored value against the draft and warns about the ones that would fail, before anything is written to lpm.json.

Import your .env files

Drop an .env file on the window, or paste its text. A review sorts the keys into new, changed and unchanged, and you choose which values to keep before anything is saved.

The same secrets in your terminal

LPM Vault and the LPM CLI read the same Keychain items. Use the app, the terminal or both.

lpm envFree

lpm env set stores a value outside your project folder. Your lpm.json keeps a project's ID and the names of its environments, and it holds no values.

Where values live
In the Keychain on a Mac. On Linux and Windows, in an encrypted file whose key the system's credential store protects, where there is one.
Your scripts
lpm dev and lpm run load the values. Pick an environment with --env.
Your .env files
lpm env import reads one, and lpm env export writes one when a tool needs it.
History
The LPM CLI keeps a history of changes on your machine, and lpm env rollback restores an earlier state.
Read the local secrets docs

When secrets leave your machine

A cloud copy, a team and a deploy each get the values in a different way. None of them needs a .env file in a chat.

Encrypted before they leavePro

lpm env push encrypts a project on your machine and uploads the result. The LPM.dev Registry stores ciphertext, and the keys stay on your devices.

Can LPM read it
No, with one exception that you control. If you turn on CI pulls for a project, LPM can decrypt that project, to hand its values to your CI job.
Each push
A fresh key encrypts it.
In the dashboard
You pair a browser with your LPM CLI, and the browser decrypts the values itself.
A new machine
Each device has its own key, so signing in on another machine doesn't open a personal project. Move it with a backup from LPM Vault.
Read the cloud sync docs

One key for each teammateOrganization

Share a project with your organization, and each member with access gets the project's key encrypted for that member alone.

Who can edit
The Owner, Admins and Maintainers. Other members can read.
Access
It covers a whole project. There are no permissions for single keys.
When someone leaves
lpm env rotate-key encrypts the project again for the members who remain. Replace the credentials they could see, too.
More about organizations

Deploy and CI

Push an environment to the platform that runs your app. The values go directly from your machine to the platform.

From LPM Vault
Vercel, Netlify, Coolify, GitHub Actions and Cloudflare Workers.
From the LPM CLI
Vercel, Coolify, Fly.io, Railway and GitHub Actions, for a personal project on Pro or an organization's project.
In CI
A job on GitHub Actions or GitLab.com can pull one environment with its OIDC identity, with no stored LPM token.
The trade
CI pulls are opt-in for each project, and they let LPM decrypt that project.
Read the secrets docs

Frequently asked questions

Is it free?

Local secrets and LPM Vault are free and need no account. The encrypted cloud copy needs Pro, at $10 a month, and sharing with a team needs an Organization plan.

Can LPM read my secrets?

No, with one exception that you control. A push uploads ciphertext, and the keys stay on your devices. If you turn on CI pulls for a project, the LPM.dev Registry can decrypt that project, because it has to hand the values to your CI job.

Do I have to stop using .env files?

No. lpm env import reads an existing file, and lpm env export writes one when a tool needs it.

Does LPM Vault run on Windows or Linux?

No. LPM Vault is a Mac app, for macOS 14 or later. lpm env works on macOS, Linux and Windows.

What happens when a teammate leaves?

Remove them from the organization, then run lpm env rotate-key --org=<slug>. They can't open anything encrypted after that. If they are the only member who can open a project, share it with someone else first. Replace the credentials they could see, because rotation can't erase a copy.

I set up a new laptop. How do I get my secrets?

Each device has its own key, so signing in on a new machine does not open an existing personal project. On a Mac, LPM Vault backs up every project to one file that a passphrase protects, and you restore it on the new Mac. A project your organization shares with you opens with lpm env pull --org=<slug>.

Start with the secrets on your machine

Install the LPM CLI and run lpm env import on a .env file you already have. It's free and needs no account.