Concerns Over Bitwarden Moving Away from Open Source: What Does Our Future Hold?

Ask the Community Password Manager
, ,
3

I also note that there have been discussions in:

The reddit’s post above has comments from Kyle matching what Gary said above, including:

Everything that we do has not been FOSS for many years now. We have several business/enterprise products that we sell under a proprietary source available license. Essentially an open core model. We have no plans to change that strategy.

The licensing FAQ also hasn’t substantially changed since at least Oct 2021:

Our current software products have the following licenses:

Bitwarden clients: The core password management code for individual password vaults, including Desktop, Web, Browser, Mobile, and CLI versions, is available under the GPL 3.0 license.

Bitwarden server: The main Bitwarden server code is licensed under the AGPL 3.0 license.

So, back to your questions, in my opinion:
→ For most users, nothing. Bitwarden is not changing feature sets, pricing tiers, and access to the source code. In the Reddit post, Kyle was talking about the strategy of retaining GPL, A-GPL licenses with proprietary, source-available software, which may be controversial/unacceptable to a portion of OSS community. If this is unacceptable, then these people most likely will move off Bitwarden. For people using Vaultwarden, I don’t know. For people using Goldwarden, probably nothing (but we have to ask @quexten for that).
→ This licensing model seems to have been dated back as far as Oct 2021, it only comes to a harsh light because of a possible mistake in packaging. I personally am not attached to a FOSS software, but being able to inspect the code itself is a very good feature to have.
→ Personally, no, but I note that it’s easy to move completely/partially off Bitwarden. Bitwarden has become a standard, and I don’t see a problem if there’s a need to move off BW.

2 Likes