cross-posted from: https://thelemmy.club/post/57178798

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
  • Sina ( Sina@beehaw.org ) 
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    2 hours ago

    If it remained open source I`d see no reason to panic yet, that is the single most important part. Though having read through so many posts I’m still not sure if that is the practical case for the FF addon I care about.

    I have to look at the alternatives again. I would be fine using Proton for this, but ProtonPass has a couple of issues still. I’m guessing there is no usable free password manager outside of these two, that has a FOSS client doing client side encryption paired with free cloud storage for the passwords. I’m not completely against self hosting, but it would be inconvenient, I’m not going to keep a PC online just for this when I’m not home.

    edit:

    Bitwarden continues development of open source code under GPLv3. Code under the commercial license is just as viewable and transparent on GitHub. This licensing model provides additional legal protection for select features.

    I suppose I can ride this out for a while longer then.