Skip to content
All posts
Security3 min read

Deterministic vs vaulted password managers, honestly

A fair look at how stateless derivation and encrypted vaults actually differ: what each one protects, where each one breaks, and how to choose.

The MoolKey team
A row of secure archive cabinets with keyed wheel handles.

There are two real schools of password management, and most of the noise online confuses them. Let’s separate them cleanly and then talk about when each one is the right call.

Two architectures

A vaulted manager (1Password, Bitwarden, LastPass, Dashlane) stores an encrypted database of your credentials and syncs it across your devices. You unlock the vault with a master password; the provider holds the ciphertext.

A deterministic manager (MoolKey) does not store generated passwords or PINs. It recomputes each one from inputs plus a Master Key, every time, using a slow hash. Same inputs, same output, forever.

Everything else follows from that one difference.

What each one actually protects

Questions answered by vaulted and deterministic password managers
QuestionVaultedDeterministic
Where do generated credentials live?Encrypted, on a serverRecreated in the browser
What account data remains after a breach?The encrypted vaultNon-secret account metadata and security records
Can it work offline?With a cached vaultAlways, byte-identical
Is there account recovery?Usually yesNo, by design

Neither row is automatically “better.” They are answers to different fears.

Where vaulted managers shine

  • Autofill. A vault knows your exact stored string, so it can fill forms in one click and detect phishing domains.
  • Arbitrary secrets. Notes, recovery codes, credit cards, SSH keys: anything you can paste, a vault can hold.
  • Recovery. Forget your master password and most providers give you a path back in.

If those matter most to you, a well-run vaulted manager is a genuinely good choice. We mean that.

Where deterministic wins

The deterministic model avoids storing a generated credential list:

  1. No stored password list. A backend breach cannot expose a saved list of generated credentials, although account metadata and security records still exist.
  2. No generated-credential sync. Two devices compute the same answer independently. There is no credential copy to reconcile, corrupt, or fail to sync.
  3. No migration. Switching tools normally means exporting and importing a vault. With MoolKey there is nothing to move.
  4. True offline parity. The output on a plane is identical to the output online, because the network was never involved.

The honest caveats

We are not going to pretend the trade is free:

  • Forget the master key and it is gone. No reset, no support ticket that helps. That is the price of nobody, including us, being able to reach your secrets.
  • Rotation is per-account, not arbitrary. You bump a version integer to roll one password. You cannot pick “the exact string I want.”
  • Autofill is intentionally absent. MoolKey is a least-surface launcher, not a content script crawling your pages.

How to choose

Ask yourself one question: what keeps you up at night?

If it is the friction of daily logins, optimize for autofill and pick a vault. If it is the thought of a permanent encrypted copy of your credentials sitting on someone’s server, choose a deterministic model that recreates generated credentials instead of storing them.

For a line-by-line breakdown against named managers, see the full comparison. We flag every row MoolKey wins, and the two it doesn’t.

#comparison#threat-model#architecture

Make one account easier today.

Start with the password you keep reusing or the bank card that still shares a PIN. MoolKey is free, and you do not need to move everything at once.

Free forever Works offline Phone or computer