TL;DR
Get the latest gadgets 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 commercially licensed builds beginning with the next release. It says the GPLv3 version will continue to be updated on GitHub, current features are available in both versions, and self-hosting is unaffected; future features may be assigned to either license case by case.
Bitwarden plans to distribute its password-manager apps through app stores and its own download page under a commercial license starting with the next release, the company said in a community-forum post on October 9. It says the GPLv3-licensed code will remain available and updated on GitHub, while the licensing change is intended to provide additional legal protection for selected features.
Bitwarden said users do not need to take action and that the apps will work as they do now. The company said all current features are available in both versions, and that apps distributed by Bitwarden are built from code in its GitHub repositories. It also said people can continue to read, audit, contribute to and fork the codebase, adding that the change does not mean Bitwarden is going closed-source.
In a follow-up forum reply, Bitwarden representative RyanL clarified that direct downloads from Bitwarden’s website will also use the commercial license. Asked how future features would be divided, RyanL said some components may be published under that license and exist only in the commercial build; new features will be considered case by case. The company said code under the commercial license will remain viewable and transparent on GitHub.
Bitwarden also said the licensing change does not affect self-hosting and is aimed at parties that repackage and resell the product. It reaffirmed that its free plan will remain available. The announcement does not provide a detailed list of future components that may be restricted to the commercial build.
How the License Split Affects Users
For ordinary users, Bitwarden says the immediate change should require no action and should not alter current features. The distinction matters most to people who choose software based on its license, maintain forks, distribute repackaged builds or rely on particular client versions. Those users will need to track which code and features remain under GPLv3 as the two licensing paths develop.
For self-hosters and projects that work with Bitwarden-compatible services, the company’s statement that self-hosting is unchanged offers near-term reassurance. But the announcement leaves future feature allocation to a case-by-case decision, so it does not promise that every later capability will appear in both builds. That creates questions for developers and users planning around long-term compatibility, even as the source code remains publicly inspectable.
The policy also distinguishes source visibility from licensing rights: Bitwarden says commercially licensed code will still be viewable on GitHub, but visibility alone does not establish the same reuse and redistribution permissions as GPLv3. The practical consequences will depend on the terms of each license and the features Bitwarden assigns to each version.
As an affiliate, we earn on qualifying purchases.
What Bitwarden Announced
The announcement appeared in the Bitwarden Community Forums on October 9, 2026, under the heading “Published version update in app stores.” Bitwarden described a change to the licensing of builds it publishes, not a removal of its code from public view. It said its GPLv3 open-source version will continue to be updated and published on GitHub.
Forum users asked which license would apply to downloads outside app stores and whether future functionality would be split between versions. RyanL answered that Bitwarden’s website download links would point to the commercial-license build and that new features would be evaluated individually. The exchange records the company’s stated plan; it does not specify a release date beyond saying the change starts with the next release.
Some users raised concerns about whether the open-source edition might eventually fall behind or whether self-hosting and third-party compatibility could change. Those are users’ concerns, not evidence that Bitwarden has announced such changes. The company’s response says self-hosting remains unaffected and the GPLv3 code will keep receiving updates, while leaving the future license of individual features open to case-by-case decisions.
“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.
Which Future Features Stay Open
Bitwarden has not named the future components that will be exclusive to the commercial build, or explained how many features may be assigned to each license. It also has not published a side-by-side feature comparison for the two versions. Although it says current features are available in both, the scope of that assurance is limited to current features.
The forum exchange does not spell out how the change will apply to every distribution channel or community-maintained package, including specific platform builds users asked about. It also does not detail how compatibility between commercial clients, GPLv3 clients and third-party implementations will be handled if future features differ. Bitwarden’s statements on GitHub updates and self-hosting describe its current plan, but the post does not set out a longer-term guarantee covering every future release or feature.
password manager with GPLv3 license
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Details Expected Before Release
The licensing change is scheduled to begin with Bitwarden’s next release. The company has not given a release date in the supplied forum announcement. Users and developers can watch the release notes and GitHub repositories for details on the builds, license notices and any feature differences as that release approaches.
Bitwarden invited questions in the forum thread, and its representative said the company would work to answer a question about the portable desktop app. Further clarification on channel-specific builds, future feature allocation and compatibility would help users decide which version fits their needs. Until those details are published, the confirmed points are the planned commercial licensing of Bitwarden-distributed builds, continued GPLv3 updates on GitHub, and the company’s statement that self-hosting is not affected.
As an affiliate, we earn on qualifying purchases.
Key Questions
When does Bitwarden’s commercial licensing change begin?
Bitwarden says the change starts with the next release. Its October 9, 2026, forum post did not give a specific release date.
Will Bitwarden’s source code remain available?
Yes. Bitwarden says its GPLv3 version will continue to be updated and published on GitHub. It also says the code behind its apps remains viewable, auditable and open to contributions, including code under the commercial license.
Will users lose current features or need to change anything?
Bitwarden says no action is needed, the apps will work as they do today, and all current features are available in both versions. It has not listed which future components may be exclusive to the commercial build.
Does the licensing change affect self-hosting?
Bitwarden says the change does not affect self-hosting. It has not provided a detailed account of how every future feature or third-party implementation will interact with the two licensing paths.
Will future features be available in the GPLv3 version?
That has not been determined across the board. A Bitwarden representative said future features will be evaluated case by case, and that some components may appear only in the commercial build.
Source: hn
Fall Picks
fall essentials
As an affiliate, we earn on qualifying purchases.
