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
      • nibbler@discuss.tchncs.deEnglish
        3·
        13 hours ago

        History shows this will happen. Or do you have any counter example?

        Mariadb, libreoffice and most recently OpenCourant

        • Natanox@discuss.tchncs.deEnglish
          2·
          13 hours ago

          Not arguing against it of course, just dislike when people make forking (and establishing a whole new standard) sound like not that big of a deal.

          • nibbler@discuss.tchncs.deEnglish
            11·
            13 hours ago

            well, the first step of forking is clicking a button or execting a “git clone” command. thats trivial. publishing to android is a bit of work, but very one-time.

            keeping up with development is a different story - but many foss projects thrive with support from whoever needs to have something fixed.

            • Natanox@discuss.tchncs.deEnglish
              1·
              13 hours ago

              You’ll also have to convince other maintainers to adopt the new API in this case, otherwise it’s pointless. Vaultwarden is only the server, you’d at least require one third-party client (e.g. Keyguard) to add and maintain the Vaultwarden API and probably also someone to fork the browser plugins. This whole issue is quite involved.

              • nibbler@discuss.tchncs.deEnglish
                2·
                12 hours ago

                I highly doubt future compatibility. Things will diverge. I care about having a good hostable password manager. I don’t care about the name of the client or if it’s compatible with some closed source shit.

      • ryannathans@aussie.zoneEnglish
        77·
        18 hours ago

        When presented a hypothetical between the commenter suggesting it be

        A) forked now

        And me suggesting

        B) forking when there is a problem

        You elect C) the commenter does the work?

        Brilliant contribution