• Might be a dark turn, but being on the B-side already, I’m often thinking about “detached” self-hosted approaches, like what if I’m being hit by a tram and all my family members’ password gets sealed. So I don’t want to cripple everyones digital life on top of other bad things happening. Also interesting with 3rd party solutions - what if the chosen SaaS makes a step where everyone should migrate off from it… depending on the family size, it can be a real pain in the neck, an urgent, critical issue any day which you are dedicated to solve for them.


    score 1 · canonical

  • If you use KeePass, make sure to use the remote storage integrations for it, that’ll make sure that you get useful sync/merge behavior.

    KeePass isn’t just XC, there’s also apps for both Android and iOS that have autofill integration, and that’ll connect to a Google Drive or SFTP folder and do intelligent merging, as long as you use an integration so it knows that it’s a remote folder, and not just a local folder that happens to be sync’d.

    I can attest that I’m using KeePass (via Keepass2Android and OneKeyPass) for my partner and I, and it’s working nicely against an SFTP folder, and my partner basically only had to switch from using 1password to using the KeePass apps.


    score 1 · canonical

    • If you use KeePass, make sure to use the remote storage integrations for it, that’ll make sure that you get useful sync/merge behavior.

      What I do is just stick it in Nextcloud and as long machines you’re not using have the DB locked, it’s pretty Just Works, as it syncs the files elsewhere. The remote stuff requires all the clients have the same specific protocols supported.


      score 1 · canonical

  • I use KeepassXC with Syncthing for personal and team databases, the only downside of it is merge conflicts, but I’m not really worried about it as it doesn’t happen often and syncthing keeps the conflict so i wont lose the data


    score 1 · canonical

    • Same. In case of a conflict it’s usually even possible to import one of the conflicted databases into the other - duplicates get discarded, and then you have all entries in one.

      Currently trying out ChiPass (a less vibey excuse me, consultant-written fork of XC). At least before XC finally made the switch to Qt6, Chi was even nicer to use, with fewer UI glitches on my system.


      score 1 · canonical

      • If you use any of the built-in remote storage options for a given iOS KeePass app (of which there are several, I’m currently using OneKeePass), those will work fine for shared vaults, and because of them treated the shared vault as a remote file, KeePass apps also cache it locally and can do per-entry merge instead of just dropping a conflict file if changes collide.


        score 1 · canonical

  • If it was me doing this, I’d choose 1Password and try to avoid the hubris that I can do better (my background is infosec and so I’m well aware what I can do with self hosting it. I just don’t want to be the single bus factor on it)

    Luckily, my reverse dependencies (aka parents) are relatively technical and they have their own password manager setup.

    Evaluate what you want to spend time on.

    1Password may misstep - I wouldn’t judge it as a pattern.


    score 1 · canonical

  • Another KeePass[DX|XC]+Syncthing user here, though I acknowledge the initial setup can be clunky and it could be a pain if you have a lot of people accessing the same database. You’d want Syncthing-Fork from F-Droid for your Android users and I’m less familiar with the iOS side. Nevertheless, it’s worked great for my wife and me.

    The side benefit is that Syncthing makes it so easy to sync and backup anything. Once you have it installed for one thing (like a password database) you’ll find yourself using it for so much more. It’s so easy to have multiple copies of your important data across devices without needing a central server or cloud account (but you can also easily have it running on a home machine as a central repository).


    score 2 · canonical