TL;DR
Get business pricing on monitors, keyboards and dev gear
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
Bitwarden says apps distributed through app stores and its direct download page will move to a commercial license starting with the next release. The company says its GPLv3 code will continue to be updated on GitHub, current features remain available in both builds, and self-hosting is not changing; how future features will be divided between licenses remains undecided.
Bitwarden will distribute commercially licensed builds of its password-manager apps through app stores and its direct download page starting with the next release, the company said in a community forum post on October 9. It says the change does not end its open-source development: the GPLv3 version will continue to be updated on GitHub, and current features will be available in both versions.
Bitwarden said users do not need to take action and that the apps will work as they do today. It also said the builds released by the company are made from code available in its GitHub repositories, which users can still read, audit, contribute to and fork. The company described its aim as maintaining open-source security and transparency while applying commercial licensing to builds distributed through its channels.
In follow-up replies, Bitwarden clarified that the direct links on its download page will also point to the commercial build. A company representative said the commercial licensing model provides additional legal protection for select features. Bitwarden also said future components may be published only under the commercial license, and that it will decide case by case which license applies to newly developed features.
The announcement says the current feature set is available in both versions. It does not promise that every future feature will be included in the GPLv3 build. Bitwarden said its free plan is staying, and that the licensing change affects people repackaging and reselling the software rather than self-hosting. It also said there is no change to self-hosting.
What the License Change Means
The change matters to users and organizations that choose software partly because its code is licensed for reuse, modification and redistribution. Bitwarden says the code remains viewable and that the GPLv3 project will continue, but the official builds users download will be commercially licensed. That distinction affects the terms governing those builds even if their source code can still be inspected.
For people who simply use the apps, Bitwarden says no immediate change is required and current features will remain available. For developers, downstream distributors and users tracking future development, the open question is how often new components or features will be exclusive to the commercial build. That could produce differences between the two versions over time, although the company has not specified what those differences will be.
The forum announcement prompted questions from users who rely on self-hosting or third-party projects and who want the open-source version to remain useful. Bitwarden’s statements address self-hosting and continued GPLv3 updates, but do not settle every practical question about future feature parity or compatibility.
As an affiliate, we earn on qualifying purchases.
How Bitwarden Describes Both Builds
Bitwarden’s October 9 post presented the change as a dual-license model: commercially licensed builds for distribution through its app-store listings and download page, and a GPLv3-licensed version that remains available and updated on GitHub. The company’s replies added that code under the commercial license will also remain viewable and transparent on GitHub.
The forum discussion distinguished source-code access from licensing. A user asked whether future features excluded from GPLv3 builds would still be open source; Bitwarden’s representative said some future components may be commercial-only and that each new feature will be evaluated individually. That response confirms that continued code visibility does not necessarily mean every component will be released under GPLv3.
Users also raised concerns about self-hosted installations and compatibility with community-maintained clients. Bitwarden said self-hosting is unaffected and that the licensing change targets repackaging and resale. The source material does not provide detailed compatibility commitments for third-party software.
“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.
Open Questions on Future Features
The release date for the next build and a detailed schedule for the licensing change were not provided. Bitwarden also has not listed which future components or features, if any, will be exclusive to the commercial build, or how it will communicate licensing decisions as development proceeds.
Forum users asked about the licensing of particular download channels, feature differences, compatibility between commercial and GPLv3 clients, and support for third-party projects such as Vaultwarden. The company answered that its direct-download page will serve the commercial build and that self-hosting is unchanged, but the supplied statements do not resolve every channel-specific or compatibility question. Claims from commenters about possible future withdrawal of open-source development are concerns expressed in the discussion, not announced Bitwarden policy.
As an affiliate, we earn on qualifying purchases.
Details Expected Before Release
Bitwarden said the licensing change will begin with its next app release, but did not give a date in the forum post. The company invited users to ask questions in the discussion thread. Its next useful clarification would be a channel-by-channel account of which build users will receive, along with a clear description of how it will identify components and features released under each license.
Until Bitwarden provides those details, users can rely on the company’s stated commitments: GPLv3 code will continue to be updated on GitHub, current features will be available in both builds, and self-hosting is not changing. Whether those commitments translate into long-term feature parity or specific guarantees for third-party compatibility remains unresolved.
password manager with commercial license
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
When does Bitwarden’s commercial licensing change take effect?
Bitwarden said it will begin with the next release. The October 9, 2026, announcement did not specify a release date.
Is Bitwarden ending its open-source version?
No. Bitwarden said the GPLv3 version will continue to be updated on GitHub, and that users can still inspect, audit, contribute to and fork code. It also said it is not going closed-source.
Will users need to change anything?
Bitwarden said no action is needed and that the apps will work as they do today. It said current features will be available in both versions.
Will self-hosting be affected?
Bitwarden said the licensing change does not affect self-hosting. The announcement did not provide detailed commitments about compatibility with every third-party client or project.
Could future features be missing from the GPLv3 build?
Yes. Bitwarden said some future components may be available only in the commercial build, and that it will decide the license for new features case by case. It has not identified specific future features that will be excluded from the GPLv3 version.
Source: hn
Columbus Day / Indigenous Peoples' Day Picks
long weekend sales
As an affiliate, we earn on qualifying purchases.
