CarryPass is an open-source, client-side password manager and credential sharing tool built with strong cryptographic primitives and a zero-knowledge philosophy.
All logic runs in your browser. Nothing is sent or stored on servers β no telemetry, no tracking, no compromise.
π§ Inspired by modern cryptography and the principles of privacy, anonymity, and user sovereignty.
CarryPass is built on a simple principle:
βThe best way to protect user data is to never collect it.β
We designed CarryPass from the ground up to enforce:
- π» Client-only execution β No data is sent to any server
- π§ Zero-knowledge architecture β We canβt access your passwords, because we never see them
- π Deterministic password generation β Eliminates the need to store or sync vaults in the cloud
- π No telemetry, tracking, or analytics
- π Full offline support via PWA
We believe that privacy is not a feature β itβs a foundation.
Some browsers and password managers look for .well-known/change-password
to help users update their passwords in case of a breach.
CarryPass does not require or support this mechanism because:
- It does not store passwords at all
- Passwords are generated deterministically from user input
- There is no account or backend system to update
However, for full compatibility, we include a .well-known/change-password
file to indicate this clearly.
π See: https://carrypass.net/.well-known/change-password
-
β Deterministic password generation
Generate secure, unique passwords from:- Service name
- Master password
- User-defined strength and charset
- Salted and stretched with Argon2 + PBKDF2
-
π Encrypted vaults
- AES-GCM encryption with a new random nonce per edit
- Per-member, per-team, and admin-level vault separation
- Vaults exportable and re-importable with full integrity
-
π₯ Team support with TOTP
- Admin assigns members to teams
- Team credentials encrypted with deterministic CarryPass-generated passwords
- TOTP-based unlock and onboarding via QR code
-
π· QR onboarding and vault delivery
- Secure QR codes for device setup
- Encrypted secrets and keys included
-
π‘ Fully offline PWA
- Installable and functional even with no internet connection
- Inputs: Service name, master password, strength parameters (length, charset, iteration strength)
- Process:
Argon2
derives an enhanced salt using memory- and time-hard computationPBKDF2
derives a key using the Argon2 output + input stringAES-CTR
generates a deterministic byte stream from this key
- Output: The byte stream is sliced and mapped to user-defined character sets to generate a deterministic password
-
Admin, Member, and Team Vaults:
- Encrypted with AES-GCM for confidentiality and integrity
- Each vault uses a new random nonce on every edit or export
- Vaults are encrypted using keys derived from secure user input or generated passwords
-
Per-Member Vault Protection:
- Members finalize their access with a personal password (β₯128-bit entropy)
- This password is hashed via PBKDF2
- The resulting hash encrypts the member's vault
- Admin stores PBKDF2 hashes of member passwords to re-encrypt their vaults upon updates
- Each Team Vault is encrypted with a password generated deterministically using CarryPass:
- Service: team name
- Password input: a string like
GTHKSM
selected from a character set likeCCXCGTHKSM45103
- Strength: 45-character password, β₯100,000 + 103 PBKDF2 iterations
- This team password is then hashed and used to encrypt the team vault
- The resulting team vault key is stored in each assigned member's record
- Only assigned members can decrypt the team vault using their local access
- Each member has a unique TOTP secret generated at setup
- Onboarding devices scan the QR to persist the TOTP secret (encrypted in local storage)
- The app uses the current TOTP token to validate access to the encrypted team credentials
- On every admin vault export:
- All vaults (admin, member, team) are re-encrypted using new random nonces
- Keys are derived and stored deterministically to allow secure re-import
- Admin can revoke or rotate team access by modifying code maps and assigned member vaults
Include screenshots of the generator, vault viewer, QR onboarding screen, etc.
CarryPass is free to use under the MIT License for personal and non-commercial purposes.
If you wish to:
- Rebrand or white-label CarryPass
- Integrate it into a proprietary service
- Offer it as part of a commercial product
- Get dedicated support, SLA, or custom features
β‘οΈ Please contact us for a commercial license.
Visit the app at:
π https://carrypass.net
Works offline after first load (PWA installable).
You can run CarryPass locally using any static file server.
-
Clone the repo:
git clone https://github.com/racz-zoltan/racz-zoltan.github.io.git cd racz-zoltan.github.io