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 that starting with its next release, apps distributed through app stores and its download page will be commercially licensed. The company says its GPLv3 codebase will remain available on GitHub, existing features will be in both versions, and self-hosting is unchanged; some future components may appear only in the commercial build.
Bitwarden said October 9 that apps it distributes through app stores and its download page will use a commercial license starting with the next release, while its GPLv3-licensed code will continue to be updated on GitHub. The password manager says the change requires no action from users and will not affect how the apps currently work, but some future components may be available only in the commercial builds.
In a post on the Bitwarden Community Forums, the company said the store-distributed apps will be commercially licensed and that the GPLv3 version will continue to be published on GitHub. It said all current features are available in both versions. Bitwarden added that people can still read, audit, contribute to and fork the code, and that the apps it releases are built from code in those repositories.
In forum replies, Bitwarden representative RyanL clarified that the company will evaluate newly developed features case by case. Some future components, the representative said, will be published under the commercial license and appear only in that build. RyanL also said direct downloads from Bitwarden’s download page will use the commercial license. The announcement does not provide a timetable for specific features or identify components that will be exclusive.
Bitwarden said the licensing change is intended to provide additional legal protection for select features and affects those repackaging and reselling the software. The company also said there is no change to self-hosting and that its free plan will remain available. Those commitments address immediate concerns, but users have asked how the two versions will differ as development continues.
How the License Split Affects Users
For most users, Bitwarden’s stated immediate effect is limited: no action is required, and the next store builds are expected to work as current apps do. The change matters more over time because the company says some future components may be restricted to the commercial-license version. That could create differences between the app distributed by Bitwarden and GPLv3-based builds, although the company has not yet identified what those differences will be.
The announcement also matters to people and organizations that repackage, redistribute or build on Bitwarden. Commercial licensing changes the legal terms under which those parties can use the distributed builds. At the same time, Bitwarden says its source remains available and forkable under GPLv3, which distinguishes its plan from a complete move to closed-source software. The practical scope of that distinction will depend on which code and components are placed under each license.
password manager with open source code
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
What Bitwarden Says Stays Open
Bitwarden’s October 9 forum announcement describes a dual-license approach: commercially licensed builds for distribution through stores and its download page, with GPLv3 code continuing to be developed and published on GitHub. The company says code under the commercial license will also remain viewable and transparent on GitHub. Access to source code, however, does not by itself mean every component is covered by the same open-source license.
The company’s post followed user questions about whether the move meant Bitwarden was going closed-source, whether self-hosting would change and whether future features would remain in the GPLv3 version. Bitwarden answered that it is not going closed-source, that users can continue to fork the code and that self-hosting is unaffected. It also said newly developed features will be considered individually for licensing, rather than promising that all future features will be included in both versions.
That case-by-case approach leaves a meaningful distinction between continued source availability and a guarantee that every future feature will be GPLv3-licensed. The forum thread records concerns from users who rely on open-source builds or third-party projects, but the available announcement does not settle every compatibility or distribution question they raised.
“The GPLv3 OSS licensed version continues to be updated and published on GitHub.”
— Bitwarden, in its Community Forums announcement
As an affiliate, we earn on qualifying purchases.
Which Features Will Be Commercial
Bitwarden has not named the future components that may be exclusive to commercial builds, explained how it will decide licensing for individual features, or set out a comparison of the two versions. The forum exchange also leaves questions about which license will apply to particular distribution channels, including some downloads and third-party packages.
Users raised questions about compatibility between commercial and GPLv3 clients, third-party projects, and the long-term treatment of self-hosting. Bitwarden says self-hosting is unchanged, but the post does not detail how future commercial-only components could affect those projects. The company’s statements describe its current plan; they do not establish how licensing decisions will be made for every future release.
As an affiliate, we earn on qualifying purchases.
Details to Watch in Future Releases
The change is scheduled to begin with Bitwarden’s next release. Users and developers can compare the release and GitHub materials as they become available to see which code is included in each licensing track and whether any features differ.
Bitwarden invited users to post questions in the forum thread. Further company explanations about feature licensing, package distribution and compatibility would help clarify the effects for self-hosters and third-party developers. Until those details are published, the confirmed position is that GPLv3 development and self-hosting continue, while some future components may be limited to commercial builds.
As an affiliate, we earn on qualifying purchases.
Key Questions
When does Bitwarden’s licensing change start?
Bitwarden said the change begins with its next release. Apps distributed through app stores and Bitwarden’s download page will use the commercial license.
Is Bitwarden ending its open-source version?
No. The company says the GPLv3 version will continue to be updated and published on GitHub, where users can read, audit, contribute to and fork the code. Some future components may be commercial-only.
Will users need to change or reinstall their apps?
Bitwarden said no action is needed and that the apps will work as they do today. It did not describe any immediate change to existing features.
Will the change affect self-hosting?
Bitwarden said there is no change to self-hosting. The announcement did not provide detailed answers about how future commercial-only components could affect third-party projects or compatibility.
Will future features be available in both versions?
Not necessarily. A Bitwarden representative said new features will be considered case by case, and some future components will exist only in the commercial-license build. The company has not yet identified which features those will be.
Source: hn
Halloween Picks
halloween
As an affiliate, we earn on qualifying purchases.
