Android · Chrome

Strongroom

A password manager written entirely in my own code

KotlinReact NativeTypeScriptAndroid AutofillChrome extensionCloudflare Workers

View sourceChrome extension

Why I built it

I wanted my passwords out of Google and out of every other company's hands. I had four reasons. A company could read them, whatever it says about encryption. A breach could leak them. A locked or closed account would take every password with it. And I wanted to own the thing that holds them.

The last reason decided it. Strongroom replaces Google Password Manager on my phone and in Chrome.

What it does

How it works

The master password goes through Argon2id to make a key that unlocks the vault key, and every record is encrypted with AES-256-GCM under a fresh random nonce. Changing the master password re-wraps one key and touches nothing else. On Android the vault logic is Kotlin. The Chrome extension is a TypeScript implementation of the same vault format.

The sync server sees record IDs, sizes and timestamps, never names, sites, usernames or passwords. Every device keeps a full local copy, so losing the server would cost sync, not passwords.

Copied passwords are cleared from the clipboard after 30 seconds, even if the system kills the app in the meantime.

Why write a password manager when Bitwarden and KeePass exist?

They're good, and self-hosting Bitwarden through Vaultwarden was the obvious option. I turned it down on purpose. The point was that everything holding my passwords is code I wrote and can read end to end.

Isn't writing your own password manager risky?

Writing your own cryptography would be, so I didn't. The cipher and the key derivation come from audited libraries. What I wrote is the vault format, sync, autofill and the apps around them, and the design was written down and reviewed before any of it was built.

Where it stands

Version 0.2.1 runs on my Android phone with sync, alongside the Chrome extension. An iPhone app and a Safari extension wait on a paid Apple developer account.