Main vault
Search and organize passwords, notes, files, folders, and favorites.
Git-native encrypted vault
GitPassword
A desktop GUI vault for passwords, notes, and files, encrypted locally and stored in the Git repository you choose.
Works with the Git remote you already use
GitHub
GitLab
Bitbucket
GiteeSelf-hosted Git
Local repository
Core Concept
A Git-powered encrypted vault for individuals and small teams
Encrypt locally, then sync through a Git repository you control. Argon2id and AES-256-GCM protect passwords, private notes, and confidential files—without a centralized cloud vault or a recurring SaaS subscription that holds your data hostage.
Modern cryptography
Argon2id key derivation and AES-256-GCM encryption are designed to resist offline brute-force attacks and keep vault contents confidential.
You control the data
Keys and plaintext stay on your device. Your Git host stores encrypted blobs—not a vendor-hosted vault you lose if a cloud subscription lapses.
Core Features
One vault for passwords, notes, and files
Store credentials, private notes, and confidential files in a Git-backed vault, encrypted locally on your device.
Passwords and credentials
Password vault
- Structured credential fields: Accounts, passwords, website URLs, TOTP codes, SSH notes, and custom fields in one place.
- Built-in password generator: Create strong passwords with custom length and character sets, so you can stop reusing weak ones.
- Instant search: Search by title, username, or website—including pinyin—to find credentials quickly.
Data Sovereignty
Your data stays under your control
You are not locked into a cloud vendor. Keep the vault local, on self-hosted Git, or on a major Git host—and export or migrate whenever you want.
Local or remote Git, your choice
Keep data on this machine or sync to GitHub, GitLab, Bitbucket, Gitee, or your own Git server. Whoever holds the repository holds the encrypted vault.
Import and export in the open
Export plaintext when you need a backup, audit, or migration. No proprietary lock-in if you stop using the app.
Compatible with pass
Import and export the pass (password-store) format so you can move in or out of the Unix password ecosystem.
Why Choose GitPassword
Why developers pick GitPassword
If you do not want a centralized commercial password cloud, GitPassword keeps encryption local and uses Git for history and sync.
Typical cloud password manager tradeoffs
What GitPassword does instead
Centralized breach risk: a vendor cloud is a single target; a weak master password can be attacked offline if the vault is stolen.
Local cryptography: Argon2id (memory-hard) plus an optional Vault Secret, so offline guessing is much harder even if encrypted data leaks.
Recurring SaaS fees: monthly or yearly billing, and some products restrict access if you stop paying.
GUI workflow
A real desktop app over an encrypted Git vault.
View the vault list, repository setup, and conflict recovery flows from the GitPassword desktop app.
Repository setup
Clone or connect the Git repository that will hold your encrypted vault.
Conflict recovery
Use Git history and sync state when multiple devices change the vault.
FAQ
GitPassword questions, answered plainly.
Short answers for security, Git sync, recovery, platform support, and Microsoft Store distribution.