API keys, tokens, database passwords, SSH credentials, certificates and .env files, organised by project and environment in a vault that is encrypted on your machine.
Use your secrets where you work: a CLI that runs commands with them, CI secret sync, an SSH agent and a VS Code extension. Decrypted only on your machine.
For you: Run commands with secrets, write .env files, push to CI, use SSH keys and VS Code — decrypted only on your machine.
keyvalt run starts your app with a project’s secrets; env pull writes .env files
Push secrets to GitHub Actions, GitLab CI/CD or Vercel in one command
SSH agent serves keys from your vault to ssh and git, never written to disk
VS Code: insert or copy secrets and pull .env files
Connected tools can read only developer items and can be revoked under Devices
Sign up, choose a strong master password and store the recovery kit offline.
2
Enable two-step verification
Protect your KeyValt sign-in with an authenticator code.
3
Get developer tools
Developer tools come with the Business plan (and the Developer plan where offered). A solo developer can use Business with one seat.
4
Create a project
For example “payments-api”, with environments such as development, staging and production.
5
Import your .env files
Import each environment’s .env file, then delete the plain-text copies from your disk.
6
Add other credentials
API keys, OAuth apps, database and SSH credentials and certificates, each as its own typed record.
7
Set expiry and rotation dates
Add an expiry date or rotation period so the Expiry & Renewal Center can warn you in time.
8
Add your consoles as portals
AWS, GitHub, Cloudflare and others, with their MFA codes.
9
Copy when you need a value
Open the project and copy a secret or download the .env for an environment when you set up a machine.
10
Use secrets in your terminal and CI
Install the KeyValt CLI: keyvalt run starts your app with the right secrets, and keyvalt ci push copies them to GitHub, GitLab or Vercel.
11
SSH keys and VS Code
Run keyvalt agent to use SSH keys from your vault, and the VS Code extension to insert secrets or pull .env files.
12
Share with a handoff link
When someone needs a credential, send a Secure Handoff link with an expiry instead of pasting it in chat.
Real-world use
How people use it
Example situations. Names are illustrative.
Cloud engineer with several AWS accounts
Situation
Anita manages dev, staging and production AWS accounts plus Cloudflare and GitHub.
With KeyValt
Each console is a portal with its MFA code; access keys live in the project for each environment, with rotation dates.
Cleaning up .env files
Situation
Karan has .env files for six projects on two laptops, some outdated.
With KeyValt
He imports them into projects and environments, deletes the plain files and downloads a fresh .env only when needed.
No more surprise certificate expiry
Situation
An SSL certificate expired last year and took a site down for an hour.
With KeyValt
Certificates now carry expiry dates and appear in the Expiry & Renewal Center weeks ahead.
IT support engineer
Situation
Imran supports 40 office machines, routers and admin panels.
With KeyValt
Router and admin panel logins are portals, server access is in SSH records, and procedures are in encrypted notes.
Why KeyValt
Practical security you’ll actually use
Encrypted on your machine
Secrets are encrypted before they leave your browser; the server stores ciphertext only.
Organised like your work
Projects and environments instead of one long list.
Knows what expires
Expiry and rotation dates feed a single renewal view.
Share without chat history
Expiring, revocable handoff links.
Your logins too
The same vault handles your consoles, personal accounts and cards.
Security & privacy
How your data is protected
Each item uses its own key, and its encryption is bound to the item’s identity, so encrypted values cannot be swapped between items on the server without detection.
What we do
Your vault is encrypted in your browser with AES-256-GCM before it is saved. Our servers store only encrypted data and have no key to read it.
Your master password never leaves your device. A key is derived from it with Argon2id (64 MiB of memory, 3 passes); only a separate login hash is sent, and it is stored hashed again.
Optional two-step verification for your KeyValt sign-in with an authenticator app, plus one-time recovery codes.
A recovery kit, created on your device, lets you reset a forgotten master password without losing data.
Sign-in sessions use secure, HttpOnly cookies and expire after 7 days of inactivity. Repeated failed logins lock the account temporarily.
The extension fills only on the website saved with the login, flags look-alike addresses, and locks itself when idle.
Secure Documents are encrypted in your browser before upload. Authenticator secrets in your vault are encrypted like everything else.
Good to know
If you lose both your master password and your recovery kit, we cannot recover your vault.
KeyValt does not check your passwords against breach databases or flag reused passwords yet.
“Use-only” sharing is an application control, not a cryptographic one.
KeyValt has no SOC 2 or ISO 27001 certification at this time.
The extension is available for Chrome and Edge; there are no native mobile vault apps yet.
Prices in Indian Rupees from our current plan list. No GST or other tax is added. A 14-day free trial, without a card, is available on eligible paid plans.
Can my application read secrets from KeyValt at runtime?+
No. There is no CLI, SDK or API for that. KeyValt is for storing and sharing secrets securely by people. Use your cloud provider’s secret manager for runtime access.
Does KeyValt rotate keys automatically?+
No. You can set an expiry date or rotation period, and KeyValt shows what is due and can email a reminder. You rotate the key with the provider.
Can I import and export .env files?+
Yes. Import a .env file into a project environment and export it again when you need it. Delete plain-text copies you don’t need.
Is version history kept?+
Yes. A secret keeps up to 10 previous versions with their dates.
Which plan includes developer tools?+
Business includes them, and so does the Developer plan when it is offered. Free and Pro do not include developer tools.
How do I share a secret with a client or teammate?+
Create a Secure Handoff link. It is encrypted in your browser; the key is in the link or protected by a password you share separately. Set an expiry and view limit, and revoke it when done.
Can I store SSH private keys?+
Yes, as an SSH record with host, user, port, private key and passphrase. Treat any machine where you paste the key as part of your security.
Is it safe to store production credentials?+
They are encrypted on your device with AES-256-GCM and our servers cannot decrypt them. Follow your company’s policies; some organisations require production secrets to stay in approved enterprise tools.
Does it support SSO or SCIM for my company?+
No. Sign-in is email and password or Google. There is no SAML single sign-on or SCIM provisioning.
Which browsers does the extension support?+
Google Chrome and Microsoft Edge.
Protect your developer secrets
Move your keys, tokens and .env files into an encrypted, organised vault.