The Open Source Tightrope: Analyzing Bitwarden's Shift to Dual Licensing
AI-generated image · Bay Street Wire
Bitwarden is transitioning its app store builds to a commercial license, sparking a debate over the balance between open-source transparency and enterprise monetization.
Q: What specific change is Bitwarden implementing regarding its software distribution?
A: As first reported on the Bitwarden Community Forums, the company is transitioning the apps it publishes to various app stores, as well as direct downloads from its download page, to commercially licensed builds.
Q: Does this mean Bitwarden is abandoning its open-source roots?
A: No. RyanL, representing Bitwarden, stated that the company is not going closed-source and that the GPLv3 OSS licensed version will continue to be updated and published on GitHub. The company also maintains that users can still fork Bitwarden and that the "free forever" plan remains permanent.
Q: Will the functionality of the app change for the average user?
A: For now, no. RyanL clarified that all current features are available in both versions and the apps will function exactly as they do today. However, future features will be evaluated on a case-by-case basis; some may be published exclusively under the commercial license, though RyanL emphasized that this code remains viewable on GitHub for transparency.
Q: Who is most affected by this shift, and how has the community reacted?
A: The change specifically affects those repackaging and reselling Bitwarden, with no change to self-hosting. Community response is mixed; user David Mayr expressed concern, describing the move as a potential "rugpull" and citing previous negative experiences with MinIO. Mayr specifically questioned the future ease of self-hosting and compatibility for third-party teams like Vaultwarden.