vaultwarden + bitwarden is way more mature right now, but the main difference is that sesame is local-first by design. Vaultwarden also depends on staying compatible with bitwarden's clients/api, while this owns the whole stack
bitwarden clients are open source, so it would be possible to fork them if bitwarden ever makes user unfriendly decisions
bitwarden clients are open source, so it would be possible to fork them if bitwarden ever makes user unfriendly decisions