Published version update in app stores
community.bitwarden.com
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...

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

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
    • giant_smeeg@feddit.ukEnglish
      15·
      9 days ago

      Don’t even know where i’d switch.

      Proton -> I already use Proton suite and I like the seperation, the 2 password option doesn’t work for me either. I just need a seperate password.

      Keepass -> I use quite a few devices and the sync just seems like a nightmare…

      Any other options? For now i’ll stick as BW is still great but will start exploring others.

          • rumba@lemmy.zipEnglish
            4·
            8 days ago

            A little more than a year ago, Syncthing for Android had a lot of issues, there was a breaking change installed that required updates and the existing clients had issues, it has since been forked.

            If you don’t need the granular security or family-friendliness it should provide.

            • ImmortalColeSlaw@lemmy.todayEnglish
              1·
              4 days ago

              Yes I want to say this was right before or during the chaos because I remember reading about the fork after I gave up lol

          • FauxLiving@lemmy.worldEnglish
            2·
            8 days ago

            I recall having issues and bouncing off of it on my first attempt, but I’ve been using it on GrapheneOS/Pixel 8 Pro without issue for at least 2 years now.

      • blarth@thelemmy.clubEnglish
        71·
        8 days ago

        Because the new CEO seems to really be wanting to find revenue and this step just reaffirms in my mind that he’s likely going to start reducing features for unpaid accounts.

      • rumba@lemmy.zipEnglish
        1·
        8 days ago

        It’s only a matter of time. Quietly private -> publicly private -> remove features from free. It’s inescapable. The stockholder greed compels them.