Bitwarden shifts app store builds to commercial license
Original: Bitwarden Dual License Model
Why This Matters
Signals a growing trend of open-source password managers adopting dual-license models to protect revenue.
Bitwarden announced that starting with the next release, all app store and direct-download builds will carry a commercial license, while the GPLv3 version continues on GitHub with all current features intact.
Bitwarden's RyanL posted on the community forum on October 9, 2026, that the company is moving its publicly distributed app store builds to a commercial license. The GPLv3 open-source version stays on GitHub and keeps all existing features—but new features going forward will be evaluated case-by-case, and some may ship only in the commercial build. Direct downloads from Bitwarden's official download page will also point to the commercial builds. The codebase remains readable, auditable, and forkable on GitHub; Bitwarden explicitly says it is not going closed-source. Self-hosting is unaffected. The company states the change targets those who repackage and resell Bitwarden, not end users. The free plan is described as permanent. In a clarifying exchange, RyanL confirmed that commercially licensed code will still be viewable on GitHub—'this licensing model provides additional legal protection for select features,' he wrote. Community members quickly flagged that 'all current features' language means only existing features are guaranteed in both builds; future features may diverge.