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
  • sbird ( scallisto@retrofed.com ) 
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    5 days ago

    From reading the thread, it looks like they are dodging the question of what features will be restricted to the commercial license versions (“case-by-case basis” apparently). They keep repeating “no change to people using the app currently”, “no change to self-hosting right now”, etc., but it doesn’t inspire confidence.

    I would recommend to read the thread and ask questions there if you have any, but I would definitely have a backup plan ready.

    The KeePass ecosystem is awesome and it’s what I use, it’s local-first and you can use Syncthing to have passwords across many devices. KeePassXC for desktop (+ browser extension if you need it), KeePassDX on Android (w/ Syncthing-fork), and if you use iOS, you have KeePassium and Strongbox (w/ Synctrain). The iOS apps are more limited, blame Apple for their restrictive ecosystem and high entry fee.

    edit: Recently swapped out KeePassXC for ChiPass, a fork that has does not allow LLM use for development. It works fine with the same browser extension (which has a different LLM policy to the desktop client from my understanding), plus it works better with my system theme (running Niri + Noctalia, maybe Qt6 is better implemented in ChiPass? Not sure)

    Either is fine, but I like ChiPass more for their stronger LLM policy (which means less shoddy code!) and the better theming. I also prefer ChiPass’s icon (password boxes in a keyring) over KeePassXC’s (…a key), if anything