@jasonhowk @ikenndac
Any of the usual self-hosting stuff, but the nice thing about Bitwarden is that client keeps a copy of the vault locally (I'm sure most password managers do this) so that it's really only sync between client devices that require the vaultwarden instance to be online.
Copies of vault are n=clients+backups+1.
Vault backups go to a zfs volume that get's replicated to an offsite backup nightly, so in the event of corruption or bitrot, there are multiple snapshots.
There was one instance where a client update was incompatible with vaultwarden but that was fixed quickly and you still have your offline vault, just syncing changes between clients wasn't working. That might have been a bigger issue if you were an org, but for family use, it was just annoying.