Note

Why Oak Keyring exists

Passwords are durable private infrastructure. The tool that holds them should make ownership, recovery, and sync boundaries visible instead of hiding them behind a service promise.

Local ownership before convenience

Convenient password tools often turn into another account users must trust. Oak Keyring starts from the opposite direction: the encrypted vault is local, the key lifecycle is explicit, and Google Drive sync is optional encrypted transport.

The hard cases drive the design. A user should be able to recover after loss, move from an existing password store, export before leaving, and understand what role sync did or did not play in each step.

The project is still in first-preview status, so the public site avoids stable-release, audit, and production-readiness claims. That restraint is not the reason Oak Keyring exists; it is how the website stays honest while explaining the product's real reason.