This means that an encrypted vault lands on either Bitwarden or Vaultwarden. While I do not believe there is any inherit security risk with Vaultwarden, as all encryption of your passwords and vault data happen client-side and thus are encrypted on your device before ever being sent to the server.

Vaultwarden themselves even acknowledge the need to support the “upstream project” Official Bitwarden, as without them there would be no clients, or even Vaultwarden to begin! Such is the nature of open-source.Īs I understand Bitwarden’s main focus of business is towards those Teams, MSP, and Enterprise users who can afford to pay a reasonable cost for protecting digital assets, while maintaining a low cost for individuals and familes and at a bare minimum an ostensive free plan for the most basic of password management and security. As I understand the creators of Bitwarden requested the name change due to the confusion and the developers of Vaultwarden try to explicitly state the differences and official support channels vs Vaultwarden support.īitwarden of course is an Open-source project, so all the code is available for any one to create their own fork, or compatible service such as Vaultwarden. Vaultwarden was previously known as Bitwarden_RS, aka Bitwarden written in RUST. This is similar to self-hosting your own official Bitwarden service, and is mostly aimed at small businesses, families, and tech hobbiest and tinkers. Vaultwarden is only a compatible backend server, and still requires the use of the official Bitwarden clients. To say Vaultwarden is a fork of Bitwarden is something that makes it easy to understand but truly Vaultwarden is a completely separate project and the code-base is mostly written in RUST. Often some members here have inadvertently installed Vaultwarden thinking it was the official release without realizing. It’s a wonderful question and one that has come up from time to time.

Bitwarden_rs docker