AuthPass

1Password locks encrypted credentials into proprietary cloud infrastructure and recurring monthly subscriptions. AuthPass keeps secrets in standard, open KeePass KDBX vaults that live on local storage or your preferred WebDAV and cloud providers. The desktop application pairs client-side cryptography with Flutter-driven multi-platform support, giving engineers complete custody of their databases across Linux and mobile devices.

Why AuthPass instead of 1Password

Adopting 1Password means storing vault metadata and encrypted credentials on proprietary infrastructure under recurring subscriptions. For engineers focused on privacy and control, this creates vendor lock-in and external compliance risk. AuthPass treats password management as a file-level problem: credentials reside in standard KDBX 3.x and KDBX 4.x files encrypted with ChaCha20 or AES-256 and Argon2 key derivation. Cryptography runs strictly in workstation memory, ensuring master passwords and secret keys never contact external servers.

The trade-off balances convenience against autonomy. 1Password offers turnkey browser autofill and administrative team controls. AuthPass lets developers sync databases across machines using WebDAV, Nextcloud, or consumer clouds without subscription gates. Migrating from KeePassXC requires zero export overhead because database files remain identical. However, synchronization operates at the file level rather than through live streaming; while AuthPass detects remote edits to merge changes, concurrent saves across devices can still generate conflict copies that require manual review.

What it does well

• Standard KDBX format: Reads and writes KDBX 3.x and KDBX 4.x databases with Argon2 derivation, maintaining total compatibility with KeePassXC.
• Self-hosted synchronization: Syncs directly across WebDAV endpoints, Nextcloud, Dropbox, and Google Drive without proprietary vault middleware.
• Multi-vault support: Opens and manages several .kdbx files at once, allowing clean isolation between personal, client, and staging credentials.
• Integrated TOTP tokens: Stores two-factor secrets and generates rotating time-based one-time passwords within credential entries.
• Keyfile authentication: Protects sensitive databases with composite credentials, combining a master passphrase with an external file key.