Solutions / Developers

Secrets belong in a vault. Not your scrollback.

Store project credentials with the context around them, then use the tools you need to get moving. Everything runs on your own device.

The Tools page with the groups Generate, Codes, Develop and Inspect, the six generators and the password generator open.

Developers

A proper home
for project secrets.

Project secrets

API secrets, SSH keys and .env files.

Dedicated items for API secrets, SSH keys and environment variables, with collections, search and encrypted content history. Personal experiments stay apart from team projects.

The Edit item dialog for the login Fortnox: type, title, username, password with a generator, website and authenticator key.
At the edges of your workflow

In the browser and the terminal.

Fill logins from the Chrome or Edge extension. Fetch a selected value from the command line, or run a process with chosen environment variables. Each client signs in on its own and can be ended under Devices.

Apps and clients under Settings, with the installed app, the browser extension download and the command-line client.
  • Password and passphrase generators
  • App secrets and PINs
  • SSH key generation
  • QR codes
  • File fingerprints
  • JWT inspector
  • .env editor

Good to know. Secrets you pass to a process are readable by that process. Keep them out of shell logs and untrusted commands. The JWT inspector reads what a token contains; it does not check that the token is genuine.

Start with a small team.

Try your first shared vault.

Create a free account with your email address. One team with up to 3 people is free; Pro is for larger teams.