Vaultwarden handles the syncing for me.
However I do export backups on both my phone and laptop just in case.
this post was submitted on 15 Mar 2026
54 points (92.2% liked)
Selfhosted
58609 readers
1136 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 2 years ago
MODERATORS
Do you do it manually into e.g. protected json, or to a normal zip (the former doesn't support attachments as far as I know)? Or have you found a way to do it automatically? One con that I've read about this is that backups from one version is not guaranteed to work on another version. Thanks.
Well with Vaultwarden any synced device is a complete backup. So you don't need to worry about version issues.
load more comments
(2 replies)
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.
load more comments
(8 replies)
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.
Yeah, that's a good point. There are still a few cons though:
- If the server goes down (or your internet connection goes down), you can't add entries to your database. Local changes aren't allowed.
- Bitwarden doesn't support supplementing your passphrase with a key file.
- The Bitwarden clients aren't enitrely FOSS as far as I understand, the SDK used has a non-free license.
There are pros and cons in both alternatives, and there is unfortunately not a perfect solution. I like the idea and philosophy behind the KeePass format, so the increase in syncing complexity is worth it (for now at least).
It's true re adding passwords while the server is offline, but my server runs 24x7 and it's never down for more than a few minutes. If it goes down, I fix it. I also backup the encrypted DB regularly to cloud, so there is little risk of data loss. I am a very satisfied Vaultwarden user. Especially because it allows password sharing with my family. Everyone has an account.
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 ?
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.
load more comments
(1 replies)
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.
load more comments
(9 replies)
Vaultwarden, no question. When I used KeePass, I had Synology Drive which worked well to sync.
load more comments
(2 replies)
Paid bitwarden.
I use Bitwarden too. I now use the paid version (which is incredibly cheap) but I was able to sync between Android and PC without the paid for version iirc
The only (known to me) perk of the paid version is the encrypted storage (and probably the org feature).
So yeah. I see it more of a donation/appreciation than a service fee.
But the recent peice increase stung a bit.
load more comments
(1 replies)
Bitwarden.
Paid. Not because I need the added paid features, but because I value it and want to show my appreciation for the developers.
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.
KeePass2Android is a fantastic project. I've been using it for 10+ years on my Android devices. Every once in a while I'll try a different variant, like KeePassDX, but I always return to the spartan look of KP2A. It "just works", with no extra fluff.
merging changes from different clients is part of the keepass database format and “just works”.
This is the best thing about KeePass in general.
I use keepass2android and "sync" via its native WebDAV support with my nextcloud instance as the source. Been working great forever.
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.
load more comments
(1 replies)
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.
Correct.
That conversation has finished, the dust has settled and syncthing-fork is fine.
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
i self host, and back up, vaultwarden, and use bitwarden in browser and android.
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.
Selfhost Vaultwarden. Browsers Bittwarden extensions and Android with Keyguard app.
Vaultwarden
KeepassXC and Nextcloud. Been working fine for years.
Same setup here. Worked for years and I've no plans to switch. As long as Nextcloud is up, bidirectional editing is simple. Trouble comes when one of the clients edited the KeePass file and can't sync.
load more comments
(1 replies)
Nextcloud and favorite the file. It's worked reliably forms for years. I don't need to create new passwords on my phone, though.
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.
I actually used pass many years ago and I quite enjoyed it, except for the fact that the entry names are presented in clear text. You'd also have to manage your GPG secret which I'm not a fan of (in fact, my password manager is how I usually manage GPG and SSH keys in the first place). On the other hand, I guess you should keep a key file on each device on top of a passphrase even if you use a KeePass database, so I guess that point is moot. There are also no good way to include attachments. At that point Vaultwarden feels more convenient, but the more I'm thinking about it, the more I'm warming up to the idea. We'll see, maybe I'll give it a shot again.
Thanks for sharing your thoughts!
load more comments
(1 replies)
load more comments
(3 replies)
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.
Keepass + syncthing = win
I don't update my 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.
Yeah, I have a tendency to modify my database quite often. I often make new accounts, add attachments, modify passphrases on older accounts, etc. I modify it several times a week. I might be an outlier, and in that case I understand why people don't consider this to be a huge problem haha.
load more comments
(1 replies)
I've been using KeePass for almost 20 years now, used to host the database on Google Drive. I started using Syncthing about a year or so ago, including Syncthing-Fork on my Android devices. It's nearly flawless - I sync the database across 6 devices (two phones, two laptops, gaming PC, NAS [which is backed up regularly]), so there is the occasional conflict maybe once every few months, but I think that's more user error than anything else. It's fairly easy to resolve since Syncthing clearly labels the affected file.
It's very important to remember that "Syncthing-Fork" IS NOT the official Syncthing project. Syncthing-Fork uses Syncthing under the hood while providing a mobile-friendly wrapper.
Edit: Catfriend1 (the original maintainer of Syncthing-fork) recently put in their 2 cents.
TL;DR - The new dev is fine. For me personally, the fact that 1) devs from both F-Droid and Syncthing itself have reviewed and confirmed that the code is safe, and 2) the original maintainer vouched for the new guy, is good enough for me. There will always be those who refuse to trust anything, even from the original developer, and they are often the most vocal about it - i.e. the "vocal minority". Whether or not you want to listen to their criticisms is up to you. IMO, they're just beating a dead horse.
Passwords Nextcloud app
view more: next ›