Selfhosted

Vaultwarden handles the syncing for me.

However I do export backups on both my phone and laptop just in case.

On Android I use KeePassDx Syncthing-Fork. The handover was rough but the maintainer of the Play version joined researchxxl's team. Many on the Syncthing forum seem to have accepted research which is good enough for me. Also, KeePass's database in encrypted so no danger there.

I use Vaultwarden. Each synced device is a backup, so there's no real need to keep anything further than that, but I do keep one backup of the server files anyway.

Vaultwarden with the Bitwarden Android app and browser extension for my desktop. I already have a solid system for backing up the important data for all my docker containers. As soon as I added it, it was automatically added to that process.

My spouse has an account so if I die she can gain access to my passwords with a simple request. That's function is important to me.

bitwarden

seems odd you say how cumbersome it is to manage and backup (not an issue I've faced though) and yet you are using some cumbersome alternative ?

I use KeepassDX syncing via Nextcloud, works flawlessly. I also used to use Keepass2Android, also works very well.

Can you elaborate on the "nextcloud doesn't support 2-way syncing on android" statement? I can sync my Keepass database back and forth without issues.

Vaultwarden, no question. When I used KeePass, I had Synology Drive which worked well to sync.

KeePass2Android:

If you're using a keepass database, Keepass2Android can natively sync with many cloud options including self hosted and generic ones, even without specific "companion" apps. That's what I use. In my case, it's backed by my NextCloud, but it used to be Google drive before.

Just also sync the file on your PC, merging changes from different clients is part of the keepass database format and "just works".

Also VaultWarden works great if your can self host it, but I prefer keepass for a variety of features and integrations.

I just switched back to vaultwarden. My vaultwarden data is backed up as part of my nightly backups. Desktop and android use bitwarden clients. Seeing as https://codeberg.org/small-hack/open-slopware/src/branch/main states keepassxc is using AI to create PRs. Otherwise you could see how seafile might work for you to sync your keepass db. If you are on android with termux you can run syncthing in termux which also works and avoids the issue with the syncthing fork

Bitwarden.

Paid. Not because I need the added paid features, but because I value it and want to show my appreciation for the developers.

Paid bitwarden.

I use Nextcloud + KeepassDX on android and KeepassXC on PC. Have never had an issue. Changes on desktop/phone are propagated virtually immediately across devices.

Selfhost Vaultwarden. Browsers Bittwarden extensions and Android with Keyguard app.

Vaultwarden

Syncthing-Fork is still untrustworthy since the disastrous handover

Maybe I'm OOTL on this?

I thought everyone concluded that it was poorly communicated but ultimately no indication of any foul play.

I use keepass2android and "sync" via its native WebDAV support with my nextcloud instance as the source. Been working great forever.

Keepass + syncthing = win

I migrated out of keypass and into vaultwarden, not looked back since.

Personally, I use Keepass with syncthing and it works fine enough. If you don't really trust the new person behind Syncthing-Fork, you could always install the older version before the handover (I think before v3.4?).

If you really don't trust syncthing at all, you could just manually back it up. New passwords aren't made every day, so you could just copy the passwords database over between your devices whenever there's a change. That's what I did before I heard about syncthing, and is what I do with my music still, since I don't regularly update what music I listen to.

Passwords Nextcloud app

I use passwordstore.org which is basically a bash script that wraps GPG; but there is an Android client as well.

Everything is stored in encrypted files tracked by git. Files are synchronized by git/SSH to a server I run.

Keypass with the vault loaded onto a free OneDrive account.

Just back it up occasionally.

I share your sentiment about Syncthing-Fork and the botched handoff to researchxxl. I have yet to implement the Termux-based workaround that allows me to use Syncthing from the browser without the Android app / wrapper. It looks pretty clean as it's just pure Syncthing with a little starter script.

Keepass for Android, my database is stored on OneDrive. Easy access on my win pc and android (KPA has built in sync for many cloud storage providers)

I don't update my Keepass db often enough to need syncing. Maybe every other week or so I just pull the latest backup from my desktop from backblaze b2 to my phone, or if I change something on the phone, I send a copy to myself using signal "note to self." Then I manually merge the databases.

Pretty low-tech.

OpenCloud seems promising. It's a fork of ownCloud from former developers of ownCloud, lighter weight than NextCloud, it uses flat files to store data rather than a DB, and it has an Android client on F-Droid (and Google Play).

smbsync2

I still think a syncthing client of some form is ideal. As someone else mentioned there is the option of using the Syncthing Tray devs experimental android build. To avoid issues with sync-conflicts / maintain high-availability access to the most recent file, I sync the databse to a raspberry pi with the encryption option selected (not that the pi is untrusted per se, but it is a device that doesn't need access to the file, it just serves the most recent changes to other devices since often my laptop / phone / desktop are not all on at the same time).