Unfortunately the self-host documentation isn't great and the deployment options are quite limited.
Sure, it's at least dockerised, but it requires root privileges (so no running it in a secured kubernetes env) and forces you to use MSSQL as the db (so pay up for that or hope that express works).
It's also unfriendly to automated deployment, with several manual steps and regular rebooting requires.
Make sure you go into that eyes wide open, I misguidedly thought there was some communication between Bitwarden and the open source vaultwarden but there is not.
I've been burnt by things breaking as Bitwarden updates the client and vaultwarden tries to keep up without any advance notice of the changes until someone reports it's broken.
I prefer Vaultwarden because it’s much much easier to set up and had only minimal problems, the only one I could think of being some inconsistent behavior when syncing passwords for the clients inside organizations. I find the setting up of Bitwarden locally gruesome.
There was a breaking change when I updated to iOS 18, but by the time I’ve noticed that, it was already fixed in an update.
