Keep passwords, tokens, and keys in encrypted vaults

One encrypted file for every password, token, and key your project needs.

One file

Commit it next to the code.

Safely encrypted

Vaults can only be opened with their key.

Fully private

You and your team own everything.

YOUR APPPostgreSQL · connection stringMySQL · connection stringMongoDB · connection stringRedis · passwordElasticsearch · API keyGitHub · personal access tokenGitLab · access tokenAmazon Web Services · access keyGoogle Cloud · service account keyCloudflare · API tokenDocker · registry credentialsVercel · deploy tokenStripe · secret keyTwilio · auth tokenSendGrid · API keyOpenAI · API keyAnthropic · API keySupabase · service role keyFirebase · service account keySentry · auth tokenDatadog · API keyAuth0 · client secretSlack · bot tokennpm · publish tokenOkta · client secretHeroku · API keyNetlify · deploy tokenGrafana · API keyRabbitMQ · broker credentialsDiscord · bot tokenPagerDuty · integration keySnowflake · account credentialsLinear · API keyMailgun · sending key

Safely store a secret in just a few commands

~/project

$ valt0 init prod

Created the empty vault file.

key VLT0-KEY-D8B38D16-19B5681D-… save it now

$ valt0 store prod:STRIPE_KEY

Key for prod.valt0: ••••••••••••

Value for STRIPE_KEY: ••••••••••••••••

The secret is now stored safely in the vault.

$ git add prod.valt0 && git commit

1 file changed. Locked, as always.

  1. 01

    Make the vault

    Creates prod.valt0 and prints its key.

  2. 02

    Put a secret in

    Your secrets are securely encrypted at rest. Nothing is leaked.

  3. 03

    Keep it anywhere

    An ordinary encrypted file. Commit it next to the code, or carry it on a stick.