TL;DR
Get privacy and security gear delivered free with Prime
- Fast, free delivery on millions of items
- Prime Video, Amazon Music and more included
- Member-only deals all year
Bitwarden says apps distributed through app stores and its download page will move to a commercial license starting with the next release. The company says its GPLv3-licensed code will continue to be updated on GitHub, existing features will be available in both versions, and self-hosting is unaffected; future features may differ by license.
Bitwarden will distribute its apps under a commercial license beginning with the next release, while continuing to publish and update a GPLv3-licensed version on GitHub, the password manager said in a community forum post on October 9. The change affects the licensing of builds distributed through app stores and Bitwarden’s download page; the company says users do not need to take action and the apps will work as they do now.
Bitwarden said the GPLv3 open-source version will remain available on GitHub, where people can read, audit and contribute to the code. The company also said its commercially licensed apps are built from code in those repositories and that it is not going closed-source. According to a Bitwarden representative, direct downloads from the company’s app download page will also use the commercial license.
The announcement says all current features are available in both versions. However, Bitwarden representative RyanL wrote in the forum that some future components may appear only in the commercial build, and that new features will be assigned a license on a case-by-case basis. The company described the commercial model as providing additional legal protection for selected features.
Bitwarden said the license change affects organizations that repackage and resell Bitwarden, not self-hosting. It also said its free plan will remain available permanently. The post did not give a detailed feature-by-feature comparison between the two builds or specify which future components might be exclusive to the commercial version.
What the License Change Means for Users
For existing users, Bitwarden says the immediate effect should be limited: no action is required, and the next store-distributed app is expected to work as before. The announcement does not say that current features will be removed from the GPLv3 build. Its assurance that present features remain in both versions gives users a near-term point of comparison, but does not settle how the versions may diverge as development continues.
The longer-term issue is how Bitwarden will divide new development between the two licenses. Users who value an open-source client, maintain self-hosted deployments, or depend on third-party implementations may want to know whether future functions will remain available under GPLv3 and whether versions will continue to interoperate. The company’s stated case-by-case approach leaves those decisions open rather than setting a fixed policy for every future feature.
For businesses that redistribute or sell Bitwarden-based products, the change has a direct licensing implication: the builds distributed by Bitwarden will be commercially licensed. Bitwarden says that additional legal protection for selected features is a purpose of the model, but it has not provided a detailed explanation of the terms or their application to specific use cases in the supplied announcement.
As an affiliate, we earn on qualifying purchases.
Two Licenses, One Published Codebase
Bitwarden’s forum announcement describes a dual-license approach: commercial licenses for the apps Bitwarden distributes and continued GPLv3 publication of open-source code. The company says code under the commercial license will also remain viewable and transparent on GitHub. It also says users can still fork the project, and that the apps it releases are built from code in those repositories.
The discussion that followed shows that users were seeking clarity on distribution as well as licensing. One forum participant asked whether the portable desktop app and store versions would be commercial or open-source builds; RyanL said the download page would direct users to the commercial license. Participants also raised questions about Linux distribution packages, differences between the parallel builds, compatibility, and whether self-hosting would remain supported. The supplied thread does not record answers to all of those questions.
Some commenters expressed concern that the change could lead to fewer features being developed under the open-source license. Those comments are user concerns, not confirmation that Bitwarden plans to discontinue its GPLv3 version. The company’s stated position is that it will continue GPLv3 development, while deciding the license for new features individually.
“No action is needed, and the apps will work exactly as they do today.”
— Bitwarden, in its October 9 community forum announcement
As an affiliate, we earn on qualifying purchases.
Future Feature Access Remains Open
Bitwarden has not published a complete comparison of the two builds or named the future components that may be commercial-only. It is also not clear from the supplied forum discussion how the company will communicate licensing decisions feature by feature, or how quickly changes in one build will be reflected in the other.
Questions about the licensing of particular package formats, including the Linux Flatpak and portable desktop app, were raised in the thread. The representative answered that the main download page will direct to the commercial license, but the supplied material does not establish the status of every third-party distribution channel. It also does not provide detailed compatibility commitments for commercial and GPLv3 clients, or for third-party server implementations.
Bitwarden says self-hosting is unchanged and that its free plan will remain. The post does not spell out how those assurances apply to every future product or deployment scenario. No date beyond “the next release” is given for the first commercial build.
As an affiliate, we earn on qualifying purchases.
Next Release Will Set the Baseline
The next Bitwarden app release is expected to introduce the commercial license in builds distributed through app stores and the company’s download page. Bitwarden has not specified a release date in the supplied announcement. Users and administrators can check the release notes and license details on GitHub as that release approaches.
Further clarity will depend on Bitwarden’s publishing decisions for later features and on any additional answers it gives to questions in the community forum. A feature-by-feature account of what is shared between the builds, along with details for specific download channels, would help users assess practical differences. For now, the company’s published commitments are that GPLv3 code will continue to be updated, current features remain in both versions, and self-hosting is not affected by this licensing change.
As an affiliate, we earn on qualifying purchases.
Key Questions
When does Bitwarden’s commercial licensing change begin?
Bitwarden says it will begin with the next release. The October 9, 2026, forum announcement did not give a specific release date.
Will Bitwarden remain open source?
Bitwarden says it will continue updating and publishing a GPLv3-licensed version on GitHub. It also says users can view, audit, contribute to and fork the code. The company says it is not going closed-source.
Will users lose features or need to change anything now?
Bitwarden says no action is needed and that all current features are available in both builds. Some future components may be exclusive to the commercial build, and the company says it will decide licensing for new features case by case.
Does the change affect self-hosting?
Bitwarden says the licensing change does not affect self-hosting. The supplied announcement does not detail every future deployment or compatibility scenario.
Who is the commercial license aimed at?
Bitwarden says the change affects those repackaging and reselling Bitwarden. It describes the commercial license as providing additional legal protection for selected features, but the supplied material does not include detailed license terms.
Source: hn
Halloween Picks
halloween
As an affiliate, we earn on qualifying purchases.
