Zero-knowledge secrets

Secrets that never leave your control.

End-to-end encrypted secret management for engineering teams. Encrypted on your machine, opaque to our servers — and never written to a .env file your AI coding agent can read.

# set a secret — encrypted before it ever leaves the machine
$ bippass set DATABASE_URL postgres://… --env production
 encrypted & stored · server sees ciphertext only

$ bippass run --env production -- npm start
 injected 14 secrets · lease expires in 1h
Why BipPass

Everything a secret needs, and nothing it doesn't.

A single system for storing, sharing, and rotating secrets across every environment — without ever trusting the server with plaintext.

End-to-end encrypted

Values are sealed on the client with X25519 + secretbox. We store versioned ciphertext, never plaintext.

Zero-knowledge

Keys derive from your passphrase and never leave the device. A breach of our database reveals nothing.

Fine-grained access

Scope secrets to environments, teams, and roles. Request, approve, and audit every grant.

Automatic rotation

Rotate credentials on a schedule or on demand. Old versions stay recoverable, new ones roll out instantly.

Built for the CLI

Inject secrets into any process with one command. No plaintext on disk, no secrets in your shell history.

Complete audit trail

Every read, write, and reveal is recorded. Know exactly who touched what, from which device, and when.

AI agents

Your coding agent can't leak what it never sees.

AI assistants read your repository — that is the entire point of them. A .env file is just a file, and everything in it is one command away from a model's context window, a bug report, or a pull request. BipPass never writes one.

# what an agent finds when it reads the repo
$ cat .env
cat: .env: No such file or directory

# secrets arrive in the process, not on the filesystem
$ bippass run --env production -- npm start
 injected 14 secrets · nothing written to disk
  • Nothing on disk to read

    bippass run decrypts in your terminal and passes values straight into the process environment. No .env is written, so there is no file for an assistant to open, index, or paste into a prompt.

  • Nothing in git to commit

    bippass scan and the pre-commit hook catch a secret before it reaches a commit — including the ones an agent helpfully hardcoded while fixing something else.

  • Nothing on our side to hand over

    The server holds ciphertext and no key. Whatever an integration, a support request, or a subpoena reaches for, the plaintext is not there to give.

Get started

Bring your secrets under control today.

Create a workspace, invite your team, and move your first environment in minutes. Free to start, no card required.