Everything you need to get unstuck.
Guides, references, and answers to the questions teams ask most. Start with the CLI — it's the fastest path to your first secret.
# install (macOS, Linux, Windows) $ npm install -g bippass # point it at your server and sign in $ bippass login --server https://your-bippass $ bippass use acme/api/production ✓ logged in · you're ready to go
Browse by what you're trying to do.
Developer guide
Every command, flag, and example: install and sign in, pull secrets into a .env, pin a project's scope, and keep secrets out of git.
CLI reference
Getting started
Install the CLI, log in, and create your first workspace and project.
Managing secrets
Set, read, and share secret values across environments — and keep them out of .env files.
Teams & access
Add people to a workspace, and give them the keys to a project.
Devices & trust
Why a new machine has to be approved, and what to do when a login stops.
Billing & plans
Understand usage limits and manage your subscription.
Security model
How zero-knowledge encryption works, and what the server can and cannot see.
Managing BipPass in the browser
A tour of the app: signing in, unlocking, and where every management task lives.
Managing teams & groups
Create a team, add and remove members with a role, and clean up when people leave.
Members & access policies
Invite people to a workspace, set their role, and grant precise access to one resource.
Approving new devices
Let a teammate’s new machine in — or turn the requirement on for your workspace.
Projects & secrets in the browser
Create a project, store secrets, and reveal a value — all encrypted in your browser.
Talk to a human.
If the docs don't cover it, email support@bippass.dev and a real engineer will get back to you. For security disclosures, use security@bippass.dev.