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 download page will move to commercially licensed builds starting with the next release. The company says the GPLv3 version will continue to be updated on GitHub, current features are available in both versions, and self-hosting is unchanged; future features may differ by license.
Bitwarden says its next releases through app stores and its download page will be commercially licensed, while a GPLv3 version will continue to be updated on GitHub. The password manager company said users do not need to take action and the apps will work as they do today; the announcement leaves open how future features will be divided between the licenses.
In an October 9 post on the Bitwarden Community Forums, the company said apps published to the various stores will become the commercially licensed builds starting with the next release. Bitwarden later clarified in the thread that direct downloads from its website will also use the commercial license. It did not specify a release date.
Bitwarden said the GPLv3-licensed code will remain available and continue to receive updates on GitHub. The company also said people can read, audit, contribute to, and fork the code, and that the released apps are built from code in those repositories. According to Bitwarden, all current features are available in both versions, and the licensing change does not affect self-hosting.
The company described the change as providing additional legal protection for select features. In a forum reply, Bitwarden representative RyanL said some future components will be published under the commercial license and available only in that build. The company said future features will be evaluated case by case, rather than giving a complete list of what will remain in the GPLv3 version.
How the License Split Affects Users
For most people installing Bitwarden through an app store or the company’s download page, the announced change is not an immediate change in how the product works: Bitwarden says no action is needed and current features remain available in both versions. The distinction matters more to users and developers who want to know which license applies to a particular build or to future code.
The decision also matters to open-source contributors and organizations that redistribute software. The company says its GPLv3 codebase and contribution routes remain in place, but its statement that some future components may appear only in the commercial build means the two versions could diverge over time. That could affect what community builds can include, though the company has not specified which components are planned.
Bitwarden says self-hosting is not changing and that its free plan will remain available. Those assurances address two immediate user concerns, but the forum discussion shows that some customers are seeking more detail about long-term feature parity, third-party compatibility, and the licensing of specific downloads.
As an affiliate, we earn on qualifying purchases.
What Bitwarden Has Clarified
The announcement began with a forum post on October 9, 2026. In response to questions, Bitwarden clarified that the company’s website download page, as well as app stores, will direct users to the commercial-license build. It said the source code under that license will still be viewable on GitHub, distinguishing public access to code from the terms under which it may be used or redistributed.
Bitwarden also said the GPLv3 version will continue to be developed, and that current features are present in both versions. Its promise of ongoing GPLv3 updates does not amount to a commitment that every future feature will be included there: the representative’s replies say licensing decisions for new features will be made case by case.
Some forum users raised concerns about the possibility of a gradual reduction in open-source functionality and asked about products such as third-party clients and self-hosted deployments. These posts document community questions and concerns, not confirmed changes to compatibility or the product roadmap. Bitwarden’s replies state that self-hosting is unaffected, but do not answer every question about individual distribution channels or future integrations.
“No action is needed, and the apps will work exactly as they do today.”
— Bitwarden, in its October 9 Community Forums announcement
As an affiliate, we earn on qualifying purchases.
Which Future Features Will Differ
Bitwarden has not named the future components that will be commercial-only, nor provided a schedule or criteria for deciding which license will cover new features. Its statement that current features are available in both builds answers what users receive now, but does not guarantee that functionality will remain equal as development continues.
The forum exchange also leaves some distribution and compatibility questions unresolved, including the license of specific third-party packages and how future commercial-only components might interact with other clients. Bitwarden said the download page will link to the commercial build and that self-hosting is unchanged, but did not provide a channel-by-channel inventory or address every scenario raised by users. No specific break in compatibility or change to self-hosting was confirmed in the thread.
As an affiliate, we earn on qualifying purchases.
Details Expected Before Release
The change is set to take effect with Bitwarden’s next release, although the company did not give a date in the forum post. It said it would work to provide more information about download-page builds after a user asked which license the portable desktop app would use; it subsequently confirmed the download page would link to the commercial build.
Users and developers will be able to follow the release and licensing details through Bitwarden’s GitHub repositories and community forum. The next useful clarification would be a precise list of which builds and components fall under each license, alongside any guidance about future feature differences and third-party compatibility.
As an affiliate, we earn on qualifying purchases.
Key Questions
When will Bitwarden’s apps switch to the commercial license?
Bitwarden says the change starts with the next release. It has not provided a release date.
Is Bitwarden discontinuing its open-source version?
No such discontinuation was announced. Bitwarden says the GPLv3 version will continue to be updated on GitHub, where people can read, audit, contribute to, and fork the code.
Will the commercial build have features the GPLv3 build does not?
Bitwarden says current features are available in both versions, but some future components will be commercial-only. It has not identified those components, and says new features will be considered case by case.
Does the licensing change affect self-hosting?
Bitwarden says self-hosting is unchanged. The announcement does not give further technical details about specific self-hosted setups or third-party clients.
Will users need to do anything when the change takes effect?
Bitwarden says no action is needed and that the apps will work as they do today. The company says its app-store and direct-download releases will use the commercial license.
Source: hn
Columbus Day / Indigenous Peoples' Day Picks
long weekend sales
As an affiliate, we earn on qualifying purchases.
