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 switch to commercially licensed builds starting with the next release. The company says its GPLv3-licensed code will continue to be updated on GitHub, existing features will remain in both versions, and self-hosting is unaffected; future features may differ by license.
Bitwarden will distribute commercially licensed builds of its apps through app stores and its direct-download page starting with the next release, the password manager said October 9. The company says its GPLv3-licensed code will remain available and continue to be updated on GitHub, but it also said some future components may be exclusive to commercial builds, raising questions about how the versions will diverge.
Bitwarden said users do not need to take action and that the apps will work as they do today when the licensing change begins. The company also said all current features are available in both versions. In a follow-up on its community forum, Bitwarden clarified that direct downloads from its website, as well as store releases, will use the commercial license.
The company described the move as a change in licensing for selected builds, not a decision to close its code. It said the code remains viewable on GitHub, that released apps are built from code in those repositories, and that users can still read, audit, contribute to and fork the project. Bitwarden also said the licensing change affects people repackaging and reselling Bitwarden, and does not change self-hosting.
However, the two versions may not remain identical indefinitely. In response to a forum question, Bitwarden representative RyanL said some future components will be published under the commercial license and appear only in that build. The company said newly developed features will be considered on a case-by-case basis. It described the commercial model as providing additional legal protection for select features.
How the License Split Could Affect Users
For most users, Bitwarden says the immediate effect should be limited: existing features remain available in both builds, and the apps will continue to work without action. The longer-term question is whether features will be divided between licenses, and what that could mean for people who choose or need the GPLv3 version.
The distinction matters to users who value open-source licensing, as well as developers and organizations that redistribute or build on the software. Continued access to code on GitHub supports inspection and forking, but access to source code and the rights granted by a license are separate issues. A commercially licensed component may be visible in a repository while not being available under GPLv3.
Bitwarden’s statements that self-hosting is unchanged and that the free plan will remain available address two immediate concerns raised in the discussion. They do not, by themselves, settle which future features will be released under each license. Users choosing a build may need to check its licensing and feature availability as releases arrive.
password manager with open source code
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
What Bitwarden Has Said About Both Builds
Bitwarden’s announcement appeared in its community forum on October 9, 2026. The initial post said the next store-published apps would be commercially licensed while the GPLv3 open-source version would continue to be published on GitHub. It also said the change would not require users to take action and that the free plan would remain available.
Forum members then asked whether direct downloads and future features would follow the commercial license, and what differences would exist between the versions. Bitwarden responded that its direct-download page would also point to the commercial build. It said new features would be evaluated individually, rather than confirming that all future development would be available under GPLv3.
Some users voiced concern that the licensing change could eventually reduce the scope of the open-source version. Those comments express user concerns, not evidence that Bitwarden has announced an end to GPLv3 development. The company’s stated position is that GPLv3 code will continue to be developed and made available on GitHub.
“The GPLv3 OSS licensed version continues to be updated and published on GitHub.”
— Bitwarden, in its October 9 community forum announcement
As an affiliate, we earn on qualifying purchases.
Which Features Will Remain GPLv3
Bitwarden has not published a list of future features or components that will be available only in commercial builds, nor a timeline for their release. Its case-by-case approach leaves the future scope of the GPLv3 version unsettled. The company has said current features are in both versions, but that does not establish that later features will be.
Questions raised by forum participants about particular download channels, compatibility between versions, and the effect on third-party projects were not all answered in the material provided. Bitwarden says self-hosting is unchanged, but the longer-term implications for particular community integrations are not detailed. No change to the free plan was announced; the company said it would remain available.
As an affiliate, we earn on qualifying purchases.
Details Expected Before Release
The change is scheduled to begin with Bitwarden’s next release. The company said it would work to clarify which license applies to specific downloads, and confirmed its website’s direct-download links will point to commercial builds. Users and developers can compare the release information with the code and licensing details Bitwarden publishes on GitHub.
As new components are announced, the key points to watch are whether they are available under GPLv3, whether existing features remain consistent across builds, and how Bitwarden documents distribution and compatibility. The forum announcement does not provide a release date or a complete feature-by-feature comparison.
As an affiliate, we earn on qualifying purchases.
Key Questions
When does the Bitwarden licensing change start?
Bitwarden says the change starts with the next release. The announcement, posted October 9, 2026, does not give a specific release date.Will Bitwarden stop publishing open-source code?
The company says its GPLv3-licensed code will continue to be updated and published on GitHub. It also says users can inspect, contribute to and fork the code.Will the two Bitwarden versions have the same features?
Bitwarden says all current features are available in both versions. It also says some future components may be exclusive to commercial builds, with new features assigned a license case by case.Does the change affect self-hosting or the free plan?
Bitwarden said the licensing change does not affect self-hosting and that its free plan will remain available. The announcement did not detail every possible effect on third-party integrations.Source: hn
Columbus Day / Indigenous Peoples' Day Picks
long weekend sales
As an affiliate, we earn on qualifying purchases.
