You can selfhost bitwarden, there's also vaultwarden, an open bitearden api implementation. You could host this on an internal-only server. But you also can sync your single password file with a lot devices and use keepass, I just find that a bit annoying. You also cannot share some passwords with your relatives easily that way.

[–] radioactiveradio@lemm.ee 0 points 1 year ago (1 children)

Hey it's fine if you trust them, it's a very convenient service and from what I found it's pretty secure, since there's no way to recover logins if you forget your master pass. But i personally don't like the idea of having passwords on someone else's server and I'm too stoopid to set-up my own instance on a docker container server thingy. Syncthing just works for me, got GUI and everything.

[–] ErwinLottemann@feddit.de 0 points 1 year ago

Totaly valid choice!

[–] darcy@sh.itjust.works 0 points 1 year ago* (last edited 1 year ago) (2 children)

keepass is a different paradigm. it uses a locally encrypted file. many frontends for it (use keepassxc and keepassdx). dont have to rely on some 3rd party, even if they say they have e2ee. theres no better privacy (and security) for an app than not using it with the internet. im not too concerned about ui for pw manager personally, the less time i spend w it unlocked the better. only (slight) problem for me: multi device usage (i just copy the file onto my phone occasionally). general rule of thumb: if it can be selfhosted, it is best to.

i think bitwarden is the best one of its type, it comes down to your needs and threat model

[–] ArcticLynx@feddit.de 0 points 1 year ago* (last edited 1 year ago)

I really like the cross device sync, even tho it's a security risk of course. also, I don't know anything about self hosting (might get into it when I got the time), so bitwarden might be the best pw manager for my requirements rn.

[–] iloverocks@feddit.de 0 points 1 year ago

Many use syncthing to sync their keepass files I personally just use my nextcloud