KeePassXC

You can use KeePassXC for personal login data that you want to manage yourself. It suits you if you prefer a local safe or your own synchronization storage. For centrally managed cooperation in an organisation, you need to assess how access, change conflicts and departure of users are handled.

First, create a database with a strong master password and backup. Test opening that copy before adding a lot of data.

The database is encrypted, but must be decryptable during use. Therefore, secure your computer and set automatic locking. Put the database into cloud storage, then share an encrypted file with that service. Do not store any key file next to the database thoughtlessly when you want to get divorced.

Synchronization takes care of yourself. Without the correct password and any key files you can no longer reach your safe.

Without the correct unlocking data, you cannot use an ordinary account reset to open the database. Save a controlled backup and try recovery before deleting your only old copy. Avoid simultaneously editing the same database on multiple devices without checking how changes are merged.

KeePassXC suits you if you want to save passwords in a local KDBX database and choose your own storage. You don't get a mandatory central vault service. This independence also means that you have to organize synchronize, backups and recovery yourself. It is especially attractive when you want to do that management consciously, instead of leaving everything to an online account.

This choice fits especially if you want to be able to identify where your database and backup are. Also determine how to keep access when one device fails. If you want the same safe everywhere without your own decor, then the management burden is an important disadvantage. For independent control, that same responsibility is precisely the part that you consciously bring to you.