Ownership
The starting point is simple: password data should stay with the user by default, not in somebody else's cloud vault.
projects / passary
Passary Offline password manager
A local-first password manager built around ownership, isolation, and zero-knowledge handling.
This is one of the product pages behind the broader projects overview. The public site is passary.com.
Product type
Offline password manager
Default model
Local-first
Security direction
Argon2id + AES-256-GCM
Public site
passary.com
Isolation
A smaller attack surface matters. Local-first direction and tighter boundaries are part of the product logic, not decoration.
Practical security
Argon2id and AES-256-GCM are part of the current direction because the product needs a serious baseline, not vague privacy language.
Why it exists
The default never felt right
The original problem was straightforward: cloud-first password management became normal, but that never felt like the right default to me.
I care more about ownership, tighter boundaries, and fewer unnecessary assumptions about where sensitive data should live.
That is what shaped Passary. The product direction is not about flashy password-manager marketing. It is about control, reasonable defaults, and practical security decisions.
Current focus
Browser extension direction
Desktop and mobile product decisions
Longer-term self-hosted and sharing options
Keeping the core model simple before adding surface area
Next step