KeyDBX — free KeePass-compatible password manager for iPhone and iPad

[Hank]

Hi everyone,

I'm the developer of KeyDBX, a free KeePass-compatible password manager for iPhone and iPad. I wanted to keep using my KDBX file on iPhone, with AutoFill and passkeys, without an account or a server in the middle.

Your database is decrypted only on your device. I run no servers and never see your data. The app has no analytics, ads, tracking, or third-party SDKs. It connects to the network only when you use Dropbox, and only to Dropbox.

What it does

• Reads and writes KDBX 4.0 and 4.1, with a master password and key file
• Saves only what you edited, so KeePass and KeePassXC keep opening the same file
• AutoFill for usernames, passwords, and verification codes in Safari and other apps
• Saves new passwords when you create an account or change a password (iOS 26.2 or later)
• Creates and uses passkeys, in a format compatible with KeePassXC 2.7.12 or later
• TOTP codes, including Steam codes, set up from a QR code or an otpauth:// link
• Opens databases on Dropbox directly, or through the Files app, including iCloud Drive
• Edits a Dropbox database offline and uploads the changes when you are back online
• Face ID unlock, auto-lock, entry history, and a password generator

Not supported

• KDBX 3.1 and KeePass 1.x databases

Not supported yet

• YubiKey and HOTP
• Creating a new database: create it with KeePass or KeePassXC on your computer first

It requires iOS 26 or later.

• App Store: https://apps.apple.com/us/app/keydbx/id6825241121
• Website: https://keydbx.lab076.dev/en/

If you try it with your own database, I'd like to hear what breaks. Please keep a backup of your database while you test.

[Paul]

Source code?

Why is it better than the other (choose a number) of KeePass compatibe apps?

When both sides change, Dropbox keeps a separate copy and no version is overwritten

Does it support record level sync - like KeePass?
How do you merge the changes if dropbox has a separate copy?

cheers, Paul

[Hank]

Hi Paul,

Thanks for the questions.

Source code

It's closed source for now. I understand that matters for a password manager, so here is what I can say: the app makes no network connections except to Dropbox, and only when you use Dropbox. It contains no third-party SDKs. You can check the network part yourself with a proxy or the iOS App Privacy Report.

Why use it over other apps

I'm not claiming it's better. The main reason I built it is that I wanted Face ID unlock for my KeePass database, including in AutoFill, without paying for it. These are the choices I made:

• Everything in the app is free today, including Face ID, writing, AutoFill, passkeys, and Dropbox. There's no subscription and no in-app purchase. In the future I may charge for new extra features, or add a way to donate, but Face ID unlock will stay free.
• Saving changes only what you edited. Unknown XML elements, attributes, and header fields are kept as they are, so data written by KeePass, KeePassXC, or plugins survives a save.
• It talks to the Dropbox API directly, so it doesn't need the Dropbox app, and you can edit offline and upload later.

If one of the other apps already works for you, there may be no reason to switch.

Sync and conflicts

No, there's no record-level sync. It uploads with Dropbox's revision check, so it never overwrites a newer version on Dropbox. When both sides have changed, Dropbox saves the app's version as a separate "conflicted copy", and the app downloads the Dropbox version and tells you the name of the copy. You then merge the two files on your computer with KeePass (File > Synchronize > Synchronize with File) or KeePassXC (Database > Merge From Database).

Record-level merge on the device would be the better solution. I'll consider it, but there's no plan or date yet.

cheers,
Hank