Offline-first encrypted vault for credentials and personal secrets, built with .NET, Clean Architecture, and security-focused defaults.
- Security-first local vault: credentials are encrypted at rest and unlocked only with a master password.
- No cloud, no backend, no sync service: your vault stays on files you control.
- Production-minded engineering: layered architecture, tests, release artifacts for Windows and Android companion.
Typical user flow (desktop + companion):
- Create a new vault file and define a master password.
- Unlock the vault and create or edit credential entries.
- Search and filter entries instantly.
- Copy a password to clipboard with auto-clear protection.
- Save the encrypted vault file and lock manually or by inactivity timeout.
- Optionally transfer the vault file to Android and unlock with password plus biometric authentication.
- Vault creation and unlock with master password
- Full entry CRUD (name, username, password, URL, notes, tags)
- Encrypted embedded image and PDF attachments (up to five 5 MiB attachments per entry)
- Fast search and filtering
- Clipboard copy with auto-clear policy
- Auto-lock after inactivity
- Manual transfer workflow to companion Android app
- Android companion provides read-only entry access, including attachment viewing
- Markdown import support
- Key derivation: Argon2id
- Encryption: AES-GCM (authenticated encryption)
- Integrity and tamper resistance: authentication tag + protected header usage
- Master password is never persisted
- Keys live in memory only while unlocked (best effort cleanup)
- Single encrypted file designed for backup and restore
- Active malware or keyloggers on the host
- Cloud sync and multi-device conflict resolution
- Enterprise password manager feature parity
The solution follows a layered approach inspired by Clean Architecture:
Vault.Domain: entities and business rulesVault.Application: use cases and application orchestrationVault.Crypto: Argon2id and AES-GCM implementationsVault.Storage: encrypted file format and disk persistenceVault.App: MAUI + Blazor Hybrid UI
For the full design rationale, see:
- Windows 10+ for desktop execution
- .NET SDK from
global.json - Optional for Android companion build: Android workload and SDK
git clone https://github.com/carlos-aisa/LocalSecureVault.git
cd LocalSecureVault
dotnet restore LocalSecureVault.slndotnet test tests/Vault.Tests/Vault.Tests.csproj -f net8.0 -c Releasedotnet run --project src/Vault.App/Vault.App.csproj --framework net8.0-windows10.0.19041.0More commands are available in docs/build-and-publish.md.
- Open Releases.
- Download:
LocalSecureVault-windows-vX.Y.Z.zipfor desktopLocalSecureVault-companion-android-vX.Y.Z.apkfor Android companion
- Validate the SHA256 checksums from the
SHA256SUMS.txtasset. - Extract and run the Windows app, or sideload the APK on Android.
- Automated CI build and test validation on push and pull requests
- Dedicated security analysis with CodeQL
- Security-focused tests for wrong-password, tamper detection, and corruption paths
Reference docs:
- Windows desktop app: feature-complete for MVP
- Android companion: existing vault usage flow implemented
- Signed Windows installer (MSIX)
- Optional secure export/import profile presets
- UX improvements for large vault browsing
- Expanded fuzzing and corruption resilience tests
- Contribution guide: CONTRIBUTING.md
- Security policy: SECURITY.md
- Changelog: CHANGELOG.md
This project is licensed under the MIT License. See LICENSE.