Bitwarden to Ship Commercial App Store Builds Alongside GPLv3 GitHub Version

Bitwarden announced on October 9, 2026 that starting with its next release, the Bitwarden apps in app stores will be commercially licensed builds. Bitwarden community announcement

No action is required from users. The company said the store apps will work exactly as they do today after the change. That applies to existing installs updating to the next release. No migration is needed.

Direct downloads from its Download Page will also use the commercial license. In parallel, the version licensed under GPLv3, the common open-source license that requires shared code to stay open, continues to be updated and published on GitHub. Anyone who pulls that code and builds the app themselves stays on that open-source track.

All current features are available in both the commercial and GPLv3 versions. That parity covers the codebase as it stands today. For now they start from the same text, like two printings of the same book. The split concerns what comes next.

Some future components will be published under the commercial license and will exist only in that build. Newly developed features will be evaluated case by case for which license applies. The company has not defined a fixed rule for those decisions.

There is no change to self-hosting, or running Bitwarden on your own server instead of Bitwarden's. Bitwarden said the licensing change affects those who repackage and resell Bitwarden. It said it is not going closed-source and users can still fork Bitwarden, or make an independent copy from the code. Code under the commercial license remains viewable and transparent on GitHub. Its free plan is here to stay permanently.

Looking at what this means for deployment teams, the immediate operational impact is small. End users on store builds and direct downloads stay on a supported commercial version with no workflow change. People who self-host by building from the GPLv3 source retain a maintained path with current feature parity.

In my view, the longer planning question is gradual divergence. The two builds match today, but they could separate step by step if commercial-only components add up. Teams that standardize on the GitHub GPLv3 build should track release notes closely to see which new features land in which build. Teams that redistribute Bitwarden code will need to review the commercial terms before repackaging.

The broader context here is sustainability without removing user control. GPLv3 code stays published and forkable, commercial code stays viewable on GitHub, and self-hosting is unchanged. That preserves auditability and choice of which version to run, while giving Bitwarden a mechanism to fund new development.