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...

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
  • ElectricVocalist@jlai.luEnglish
    92·
    17 hours ago

    No, that would GPL. The benefit for them is that some features will be paid and won’t be unlockable just by using Vaultwarden

    • thr0w4w4y2@sh.itjust.worksEnglish
      65·
      16 hours ago

      it literally says in the post that the license change affects companies who are repackaging and reselling bitwarden, but ok.

      • nibbler@discuss.tchncs.deEnglish
        161·
        15 hours ago

        But this is the post by bitwarden, defending their decision. AKA marketing.

        Can you explain how bitwarden can be “repackaged and resold”, that would be stopped by that change?

        Everybody can still fork/rename/publish the FOSS version which is continued to be available. Everybody can connect to vaultwarden…?

        • Buckshot@programming.devEnglish
          8·
          14 hours ago

          Yeah this only makes sense if the builds start diverging from the open source code, extra features that are closed source.

        • lemmyvore@feddit.nlEnglish
          4·
          12 hours ago

          Everybody can still fork/rename/publish the FOSS version

          Yeah, but there’s no guarantee the FOSS version will be the same as the closed one.

          • nibbler@discuss.tchncs.deEnglish
            1·
            1 hour ago

            There is certainty that the Foss version won’t be worse than current bitwarden client. Then those will diverge. So?

            • lemmyvore@feddit.nlEnglish
              1·
              1 hour ago

              The current FOSS backend used to be the center of the ecosystem. Going forward that may change. If it stops being that center and it becomes merely a token offering so Bitwarden can claim “we’re still doing FOSS” then it will become pointless.

              Simply forking the backend is meaningless without the work to also drag along the entire ecosystem, or establish a new one. Forking a project takes time, effort, vision, persistence, determination.