Post by @Mustachius_Grumpius@thelemmy.club

2026-10-10 13:33 UTC

Bitwarden Switches to Commercial License RyanL Bitwarden Employee Hello everyone! Starting in the next release, the Bitwarden apps published to the various stores will be the commercially licensed builds. No action is needed, and the apps will work exactly as they do today. Bitwarden remains committed to open source security and transparency The GPLv3 OSS licensed version continues to be updated and published on GitHub All current features are available in both versions License details are on GitHub Bitwarden remains committed to a robust, free forever plan for everyone If you have any questions, please ask them in this thread. Thanks all! EDIT: Bitwarden is not going closed-source You can still fork Bitwarden No change to self-hosting, the licensing change affects those who are repackaging and reselling Bitwarden The free plan is here to stay permanently

Replies (8)

@Lettuceeatlettuce@lemmy.ml 2026-10-10 18:01

Well, we all know how this ends… It’s a really sad day for me, I love Bitwarden, it’s easily the best password manager I’ve used, and I’m in IT, I’ve used a bunch. Fuck private equity, fuck it to death. But until then, I’ll be moving my test setup for KeyPassXC into production over the coming weeks and months. I was happily subscribed to Bitwarden for years for my personal account, I moved several people and a whole company onto its platform. We had a good run, time to move on.

Open ##5099356
@AzuraTheSpellkissed@lemmy.blahaj.zone 2026-10-10 13:50

As always, people overreacting in the comments (of the linked forum). So the current plan is that the core remains OSS, but upcoming features are partially not. To me that sounds similar to Chrome’s or VSCode’s approach.

Open ##5100793
@teezeh@ieji.de 2026-10-10 13:58

@Mustachius_Grumpius@thelemmy.club “The GPLv3 OSS licensed version continues to be updated and published on GitHub All current features are available in both versions License details are on GitHub Bitwarden remains committed to a robust, free forever plan for everyone”

Open ##5102503
@grillme@lemmy.zip 2026-10-10 14:10

Does anyone have a handy guide to switching to selfhosted version? I was considering doing that but I let my plan renew out of laziness.

Open ##5102857
@Decronym@lemmy.decronym.xyz 2026-10-11 04:30

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread: Fewer Letters More Letters SSH Secure Shell for remote terminal access TLS Transport Layer Security, supersedes SSL VPN Virtual Private Network [Thread #125 for this comm, first seen 11th Oct 2026, 04:30] [FAQ] [Full list] [@Two9A@hachyderm.io] [Source code]

Open ##5104589
@1984@lemmy.today 2026-10-11 05:27

There is no way I’m self hosting something this important… So now I’m not sure what to do actually.

Open ##5110967
@possiblylinux127@lemmy.zip 2026-10-10 15:39

It is effectively going closed source

Open ##5111978
@Imaginary_Stand4909@lemmy.blahaj.zone 2026-10-11 19:47

Side note: I just tried switching to KeePassXC and it seems pretty fine, except for one caveat. If you installed your browser (probs FF or Librewolf) through flatpak or snap on Linux, the browser extension will not work. I had to change to the non-Flatpak ver of Librewolf on my Fedora PC, which sucked a little lol 😅

Open ##5142608