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
  • Thomas Cloer@ieji.de
    282·
    8 hours ago

    @Mustachius_Grumpius “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”

    • badgermurphy@lemmy.worldEnglish
      351·
      60 minutes ago

      Unfortunately, there is no historical example where this hasn’t turned predatory. It’s a tale as old as venture capital has been in software development:

      • get free contributions from altruistic people donating their time and expertise to your FOSS project that you’re selling
      • make a closed-source set of extensions as optional dependencies
      • slowly diverge the closed source feature set to include developer and user “must-haves” you do not contribute upstream
      • slow or functionally halt open source contributions

      It is an oft-repeated long con to pull off a mass heist of donated skill and time while imposing vendor lock-in on your users through a back door.

      "As the poison spread through his body, the frog cried out, “Why did you sting me? You have killed us both!”

      The scorpion replied, “I couldn’t help it. It’s my nature.”

    • freely1333@reddthat.comEnglish
      1·
      6 hours ago

      I kinda thought the paid plan already had extra features no? Like silly ones but I swear it isn’t just donations right?

      • 4am@lemmy.zipEnglish
        4·
        4 hours ago

        It had cloud storage, built in TOTP with autofill, and some had features like organizations and sharing

        Still, this fucking sucks. Bitwarden was literally created as a ln answer to this shit happening to LastPass and Dashlane.

        • freely1333@reddthat.comEnglish
          1·
          3 hours ago

          I get it because minio dying burned me hard but so long as it keeps operating as it does now do we need more features? I would be fine with a continuously secure version of exactly what it does now. I kinda hate feature bloat