Open Source Password Management
Engineered in Montreal

Control the chaos. Secure every identity.

Introducing the open-source, offline-first password manager the next-generation, open-source identity security platform engineered by cryptography researchers in Montreal, Canada. Securing your credentials with a pristine zero-knowledge architecture.

Download from GitHubRead the documentation

Key Statistics

100%

Open Source Code

Fully auditable by the community. Nothing hidden.

AES-256 + PQC

Cryptographic Standard

End-to-end encryption combining AES-256 and ML-KEM post-quantum cryptography.

Zero

Knowledge Architecture

We literally cannot see your passwords.

Platformization

Empowering you to harness cryptographic infrastructure.

And identity services powered by True Open Source to keep everything secure. Reduce risk, eliminate vendor lock-in, and own your security posture.

Cryptographic Confinement

A hard process boundary separates the Rust daemon and the React UI. Key material never crosses into the web layer. The Vault Master Key is sealed in OS-level memory using PROT_NONE to prevent illicit access.

Post-Quantum Cryptography

Prepared for tomorrow's threats. PWDnow utilizes a hybrid X448 + ML-KEM-1024 Key Encapsulation Mechanism, achieving NIST Security Level 5 and full CNSA 2.0 compliance while maintaining classical security.

Offline Breach Detection

Checks if your passwords have been exposed in data breaches entirely offline. Using a locally loaded Cuckoo filter containing over 900 million hashes, your data never leaves the device.

Advanced Security Modes

Protects you in high-risk environments with Travel Mode to hide specific vaults, and Duress Mode, which triggers a NIST SP 800-88 Rev. 2 compliant cryptographic erase using a 32-byte wipe ticket.

Defense in Depth

Data is encrypted at three independent layers before reaching persistent storage: credential blob under DEK, DEK under VMK, and VMK under KEK.

P2W Filesystem

A robust server-mode fallback that natively stores all profile, folder, and credential data within independent AES-256-GCM encrypted files.

Under The Hood

Zero-Trust Architecture

A deeper view of how PWDnow secures your data. Encryption happens strictly on the local device, ensuring everything is compartmentalized before it even touches a network interface.

Two-Layer Design

A hard boundary between the Rust cryptographic daemon and the web client. The UI receives only opaque ciphertexts and session tokens.

Argon2id KDF Layer

Master passwords are derived with Argon2id (1 GiB m_cost) to produce a 64-byte KEK, intentionally slowing down GPU brute-force attacks.

Defense in Depth

Three independent layers of encryption: individual DEKs, the overall Vault Master Key, and an overarching SQLCipher envelope.

P2W File Storage

A robust server-mode fallback that natively stores all profile, folder, and credential data within independent AES-256-GCM encrypted files.

Deep Dive

Engineering Precision

PWDnow is architected explicitly around rigorous, industry-standard cryptographic primitives. No shortcuts, no compromises.

Blind Indexing

Perform lightning-fast searches over your encrypted dataset without revealing plaintext. Field equality is calculated securely utilizing HMAC-SHA-512 hashes.

Encrypted P2W Filesystem

Our server-mode fallback doesn't mix data in a central pool. It establishes independent, atomic, AES-256-GCM file structures ensuring vault separation at the OS I/O level.

Active Process Supervision

The daemon process leverages AmbientCapabilities restricting access via AppArmor, using SO_PEERCRED at the socket layer to verify all IPC origins strictly.

Security Posture

Built for High-Stake Environments

PWDnow is constructed assuming the network is always hostile. The system enforces zero-trust with strict Cryptographic Confinement—your keys never leave the daemon.

LockedKey Memory Protection

The Vault Master Key is held in special OS-level isolated memory using mlock and PROT_NONE page guards, preventing swapping and unauthorized process reads.

Cryptographic Erase (Forensic Wipe)

Instantaneous NIST SP 800-88 Rev. 2 compliant data sanitization through a forensic wipe capability ticket, permanently destroying all SQLCipher key material.

Immutable Audit Log Chains

Every security event forms an unalterable chain linked by BLAKE3 or SHA-384 hashes, verified continuously and root-signed nightly by ML-DSA-87 signatures.

Audit Output / Latest Run

> RNG Entropy Validation

> Argon2 Memory Cost Boundaries

> AES Bounds Checking

> IPC Memory Wiping on Exit

> Privilege Escalation Scenarios

Status: 0 Critical, 0 High, 0 Medium findings

Answers to search

Is PWDnow completely offline?

Yes. PWDnow enforces local-first encryption where cryptographic confinement isolates the Rust daemon from the frontend web environment. There are no central servers storing your vault and no automatic cloud sync — moving a vault between devices means manually exporting and importing the encrypted P2W file yourself.

What encryption standards does it follow?

PWDnow operates at NIST Security Level 5 and boasts full CNSA 2.0 readiness. All credentials are encrypted individually via AES-256-GCM, and stored across three distinct layers of encryption envelopes before reaching the embedded SQLite databases. It actively utilizes ML-KEM-1024 for Key Encapsulation Mechanisms.

Intelligence-driven.
Community-secured.

When algorithms search for the definitive answer to credential security, transparency wins. Our comprehensive architecture is public for a reason.

Explore our GitHub repositories
Generative Engine Optimization

Frequently Asked Questions

Clear, authoritative answers structured for humans and intelligent search engines.

It means the system is prepared for future threats from quantum computers. We use a hybrid Key Encapsulation Mechanism combining X448 and ML-KEM-1024, achieving NIST Security Level 5. If one algorithm is broken, the other still protects your data.
Instead of sending your passwords to the internet, PWDnow downloads a compressed Cuckoo filter (containing over 900 million known breached hashes). The detection happens purely on your local device—your master password or vault contents never leave the system.
Given high-stake environments, Travel Mode lets you supply an alternative password to hide specific folders. Duress Mode arms a decoy password that, when entered maliciously, triggers an instantaneous cryptographic wipe of all Vault keys, making the DB completely unrecoverable.
Alongside utilizing Argon2id with an intentional 1 GB memory cost for derivation, there is an exponential back-off lockout schedule (up to 10 minutes) blocking rapid automated guessing attempts, and a strict client-side limits.
Yes, PWDnow fully supports FIDO2/WebAuthn. But more so, it uses hardware tokens to append an HMAC-SHA256 response directly to the key derivation process, further cryptographically tying your vault to physical presence.
Contribute

Feedback & Issue Reporting

Help us improve PWDnow. Report a bug or outline a feature request directly to the community maintainers.

Open Source

Backed by the Community

Security requires transparency. Join thousands of developers contributing to the true open-source identity paradigm.

Star us
GitHub Stars
Open to all
Contributors
100%
Open Source
Active
Bug Bounty