I’m using Vaultgarden. Things are okay after losing my SSD yesterday morning. My strategy worked… HDD for data, SSD for the OS. I promptly found an available drive, installed Linux mint and recovered.
But that was scary. I keep a backup on another computer. The only way to actually run it and see the passwords needed to do anything was thru my phone. I was lucky that somehow the database was available offline. But if I had run out of battery I would be extremely screwed.
So I’ve decided the Vaultgarden is encumbered by not really having a local reliable copy. Maybe I’m wrong, but as I understand, if your server goes down and you log out, you’re screwed… No more passwords until your server is up again. I find that to be extremely stupid unless I was protecting my severed testicles… No wait, that would be way worse.
So I’d there a server + local system? Like Joplin… You can write notes all day with no server at all. The server just Synchronizes it all. In the past I used syncthing and I will continue using it. One thought was to have an automated backup from Vaultgarden that was automatically synced to my various devices as a Keypass database.


Important distinction: The OG KeePass desktop program supports that. KeePass XC (popular fork for Linux users, which includes OP) does not, and the maintainers have loudly rejected any attempts to add it.
It’s the only reason I still run the OG KeePass on my work laptop; webdav is the only way I can access my password database within the restrictions of my employer’s policies. I would prefer to run XC.
While you’re correct, you can merge databases with KeePassXC, which just means the method of syncing is separate. So you could have a shared folder using one of those methods you mentioned to sync and just merge it in regularly. Certainly not as simple, but does solve the problem.
Ah yes, I forgot about the merge ability. Pretty sweet protocol, honestly.
There is also KeePassDX, for android.