Verdant Vault

Verdant Vault is a password manager with no account behind it. Your vault is a single encrypted file on the device; if you want it on more than one device, you point the app at storage you already control and it syncs the file there. Nothing about the design requires trusting Forgeline with your data, which is the point — there is no server to breach because there is no server. It handles passwords, passkeys, TOTP codes, and secure notes, and it plugs into Android's autofill and credential manager frameworks so it behaves like a first-class option in the system picker.

This suits people who are comfortable with the trade: you own the file, so you own the backups. If you lose the vault and the passphrase, nobody can recover them, and there is deliberately no reset flow. People who would rather have a vendor hold a recovery key should choose a hosted manager instead, and that is a legitimate choice rather than a lesser one.

Forgeline authorizes APKBrowse to host the stable APK directly, served through a short-lived signed URL with resumable byte ranges. The same artifact is on Google Play and, built independently from source, on F-Droid — worth knowing because the F-Droid build carries F-Droid's signature, not Forgeline's, so the two cannot update over each other. Verdant Vault is also independently audited before each major version, and the audit reports are published rather than summarized.

Before installing, decide where the vault file will live and how it gets backed up, because the app will not make that decision for you. Version 3.1.2 requires Android 9.0 or newer, largely for the credential manager integration. The permission list is short by design: no internet permission at all in the base build, which is unusual for a password manager and means sync runs through the system document provider rather than the app's own network stack. If you are rolling back from 3.1.2 to 3.0.0, note that 3.0.0 cannot read vaults that have been upgraded to the current file format.