Akarguard Security Suite
A post-quantum, zero-knowledge password manager. Your vault is encrypted entirely on your device before it ever leaves — the server stores only an opaque, encrypted blob it cannot read.
AkarPass is the credential management component of the Akarguard security suite. It is designed for individuals and teams who require verifiable assurance that their passwords cannot be exposed through a server-side breach — because the server never holds plaintext to begin with.
All cryptographic operations are performed exclusively on the client using three independent layers: Argon2id for password hardening, ML-KEM-768 for post-quantum key encapsulation, and AES-256-GCM for authenticated vault encryption. Only the resulting ciphertext is transmitted to and stored on Akarguard infrastructure.
The implementation uses exclusively open-source, externally audited cryptographic libraries —@noble/post-quantum andhash-wasm. No proprietary cryptographic primitives are used.
"Zero-knowledge" means Akarguard is technically incapable of reading your vault contents. There is no back door, no server-side recovery key, and no mechanism by which Akarguard personnel can access your credentials. Even a complete database compromise yields only authenticated ciphertext with no decryption path.
All key material (master key, DEK, shared secret, private key) is zeroed from memory immediately after use.
Your master password is never used or stored directly. Argon2id derives a 256-bit master key using 64 MiB of memory, 3 iterations, and 4-way parallelism — making GPU and ASIC brute-force attacks computationally impractical. Parameters follow OWASP 2023 recommendations.
Full specification in ENCRYPTION.mdA post-quantum key encapsulation mechanism standardised by NIST in FIPS 203 (August 2024). Lattice-based design resists attacks from both classical and quantum computers. Implemented via @noble/post-quantum — zero transitive dependencies, externally audited.
Full specification in ENCRYPTION.mdEach vault is encrypted with a unique, randomly generated data encryption key (DEK) using AES-256-GCM — an authenticated encryption scheme that detects any tampering via a 128-bit auth tag. A fresh 12-byte IV is generated for every encryption operation; nonce reuse is structurally prevented.
Full specification in ENCRYPTION.mdML-KEM fallback mode
If ML-KEM WASM fails to load in restricted environments, AkarPass falls back to AES-256-GCM only — wrapping the DEK directly with the Argon2-derived master key. This mode is explicitly flagged in the stored payload ("fallback": true). AES-256 remains quantum-safe for data encryption; only the key-exchange layer is affected.
The full threat model — including adversaries considered, attack surfaces, and mitigations — is documented in SECURITY.md.
| Property | Implementation |
|---|---|
| Confidentiality | AES-256-GCM |
| Integrity & Authenticity | GCM 128-bit auth tag |
| Post-quantum key exchange | ML-KEM-768 |
| Password hardening | Argon2id |
| Forward secrecy | Per-vault fresh keys |
| XSS prevention | React + strict CSP |
| CSRF protection | Bearer JWT (no cookies) |
No master password recovery
By design, there is no server-side recovery mechanism. If you forget your master password, your vault data is permanently inaccessible. Store your master password in a secure backup location.
JavaScript memory hygiene is best-effort
JavaScript engines may internally copy buffers before zeroing. Key material is zeroed immediately after use, but complete erasure cannot be guaranteed due to garbage collection. The Tauri desktop application can leverage OS-level memory protections (mlock) for stronger guarantees.
Clipboard auto-clear after 30 seconds
Passwords copied to the clipboard are automatically cleared after 30 seconds via navigator.clipboard.writeText(""). This does not prevent clipboard managers from capturing the value.
All releases are available at github.com/AkarGuard/AkarPass/releases.
Next.js 15 — works in any modern browser
Tauri 2 — native offline-capable client
Manifest V3 — auto-fill across sites
React Native mobile application (iOS & Android) is under active development and not yet available for release.
AkarPass processes personal data in accordance with the Akarguard Privacy Policy. By its zero-knowledge design, server-side personal data is limited to your account email address and an authenticated ciphertext — Akarguard cannot associate vault contents with any individual.
Use of AkarPass is subject to the Akarguard Terms of Service and Cookie Policy. Security certifications and compliance posture are detailed on the Compliance page.
Because vault contents are encrypted before transmission, Akarguard is technically unable to fulfil data subject access requests with respect to vault contents — there is no plaintext to disclose. Account metadata (email address, account creation date) is subject to standard GDPR data subject rights. To exercise your rights, contact privacy@akarguard.net.
If you discover a security vulnerability in AkarPass, please report it responsibly. Do not open a public GitHub issue.
Full disclosure policy is documented in SECURITY.md.
Ready to get started?
Download AkarPass v0.1.0 from GitHub Releases or explore the source code.