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. It says GPLv3-licensed code will continue to be updated on GitHub, current features will be available in both versions, and self-hosting will not change; the company says future features will be assigned a license case by case.
Bitwarden will distribute commercially licensed builds of its password-manager apps through app stores and its download page starting with the next release, the company said in a community-forum announcement on October 9. It says the GPLv3-licensed code will remain available and updated on GitHub, but the change creates a distinction between the license of distributed apps and the open-source codebase.
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 will be available in both versions, and described the change as affecting people who repackage and resell Bitwarden rather than changing the service for ordinary users. Direct downloads from Bitwarden’s website, including the download page, will also point to commercially licensed builds.
The company’s forum replies clarified that the GPLv3 version will continue to be developed and published on GitHub. Bitwarden said code under the commercial license will also remain viewable there, and that the apps it releases are built from code in those repositories. It described the commercial model as providing additional legal protection for select features.
Asked how future development will be split, a Bitwarden representative said some future components will be published under the commercial license and exist only in that build. The representative added that new features will be evaluated case by case. That leaves open which features will appear in each version, beyond the company’s assurance that current features are present in both.
A License Split for Future Features
The announcement matters to users and developers who rely on Bitwarden’s code being available under an open-source license. The continued GPLv3 release means the company is not announcing that its entire codebase is becoming closed source. But the planned commercial build introduces a possible difference in future functionality: Bitwarden says some new components may be exclusive to that build.
For people who install Bitwarden through mainstream app stores or the company’s download page, the change will apply to the distributed build without requiring a new user decision, according to Bitwarden. Users who audit, modify, or redistribute the code will want to track which parts remain under GPLv3 and what terms apply to commercial-only components. The announcement also matters to organizations and third-party projects that depend on compatibility with Bitwarden’s apps or protocols, though Bitwarden said the licensing change does not alter self-hosting.
As an affiliate, we earn on qualifying purchases.
What Bitwarden Has Said So Far
Bitwarden’s October 9 forum post said the GPLv3 open-source version would continue to be updated and published on GitHub, and that users could still read, audit, contribute to, and fork the code. The company also said its free plan would remain available. These are statements about the announced policy; the forum post does not set out a detailed long-term schedule for open-source releases or a list of components assigned to each license.
In response to a question about downloads, a Bitwarden representative said the company’s download page would link to the commercial-license build. The same reply said code covered by that license would remain visible on GitHub. The announcement therefore distinguishes between public access to code and the license governing particular builds or components.
Some forum participants raised concerns about whether future features, self-hosted setups, and third-party clients would remain compatible. Those posts document user questions and reactions, not evidence that compatibility or self-hosting has already changed. Bitwarden’s stated position is that the licensing change affects repackaging and resale, and that self-hosting is unchanged.
“No action is needed, and the apps will work exactly as they do today.”
— Bitwarden, in its community-forum announcement
As an affiliate, we earn on qualifying purchases.
Feature Differences Remain Undecided
The announcement does not identify which future components or features will be commercial-only, how often those decisions will be communicated, or whether the two versions will remain functionally aligned over time. Bitwarden’s assurance that all current features are in both versions does not answer which new features will be included in the GPLv3 release.
Forum users also asked which license will apply to specific distribution channels, including a portable desktop download and Flatpak packages, and raised questions about compatibility between commercial and open-source clients and third-party projects. The supplied announcement and replies do not resolve every channel-specific question. Bitwarden said self-hosting is unchanged, but did not provide additional technical detail in the cited exchange about future protocol compatibility or a long-term guarantee against changes.
As an affiliate, we earn on qualifying purchases.
Next Release Sets the Change
The licensing shift is scheduled to start with Bitwarden’s next app release. Users can watch the release notes and the project’s GitHub repositories for details on which builds and components use each license. Bitwarden invited users to post questions in the forum thread, but the announcement did not give a date for the next release or a complete channel-by-channel distribution plan.
As new features are developed, the company says it will decide case by case whether they fall under GPLv3 or the commercial license. The practical scope of the change will become clearer as Bitwarden publishes those decisions and ships the first commercially licensed builds.
As an affiliate, we earn on qualifying purchases.
Key Questions
Is Bitwarden making its entire codebase closed source?
No. Bitwarden says it will continue updating and publishing its GPLv3-licensed code on GitHub, where people can read, audit, contribute to, and fork it. Some future components may be available only under the commercial license.
Which Bitwarden apps will use the commercial license?
Bitwarden said apps published through app stores will use commercially licensed builds starting with the next release. It also said direct downloads from its website’s download page will link to the commercial-license build.
Will existing features disappear from the open-source version?
Bitwarden said all current features will be available in both versions. It has not named which future features or components may be exclusive to the commercial build.
Is self-hosting changing?
Bitwarden said the licensing change does not change self-hosting. The forum exchange does not give further detail about long-term compatibility for third-party projects or every distribution channel.
When does the licensing change take effect?
Bitwarden said it will begin with the next release. The announcement did not provide a release date.
Source: hn
Halloween Picks
halloween
As an affiliate, we earn on qualifying purchases.
